Minutes of the 7th April 2016 Teleconference Austin-756 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 9th April 2016 Attendees: Richard Hansen Eric Blake, Red Hat Don Cragun, IEEE PASC OR Roger Faulkner, Oracle, The Open Group OR Geoff Clare, The Open Group Martin Rehak, Oracle David Clissold, IBM Mark Ziegast, SHware Systems Dev. Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR Joerg Schilling, FOKUS Fraunhofer Andrew Josey, The Open Group (joined late) * General news IEEE and The Open Group balloting on TC2 closed on April 1st. At IEEE there was 90% return and 78% approval. Four comments were received, pointing to bug report 1035. We plan to have a 10 day recirculation review with that one change. Andrew has been in contact with the IEEE staff liaison, and was informed that there is an IEEE public review running on the draft until close of business on 23 April. We decided we will wait until after that date before proceeding with a recirculation. Andrew will take an action to inform the PASC SEC and The Open Group of the current status. An interim copy of the merged draft had been producing with the macro \(aq used for the single quote character used. Geoff had highlighted a number of areas where single quote characters still need to be switched to the macro, and that work needs to be scheduled. Andrew will circulate the previous final front matter from TC1 so we can assess the use of the single quote character in it. * 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 28 Jan 2016) * Current Business Bug #249: Add standard support for $'...' in shell Reopened http://austingroupbugs.net/bug_view_page.php?bug_id=249 We will return to bug 249 on a future call. Bug #957: Add an extended set of exit status codes Rejected http://austingroupbugs.net/view.php?id=957 This was discussed at length and rejected. Since the standard does not reserve EXIT_ as a prefix for , adding these symbols to that header could potentially break existing applications. In addition, no known implementation defines those constants in . It may be reasonable to standardize as-is, but this would require sponsorship and no organization was willing to sponsor that addition. Additional concerns about the usage of these identifiers in portable applications (both shell scripts and C code), were brought up and in some cases seen as requiring invention to accommodate: There is no way provided for an application to translate an exit value into a meaningful description of why that value was returned (there is no analogue to strerror()). There is no guarantee that two applications using these exit codes would get agreement on the values returned by cooperating processes on different systems unless the values were included in the standard. No way was suggested by the submitter to reserve namespaces for additional constants to be added by implementations in the future with consistent values. It is unclear whether the standard utilities would have to be modified to use these values, or avoid the use of values in the range EXIT__BASE to EXIT__MAX for unrelated causes. Bug #961: permit to terminate {...} command Accepted http://austingroupbugs.net/view.php?id=961 This item is tagged for Issue 8 Next Steps ---------- The next call is on April 14, 2016 (a Thursday) Apologies in advance Richard Hansen 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#