Minutes of the 9th January 2020 Teleconference     Austin-995 Page 1 of 1
Submitted by Andrew Josey, The Open Group. 10th January 2020

Attendees:

    Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR
    Don Cragun, IEEE PASC OR
    Joerg Schilling, FOKUS Fraunhofer
    Andreas Grapentin, HPI, University of Potsdam
    Andrew Josey, The Open Group
    Eric Blake, Red Hat, The Open Group OR 

Apologies
    Geoff Clare, The Open Group
    Mark Ziegast, SHware Systems Dev.

* General news 

None.

* Outstanding actions

(Please note that this section has been flushed to shorten the minutes -
to locate the previous set of outstanding actions, look to the minutes
from 13th June 2019 and earlier)

Bug 1254: "asynchronous list" description uses "command" instead of "AND-OR list" OPEN
http://austingroupbugs.net/view.php?id=1254
Action: Joerg to investigate how his shell behaves.

Bug 700 - Nick to raise this issue with the C committee
Bug 713 - Nick to raise with the C committee.
Bug 739 - Nick to raise with the C committee.
Bug 1216 - Eric to ask if The Open Group is willing to sponsor this interface, referencing bug note 4478.


* Current Business


Bug 1304: Align c99 -o with reality, the standard should not be more restrictive than implementations       Accepted as Marked
http://austingroupbugs.net/view.php?id=1304 

This item is tagged for Issue 8

In the Options, change P2543, L82297-82298 from:

    -o outfile

	Use the pathname outfile, instead of the default a.out, for
	the executable file produced. If the -o option is present
	with -c or -E, the result is unspecified.
to:
    -o outfile

	Name the file produced by the link-editor outfile, instead
	of the default a.out. If a single object file is being
	produced (by using -c with a single input file), name the
	object file outfile instead of the default file.o. If the
	-o option is present with -E, the result is unspecified.

Add the following new paragraphs to Rationale after P2551, L82609:

    <tt>c99 -c -o ...</tt> is frequently used to directly place the
    .o file into an alternative directory without a need to separately
    rename the output file. This helps to support concurrent
    compilations and out of tree builds.

    Some implementations allow -c -o directory to produce
    directory/file.o even when there is more than one input file;
    however, portable applications using -c with -o must compile
    only one file at a time and must specify the final destination
    filename rather than a directory.

Bug 1306: Documented folder= behaviour contradicts implementations (of folders command) Accepted 
http://austingroupbugs.net/view.php?id=1306

This item is tagged TC3-2008 

An interpretation required. Andrew took an action to start the interpretation.

Interpretation response:

The standard states that a null option-argument to the folders
command must produce an error, and conforming implementations must
conform to this. However, concerns have been raised about this which
are being referred to the sponsor.

Rationale:
This is not the way existing implementations behave.

Notes to the Editor (not part of this interpretation):
    Make the changes suggested in the Desired Action. 


Next Steps 
----------

Apologies in advance:
    Geoff Clare  2020-01-09
    Mark Ziegast  2020-01-09

The next calls are on:

January 13 2020 (Monday)
This call will be for 60 minutes.

January 16 2019 (Thursday)
This call will be for 90 minutes.

Calls are anchored on US time. (8am Pacific) 

Please check the calendar invites for dial in details.
http://austingroupbugs.net

An etherpad is usually up for the meeting, with a URL using the date format as below:

https://posix.rhansen.org/p/201x-mm-dd
username=posix password=2115756#