Minutes of the 31st October 2012 Teleconference Austin-583 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 2 November, 2012 Attendees Don Cragun, PASC OR Andrew Josey, The Open Group (partial) Geoff Clare, The Open Group Eric Blake, Red Hat Nick Stoughton, USENIX, ISO/IEC OR Jim Pugsley, Oracle Apologies Joerg Schilling, Fraunhofer Society Mark Brown, IBM, TOG OR * General News Andrew reported that The Open Group Governing Board had approved TC1 at last weeks meeting. A comment had also been received from IEEE Revcom which will need to be responded to. This was about whether the base standard had been circulated with the ballot. The TC1 document includes both old wording and new wording, and the merged document shows the effect of the base standard with the changes - so we think that covers it. We decided to wait for another week to hear back from the IEEE staff liaison (the IEEE site was unavailable during the meeting possibly due to the storms on the East coast). * Old Business +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 This item needs further investigation of existing implementations. Mark reported that AIX does not have a problem with this. Jim notes he is still looking at this. +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 0000576: No format specifiers for several types OPEN http://austingroupbugs.net/view.php?id=576 Bug 0000599: Reserved "no thread" value for pthread_t A/M Issue 8 Bug 0000517: EBNF support OPEN http://austingroupbugs.net/view.php?id=517 It was agreed that we need Joerg's input on this item and have left it open for now. Andrew took an action on the 12 September call to notify Joerg (completed after the meeting). * Current Business Bug 0000612: dirname of "usr/" or "/" are not clear Accepted as Marked http://austingroupbugs.net/view.php?id=612 This item is tagged for TC2-2008 To fix the problem reported in this bug: Change the last sentence of the first paragraph of the dirname DESCRIPTION on P725, L24372-24373 from: Trailing ’/’ characters in the path are not counted as part of the path. to: Trailing ’/’ characters in the path that are not also leading '/' characters shall not be counted as part of the path. To more closely align the descriptions of baseame() and dirname(): Add a new paragraph in the dirname() DESCRIPTION section after P725, L24375: The dirname() function may modify the string pointed to by path, and may return a pointer to static storage that may then be overwritten by a subsequent call to dirname(). To make it obvious that the basename() and dirname() functions and the basename and dirname utilities are closely related, make the following additions and changes to EXAMPLES and SEE ALSO sections: Change P614, L20996-21004 in the basename() EXAMPLES section from: Sample Input and Output Strings for basename() In the following table, the input string is the value pointed to by path, and the output string is the return value of the basename() function. Input String Output String ============== ============= "/usr/lib" "lib" "/usr/" "usr" "/" "/" "///" "/" "//usr//lib//" "lib" to: Sample Input and Output Strings for the basename() and dirname() functions and the basename and dirname utilities In the following table, the input string is the value pointed to by path, and the output string is the return value of the basename() function. output output basename written written basename() and string string and dirname by by dirname() functions returned by returned by utilities basename dirname path argument basename() dirname() string operand utility utility ================== =========== ============ ================ ======== ========== "usr" "usr" "." usr usr . "usr/" "usr" "." usr/ usr . "" "." "." "" NOTE . "/" "/" "/" / / / "//" "/" or "//" "/" or "//" // / or // / or // "///" "/" "/" /// / / "/usr/" "usr" "/" /usr/ usr / "/usr/lib" "lib" "/usr" /usr/lib lib /usr "//usr//lib//" "lib" "//usr" //usr//lib// lib //usr "/home//dwc//test" "test" "/home//dwc" /home//dwc//test test /home//dwc Note to the editor: Change "NOTE" in the above table to ". or empty string" split into multiple lines if needed under the heading "output written by basename utility". Change the "Sample Input and Output Strings for dirname()" example in the dirname() EXAMPLES on P726, L24404-24413 to: The EXAMPLES section of the basename() function (see XREF basename() EXAMPLES section on page XXX) includes a table showing examples of the results of processing several sample pathnames by the basename() and dirname() functions and by the basename and dirname utilities. Add a new paragraph at the end of the basename utility's EXAMPLES section after P2465, L78660: The EXAMPLES section of the basename() function (see XREF to XSH basename() EXAMPLES section) includes a table showing examples of the results of processing several sample pathnames by the basename() and dirname() functions and by the basename and dirname utilities. Add a new paragraph at the end of the basename utility's SEE ALSO section after P2466, L78676: XSH basename(), Change the table in the dirname utility's EXAMPLES section on P2609, L84125-84135 to: The EXAMPLES section of the basename() function (see XREF to XSH basename() EXAMPLES section) includes a table showing examples of the results of processing several sample pathnames by the basename() and dirname() functions and by the basename and dirname utilities. Add a new paragraph to the end of the dirname utility's SEE ALSO section after P2610, L84154: XSH dirname() Bug 0000609: It is not clear what threads are considered blocked with respect to a call to pthread_cond_signal() or pthread_cond_broadcast() OPEN http://austingroupbugs.net/view.php?id=609 This was discussed in length on the call. It was felt that the direction to require fully atomic behaviour is the right direction, however we need feedback on the internals of existing implementations to see whether pthread_cond_signal() and pthread_cond_broadcast() are already or can be made atomic. Action: Jim to provide feedback on Solaris Action: Andrew to contact HP/IBM/Apple This item was left open for now. Next Steps ---------- The next call is on November 7. 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.net/austingroupbugs