Minutes of the 12 January 2012 Teleconference Austin-546 Page 1 of 1 Submitted by Andrew Josey, The Open Group. January 14 , 2012 Attendees Andrew Josey, The Open Group Don Cragun, PASC OR Mark Brown, IBM, TOG OR Geoff Clare, The Open Group Joerg Schilling, Fraunhofer Society Nick Stoughton, USENIX, ISO/IEC OR Eric Blake, Red Hat Apologies Jim Pugsley, Oracle The TC1-2008 Draft 4 document merger into the Base Specs is still progressing, with more progress expected to be made over the next few weeks . * Old Business Bug 000073 wmemcmp C conflict? Accepted as Marked http://austingroupbugs.net/view.php?id=73 Nick has completed his action in bugnote 1083. An interpretation is required. This item is tagged for TC2-2008. Interpretation response The standard is unclear on this issue, and no conformance distinction can be made between alternative implementations based on this. This is being referred to the sponsor. Rationale: A clarification has been made in the C11 standard and POSIX will adopt this wording in the next Technical Corrigendum. Since defect reports are no longer accepted against C99 this change in C11 is being taken as if it were a response to a C99 defect report. Notes to the Editor (not part of this interpretation): Add to XBD Page 454, line 15482: "Arguments to functions in this list can point to arrays containing wchar_t values that do not correspond to members of the character set of the current locale. Such values shall be processed according to the specified semantics, unless otherwise stated." Add the following sentence "It is unspecified whether an encoding error occurs if the format string contains wchar_t values that do not correspond to members of the character set of the current locale and the specified semantics do not require that value to be processed by wcrtomb()." to: page 973 line 32587 (fwprintf, swprintf, wprintf) page 983 line 32960 (fwscanf, swscanf, wscanf) Add the following sentence "It is unspecified whether an encoding error occurs if the format string contains wchar_t values that do not correspond to members of the character set of the current locale." to page 2207 line 69521 (wcsftime) Bug 0000251: Forbid newline, or even bytes 1 through 31 (inclusive), in filenames OPEN http://austingroupbugs.net/view.php?id=251 Don reported that he was still working on a proposal to address this and related bugs. *New business Bug 0000531: Inclusion of may make visible symbols defined in Accepted http://austingroupbugs.net/view.php?id=531 This item is tagged for TC2-2008 Bug 0000532: clarify atomicity of semctl() Accepted as Marked http://austingroupbugs.net/view.php?id=532 This item is tagged for TC2-2008 Add the following new paragraph after the line 58506: Each operation shall be performed atomically. Bug 0000533: backslash newline in sed s replacement string Accepted http://austingroupbugs.net/view.php?id=533 This item is tagged for TC2-2008 Bug 0000534: unclear phrasing in "mv" regarding same source and destination file Description Accepted http://austingroupbugs.net/view.php?id=534 This item is tagged for TC2-2008 Bug 0000535: require support for path separator in function and alias names Rejected http://austingroupbugs.net/view.php?id=535 Making this change would open up a security hole, since existing scripts count on the use of to bypass any alias or function names in order to ensure they are executing the intended binary. Additionally, the use of such a function name would not propagate to child processes that directly execute the path name that had been intended to be covered by the function. Bug 0000536: missing statement from C99 about no need to generate signals Accepted http://austingroupbugs.net/view.php?id=536 This item is tagged for TC2-2008 Bug 0000529: fildes unspecified on close()'s [EINTR] OPEN http://austingroupbugs.net/view.php?id=529 This item has been filed against the wrong Category. Action: mark to move from 2008-TC1 to 1003.1(2008)/Issue 7. Bug 0000527: du and files found via multiple command line arguments OPEN http://austingroupbugs.net/view.php?id=527 We will continue with this item next time. Next Steps ---------- The next call is on January 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 ICAL: http://www.google.com/calendar/ical/nvctqtstkuni3fab9k3jqtrt4g@group.calendar.google.com/public/basic XML: http://www.google.com/calendar/feeds/nvctqtstkuni3fab9k3jqtrt4g@group.calendar.google.com/public/basic