Minutes of the 15th August 2013 Teleconference Austin-622 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 19th August 2013 Attendees Don Cragun, PASC OR Geoff Clare, The Open Group Joerg Schilling, Fraunhofer Society David Clissold, IBM Mark Brown Mark Ziegast Richard Hansen, BBN Nick Stoughton, USENIX, ISO/IEC OR Eric Blake, Red Hat Apologies Andrew Josey, The Open Group * General news No general news. * Outstanding actions +Bug 0000251: Forbid newline, or even bytes 1 through 31 (inclusive), in filenames OPEN http://austingroupbugs.net/view.php?id=251 Don has an action to produce a proposal. +Bug 0000561: NUL-termination of sun_path in Unix sockets OPEN http://austingroupbugs.net/view.php?id=561 Eric has an action to update the proposal. +Bug 0000573: Please add '+' to the portable filename character set OPEN http://austingroupbugs.net/view.php?id=573 Joerg has an action to prepare a proposed change. +Bug 0000592: consistent use of struct timespec OPEN http://austingroupbugs.net/view.php?id=592 Jim had provided additional information in bugnote 1627. This was discussed and Jim took an action to provide further information. +Bug 0000598: OH shading and new interfaces OPEN http://austingroupbugs.net/view.php?id=598 Eric has an action to propose a new solution with self-contained headers. +Bug 0000517: EBNF support OPEN http://austingroupbugs.net/view.php?id=517 Action on Joerg to look at this. +Bug 0000633: SIGEV_THREAD delivery renders many signal interfaces unsafe OPEN http://austingroupbugs.net/view.php?id=633 We noted that feedback has settled down on the mailing list, and will discuss next session. +Bug 0000657: Conditions under which fmemopen() write a NUL to the buffer are insufficiently specified OPEN http://austingroupbugs.net/view.php?id=657 Eric has an action to propose wording to clarify the behavior for fmemopen(), and also to contact the glibc developers to get their feedback. +Bug 0000658: Undefined/unspecified behavior clauses in description of open have race conditions OPEN http://austingroupbugs.net/view.php?id=658 It was noted that there is some overlap with changes in TC1. Eric took an action to update the proposal to resolve the overlaps appropriately. +Bug 0000615: pthread_setcancelstate should be async-signal-safe OPEN http://austingroupbugs.net/view.php?id=615 We now have reports on AIX and Apple. Jim to report back on whether pthread_cancelstate() is async-signal-safe on Solaris. Andrew to ask HP whether pthread_cancelstate() is async-signal-safe on HP-UX. +Bug 622 left open pending resolution of 615. http://austingroupbugs.net/view.php?id=622 +Bug 0000672: Necessary step(s) to synchronize filename operations on disk OPEN http://austingroupbugs.net/view.php?id=672 Geoff has a new proposed resolution in note 1618. Decided to solicit input from FS developers. Eric to go to Linux, David to AIX and Jim to Solaris. Jim has completed his action (see bugnote 1691). Andrew should chase HP and Apple for input. +Bug 0000663: Specification of str[n]casecmp is ambiguous reopened http://austingroupbugs.net/view.php?id=663 Action on David to follow up with the IBM developers about the EBCDIC collation sequence. Bug 696 either NAME_MAX shouldn't be optional, or readdir_r() needs clarification http://www.austingroupbugs.net/view.php?id=696 Don has an action to propose a resolution. Bug 0000721: Internal storage vs static storage OPEN http://austingroupbugs.net/view.php?id=721 This item is still open. * Current Business Bug 0000730: Typo in test(1) page (en -> an) Accepted http://austingroupbugs.net/view.php?id=730 This item is tagged for TC2-2008 Bug 0000731: split: Behavior when input file is empty Accepted as Marked http://austingroupbugs.net/view.php?id=731 This item is tagged for TC2-2008 An interpretation is required. Interpretation response: The standard states that split produces one or more output files, and conforming implementations must conform to this. However, concerns have been raised about this which are being referred to the sponsor. Rationale: When the input is an empty file, historical practice has been to produce no output files. We see no reason why conforming implementations should be required to created an empty output file in this case. Notes to the Editor (not part of this interpretation): In the NAME section, change: "split files into pieces" to: "split a file into pieces" In the SYNOPSIS section, change "[file[name]]" on both lines to "[file [name]]". Change "one or more" in the DESCRIPTION section on P3217, L107808 to "zero or more", Add to the end of the paragraph on P3217, L107821: "If the input is an empty file, no output file shall be created and this shall not be considered to be an error." Bug 0000733: Volatile qualification of sig_atomic_t is ambigiuous Accepted as Marked http://austingroupbugs.net/view.php?id=733 This item is tagged for TC2-2008 At page 546 line 18989 section 2.12.1 in the description of sig_atomic_t change: Integer type to Possibly volatile-qualified integer type Note that C99 and C11 say that the implementation can choose whether to make sig_atomic_t a typedef of a volatile- or non-volatile-qualified integer type, but where the standard explicitly uses volatile as a qualifier we require it to be volatile. Thus, the "possibly" when discussing the definition of the type does not conflict with the need to declare 'volatile sig_atomic_t'. Bug 0000734: Wrong indefinite article. Accepted http://austingroupbugs.net/view.php?id=734 This item is tagged for TC2-2008 Next Steps ---------- The next call is on August 22, 2013 (a Thursday) Calls are anchored on US time. 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