Minutes of the 12 February 2015 Teleconference Austin-695 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 13 February 2015 Attendees: Mark Ziegast, SHware Systems Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR Joerg Schilling, FOKUS Fraunhofer Geoff Clare, The Open Group David Clissold, IBM Martin Rehak, Oracle, The Open Group OR Richard Hansen, BBN Eric Blake, Red Hat Don Cragun, IEEE OR Andrew Josey, The Open Group Apologies: * General news On the PASC PAR approval, there is now a sense of urgency, as we need to have an active project at IEEE. Andrew has updated the PAR and the PMC criteria and circulated them (after the meeting) to the PASC SEC. The draft PAR and PMC criteria are also checked into the document register as Austin/693 and Austin/694. Nick will call a vote and a provisional meeting of the PASC SEC to discuss the PAR - this is anticipated to be in 30 days time, and would be the last 30 minutes of a scheduled Austin Group teleconference. * 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 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. Bug 0000375: Extend test/[...] conditionals: ==, <, >, -nt, -ot, -ef OPEN http://austingroupbugs.net/view.php?id=375 This is still left open due to discussions pending on the reflector. Bug 0000789: Add set -o pipefail OPEN http://austingroupbugs.net/view.php?id=789 * Current Business Bug #920: missing %F description in strptime Accepted as Marked http://austingroupbugs.net/view.php?id=920 This bug is marked for TC2-2008 An interpretation is required. Interpretation response: The standard states the requirements for field widths in strptime(), and conforming implementations must conform to this. However, concerns have been raised about this which are being referred to the sponsor. Rationale: The standard states that the behavior of field widths is unspecified for conversions other than C, F, or Y, but does not specify an F conversion. Notes to the Editor (not part of this interpretation): On Page: 2041 Line: 65181 Section: strptime() In the DESCRIPTION section, change from: ... conversion specifier other than C, F, or Y. to: ... conversion specifier other than C or Y. Bug #879: strptime is missing conversion specifiers described in strftime Accepted as Marked http://austingroupbugs.net/view.php?id=879 This item is tagged for Issue 8. On page 2041 line 65181 (strptime() DESCRIPTION), after applying the change for 0000920, change: or if a field width is specified for any conversion specifier other than C or Y. to: or if a field width is specified for any conversion specifier other than C, F, G, Y, or Z. On page 2042 after line 65194 (strptime() DESCRIPTION) insert: F This specifier is similar to %Y-%m-%d where the characters up to the first separator shall be converted as for %Y but with unlimited field width, the characters between the two separators shall be converted as for %m, and the characters after the last separator shall be converted as for %d. If a field width is specified, each of the %Y, %m, and %d conversions shall not convert any characters past the overall %F field width. g The last 2 digits of the week-based year (see below) as a decimal number (for example, 77). Leading zeros shall be permitted but shall not be required. A leading '+' or '-' character shall be permitted before any leading zeros but shall not be required. The effect of this year, if any, on the tm structure pointed to by tm is unspecified. G The week-based year (see below) as a decimal number (for example, 1977). Leading zeros shall be permitted but shall not be required. A leading '+' or '-' character shall be permitted before any leading zeros but shall not be required. The effect of this year, if any, on the tm structure pointed to by tm is unspecified. On page 2042 after line 65212 insert: u The weekday as a decimal number [1,7], with 1 representing Monday. On page 2042 line 65214 add a sentence to the U conversion: The effect of this week number, if any, on the tm structure pointed to by tm is unspecified. On page 2042 after line 65214 insert: V The week number of the week-based year (see below) as a decimal number [01,53]. Leading zeros shall be permitted but shall not be required. The effect of this week number, if any, on the tm structure pointed to by tm is unspecified. On page 2042 line 65217 add a sentence to the W conversion: The effect of this week number, if any, on the tm structure pointed to by tm is unspecified. On page 2043 after line 65230 insert: z The offset from UTC in the ISO 8601:2004 standard format (+hhmm or -hhmm). For example, "-0430" means 4 hours 30 minutes behind UTC (west of Greenwich). The effect of this offset, if any, on the tm structure pointed to by tm is unspecified. Z The timezone name. If this name matches tzname[1], and tzname[0] and tzname[1] differ, then the tm_isdst field of the tm structure pointed to by tm shall be set to 1. Otherwise, if this name matches tzname[0] then the tm_isdst field of the tm structure pointed to by tm shall be set to 0. Any other effects on the tm structure pointed to by tm are unspecified. On page 2043 after line 65252 insert: %OV The same as %V but using the locale's alternative numeric symbols. On page 2043 after line 65257 insert: %g, %G, and %V convert values according to the ISO 8601:2004 standard week-based year. In this system, weeks begin on a Monday and week 1 of the week-based year is the week that includes January 4th, which is also the week that includes the first Thursday of the year, and is also the first week that contains at least four days in the year. If the first Monday of January is the 2nd, 3rd, or 4th, the preceding days are part of the last week of the preceding week-based year (thus, the string "1998 53 6" with format specifier "%G %V %u" represents Saturday 2nd January 1999). If December 29th, 30th, or 31st is a Monday, it and any following days are part of week 1 of the following week-based year (thus, the string "1998 01 2" with format specifier "%G %V %u" represents Tuesday 30th December 1997). Next Steps ---------- The next call is on February 19, 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#