Minutes of the 19 July 2012 Teleconference Austin-564 Page 1 of 1 Submitted by Eric Blake. 19 July, 2012 Attendees Mark Brown, IBM, TOG OR Don Cragun, PASC OR Joerg Schilling, Fraunhofer Society Nick Stoughton, USENIX, ISO/IEC OR Jim Pugsley, Oracle Eric Blake, Red Hat Apologies Geoff Clare, The Open Group Andrew Josey, The Open Group * Old Business +Bug 0000561: NUL-termination of sun_path in Unix sockets OPEN http://austingroupbugs.net/view.php?id=561 We agreed to leave this open as Eric plans to update the proposal. +mbsnrtowcs() discussion OPEN We agreed to leave this open as Nick plans to file a defect report. +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 0000576: No format specifiers for several types. OPEN http://austingroupbugs.net/view.php?id=576 There is still some discussion on the reflector on this item. Nick agree to raise the matter with the C committee. +Bug 0000591: No reason for OH margins in the synopses of open and creat Accepted for TC2 Eric has an action to create a new bug for any further uses of OH margin marking for Issue 8 http://austingroupbugs.net/view.php?id=591#c1279 * Current Business The meeting began with a question of whether the committee should revisit the idea of standardizing strlcpy(), now that C11 under __STDC_LIB_EXT1__ (Annex K) defines strncpy_s(). glibc still refuses to implement strlcpy() on the grounds that correctly using strlcpy() uses more code than using memcpy() in the first place. There was no consensus on adding anything more than C11 interfaces to Issue 8, although it may be worth adding rationale for why strlcpy() is excluded. Bug 0000554: Five(?) clarifications of the informal regex descriptions Open http://austingroupbugs.net/view.php?id=554 The remainder of the meeting was spent on this bug, and the group achieved consensus on wording for 4 of the 5 points in the scope of the bug. It was agreed to leave it open for another week to complete the fifth point and address any further comments that might be raised. So far, the proposed changes include: In response to item 1: Change p. 182, lines 5842-5848, of POSIX.1-2008 from: In the regular expression processing described in POSIX.1-2008, the is regarded as an ordinary character and both a and a non-matching list can match one. The Shell and Utilities volume of POSIX.1-2008 specifies within the individual descriptions of those standard utilities employing regular expressions whether they permit matching of characters; if not stated otherwise, the use of literal characters or any escape sequence equivalent produces undefined results. to In the functions processing regular expressions described in the System Interfaces volume of POSIX.1-2008, the is regarded as an ordinary character and both a and a non-matching list can match one. The Shell and Utilities volume of POSIX.1-2008 specifies within the individual descriptions of those standard utilities employing regular expressions whether they permit matching of characters; if not stated otherwise, the use of literal characters or any escape sequence equivalent in either patterns or matched text produces undefined results . In response to item 2: At both p. 184, line 5984-5896 AND p. 189, line 6106-6109 of POSIX.1-2008 change The shall be special when used as: - An anchor (see Section XXX on page YYY) - The first character of a bracket expression (see Section AAA on page BBB) to The shall be special when used as an anchor (see Section XXX, on page YYY). The shall signify a non matching list expression when it occurs first in a list, immediately following a (see Section AAA on page BBB). In response to item 3: Change p. 188, lines 6082-6083 from: The interpretation of an ordinary character preceded by a ('\\') is undefined. to: The interpretation of an ordinary character preceded by a ('\\') is undefined, except in the context of a bracket expression (see XREF to ERE bracket expression). In response to item 4: On p. 188, change lines 6098-6099 from: -- If these characters appear first in an ERE, or immediately following a , , or to: -- If these characters appear first in an ERE, or immediately following an unescaped , , , or Action: Eric to create a new bug for clarification of 'line' vs. 'string' in regards to anchoring, such as at line 6053. Next Steps ---------- The next call is on July 26 and will continue processing defect reports. This call will be for the regular 90 minutes. http://austingroupbugs.net See the calendar for the list of dialup numbers. An IRC channel will be available for the meeting irc://irc.freenode.org/austingroupbugs