Minutes of the 10th September 2015 Teleconference Austin-728 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 11th September 2015 Attendees: Andrew Josey, The Open Group Don Cragun, IEEE PASC OR Mark Ziegast, SHware Systems Margot Hackett Miller, Oracle Joerg Schilling, FOKUS Fraunhofer Roger Faulkner, Oracle, The Open Group OR Geoff Clare, The Open Group Martin Rehak, Oracle Eric Blake, Red Hat Richard Hansen, BBN David Clissold, IBM Jim Grisanzio, Oracle Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR Apologies Martin Rehak, Oracle ------------------ * General news We discussed progress on the merged draft, and it was agreed that we should hold an internal review prior to the ballots. Andrew has finalized the recent interpretations in the queue except for bug 964 which should be discussed today. * 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 26 Feb 2015) Bug 0000887: printf and other functions appear many times in search results OPEN http://austingroupbugs.net/view.php?id=887 Andrew is investigating. Bug 0000900: add qsort_r OPEN http://austingroupbugs.net/view.php?id=900 The consensus was that its a good idea to add the suggested interface. The usual requirements regarding a sponsor for a new interface apply. Action: Open Group OR , to ask the Base WG if they wish to sponsor the additional qsort interface proposed here. Bug 0000901: reserve _POSIX* shell option namespace for future use OPEN http://austingroupbugs.net/view.php?id=901 The forward plan for this bug remains as before: Richard: file a new bug report with a concrete feature that would use the _POSIX* namespace (as motivation for reserving set -o _POSIX*) All: debate the proposed feature. If it's something we want, then revisit bug #901. If not, close bug #901. Bug 0000922: Implementations should be allowed to change/remove implementation-defined environment variables OPEN http://austingroupbugs.net/view.php?id=922 This item remains open. Action on Eric: propose wording for Issue 8 to add secure_getenv(), and make it clear that deleting from environment without explicit request is not compliant, but ignoring is fine. For Issue 7 TC 2: Create new bug to add additional conditions on what makes TMPDIR valid, vs. undefined behavior; also add future directions to getenv() to mention secure_getenv() * Current Business Bug 964: should m4 treat mkstemp failure as an error? http://austingroupbugs.net/view.php?id=964 There was a comment made during the bug 964 interpretation review. Notes from Geoff's mail to Austin Core, regarding options for this bug, either 1. Approve the interpretation as-is and raise a separate bug for the m4exit(0) issue, targeting Issue 8. This new bug could be resolved as an interpretation saying the standard is silent on the m4exit(0) issue. 2. Update the interpretation to add a change saying it is unspecified whether the exit status is zero or non-zero if m4exit(0) is called when a normal exit would have resulted in a non-zero exit status. We would have to restart the interpretation timer; if it is not approved before the TC2 merge is finished we could include it in the TC2 draft but with a note to reviewers explaining that it is from an interpretation that is still in review. The revised response is now: Due to issues raised during the earlier interpretation review process, this new interpretation is being proposed and the timer will be restarted: Interpretation response: The standard does not speak to this issue, and as such no conformance distinction can be made between alternative implementations based on this. This is being referred to the sponsor. Rationale: The standard does not clearly specify what should happen if a file cannot be created in this case. Notes to the Editor (not part of this interpretation): Change the description of m4exit from: Exit from the m4 utility. If the first argument is specified, it is the exit code. The default is zero. It shall be an error to specify an argument containing any nonnumeric characters. to: Exit from the m4 utility. If the first argument is specified, it shall be the exit code. If no argument is specified, the exit code shall be zero. It shall be an error to specify an argument containing any nonnumeric characters. If the first argument is zero or no argument is specified, and an error has previously occurred (for example, a file operand that could not be opened), it is unspecified whether the exit status is zero or non-zero. In the EXTENDED DESCRIPTION section, for mkstemp change from: If a file could not be created, the defining text of the macro shall be the empty string. to: If a file could not be created, m4 shall write a diagnostic message to standard error and shall continue processing input but its final exit status shall be non-zero; the defining text of the macro shall be the empty string. The interpretation status has been set to pending, and Andrew has an action to restart the clock. Bug #249: Add standard support for $'...' in shell Accepted as Marked http://austingroupbugs.net/bug_view_page.php?bug_id=249 We continued the discussions from the previous week See http://posix.rhansen.org:9001/p/bug249 We will continue with this next week. Next Steps ---------- The next call is on September 17, 2015 (a Thursday) Calls are anchored on US time. (8am Pacific) This call will be for the regular 90 minutes. http://austingroupbugs.net An IRC channel will be available for the meeting irc://irc.freenode.net/austingroupbugs An etherpad is usually up for the meeting, with a URL using the date format as below: http://posix@posix.rhansen.org:9001/p/201x-mm-dd password=2115756#