Minutes of the 29th April 2019 Teleconference Austin-929 Page 1 of 1 Submitted by Geoff Clare, The Open Group. 30th April 2019 Attendees: Mark Ziegast, SHware Systems Dev. Joerg Schilling, FOKUS Fraunhofer Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR Don Cragun, IEEE PASC OR Geoff Clare, The Open Group Eric Blake, Red Hat, The Open Group OR Apologies: Andrew Josey, The Open Group * 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 9 March 2018 and earlier) Bug 1077: Recommend support for wide-character regcomp and regexec and/or specify multi-byte behavior OPEN http://austingroupbugs.net/bug_view_page.php?bug_id=1077 Andrew has completed the action to ping his Apple contact and is awaiting a reply. Bug 1122: POSIX should include gettext() and friends OPEN http://austingroupbugs.net/view.php?id=1122 Left open as an action is still in progress to flesh out a complete proposal. Bug 1218: Add reallocarray() OPEN http://austingroupbugs.net/view.php?id=1218 Action: Eric to ask if The Open Group is willing to sponsor this interface. A full set of changes would need to be developed. Bug 1219: snprintf requirement to fail when n > INT_MAX conflicts with C OPEN http://austingroupbugs.net/view.php?id=1219 Action: Nick (on his return) to ask C committee for guidance, whether an n > INT_MAX but less than SIZE_MAX, where SIZE_MAX is between, inclusively, INT_MAX+1 and UINT_MAX (or higher on 64-bit architectures) may be a preemptive reason to fail the interface, without examining any other arguments. Bug 1220: Add an API to query the name of a locale category of a locale object OPEN http://austingroupbugs.net/view.php?id=1220 Action: Eric to ask if The Open Group is willing to sponsor this interface. * Current Business Bug 931: mark encrypt, setkey as OBS Duplicate http://austingroupbugs.net/view.php?id=931 A note had been added to bug 1192 pointing out that its resolution overlapped with that of bug 931. Since the changes in 1192 are a superset of those in bug 931 (apart from a trivial variation of the future directions wording), this was addressed by updating 931 to be marked as a duplicate of 1192. Bug 1222: "echo" specification doesn't reflect current implementations (missing -e, -E and - handling) Accepted as Marked http://austingroupbugs.net/view.php?id=1222 This item is tagged for Issue 8 On page 2674 line 87124 section echo OPERANDS, change: If the first operand is -n, or if any of the operands contain a character, the results are implementation-defined. [XSI]On XSI-conformant systems, if the first operand is -n, it shall be treated as a string, not an option.[/XSI] to: If the first operand consists of a '-' followed by one or more characters from the set { 'e', 'E', 'n' }, or if any of the operands contain a character, the results are implementation-defined. [XSI]On XSI-conformant systems, if the first operand consists of a '-' followed by one or more characters from the set { 'e', 'E', 'n' }, it shall be treated as a string to be written.[/XSI] On page 2675 line 87179 section echo APPLICATION USAGE, change: It is not possible to use echo portably across all POSIX systems unless both -n (as the first argument) and escape sequences are omitted. to: It is not possible to use echo portably across all POSIX systems unless escape sequences are omitted, and the first argument does not consist of a '-' followed by one or more characters from the set { 'e', 'E', 'n' }. On page 2676 line 87198 section echo RATIONALE, change: Conforming applications that wish to do prompting without characters or that could possibly be expecting to echo a −n, should use the printf utility derived from the Ninth Edition system. As specified, echo writes its arguments in the simplest of ways. The two different historical versions of echo vary in fatally incompatible ways. The BSD echo checks the first argument for the string −n which causes it to suppress the that would otherwise follow the final argument in the output. The System V echo does not support any options, but allows escape sequences within its operands, as described for XSI implementations in the OPERANDS section. The echo utility does not support Utility Syntax Guideline 10 because historical applications depend on echo to echo all of its arguments, except for the −n option in the BSD version. to: Conforming applications that wish to do prompting without characters or that could possibly be expecting to echo a string consisting of a '-' followed by one or more characters from the set { 'e', 'E', 'n' } should use the printf utility. At the time that the POSIX.2-1992 standard was being developed, the two different historical versions of echo that were considered for standardization varied in incompatible ways. The BSD echo checked the first argument for the string −n which caused it to suppress the that would otherwise follow the final argument in the output. The System V echo treated all arguments as strings to be written, but allowed escape sequences within them, as described for XSI implementations in the OPERANDS section, including \c to suppress a trailing . Thus the POSIX.2-1992 standard said that the behavior was implementation-defined if the first operand is -n or if any of the operands contain a character. It also specified that the echo utility does not support Utility Syntax Guideline 10 because historical applications depended on echo to echo all of its arguments, except for the −n first argument in the BSD version. The Single UNIX Specification, Version 1 required the System V behavior, and this became the XSI requirement when Version 2 and POSIX.2 were merged with POSIX.1 to form the joint POSIX.1-2001 / Single UNIX Specification, Version 3 standard. This standard now treats a first operand of -e or -E the same as -n in recognition that support for them has become more widespread in non-XSI implementations. Where supported, -e enables processing of escape sequences in the remaining operands (in situations where it is disabled by default), and -E disables it (in situations where it is enabled by default). A first operand containing a combination of these three letters, in the same manner as option grouping, also results in implementation-defined behavior. Bug 1223: Parameter name in RATIONALE example doesn't match name in code body Accepted as Marked http://austingroupbugs.net/view.php?id=1223 This item is tagged for TC3-2008 On page 1985 line 63887 section sigsuspend(), change: result = sigsuspend(sigmask); to: result = sigsuspend(mask); Bug 1224: Conflict between 2.9.1 and 2.10.2 re simple command terminator Accepted http://austingroupbugs.net/view.php?id=1224 This item is tagged for TC3-2008 Bug 1225: flushing while seeking on memory buffer streams OPEN http://austingroupbugs.net/view.php?id=1225 This item was discussed and will be continued on the next call. Next Steps ---------- The next calls are on: May 2 2019 (Thursday) This call will be for 90 minutes. There will be NO CALL May 6 2019 (Monday) May 9 2019 (Thursday) This call will be for 90 minutes. Calls are anchored on US time. (8am Pacific) Apologies in advance: Andrew Josey 2019-05-02 Eric Blake 2019-05-02 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#