Austin Group Minutes of the 20 Sep 2007 Teleconference Austin-398 Page 1 of 1 Submitted by Andrew Josey, The Open Group. Sep 21, 2007 Attendees Andrew Josey, The Open Group Don Cragun , Sun, PASC OR Geoff Clare, The Open Group Mark Brown, IBM, TOG OR Ulrich Drepper, Red Hat Nick Stoughton, USENIX, ISO/IEC OR Apologies Eric Blake Mats Wichmann, Intel We picked up at the recent interpretations. See https://www.opengroup.org/austin/interps/protected/ This is an ongoing attempt to ensure we get as many fixes into draft D4R as we can.. A comment was raised by Geoff on last weeks minutes: * Austin-148 wordexp() thread safety / XSHbug2 ERN 225 -start quote- > > Austin-148 wordexp() thread safety / XSHbug2 ERN 225 [...] > > An extra para to APP USAGE of wordexp() > > This standard does not require the wordexp() function to be thread safe > if passed an expression referencing an environment variable and while > any other thread is concurrently modifying any environment variable > (xref to exec in XSH). In the call we agreed that the "and while" in this text should be just "while". -end quote- It was agreed that Andrew should update the aardvark and the interpretation. * Austin-016 Pathname Resolution --start quote-- > Austin-016 [...] > > An additional change was also indentified for XSH mkdir(). > > On XSH mkdir DESCRIPTION. > Add a new sentence after > "The mkdir( ) function shall create a new directory with name path." > > If path resolves to a symbolic link , mkdir shall expand the symbolic link > creating the directory named by the final component of the symlink I thought that in the end we decided an addition for mkdir() wasn't needed. --end quote-- We agreed that it was not needed. Andrew to make the corrections to AI-016 * Austin-161 fprintf 0 flag There was discussion about the words proposed for the interpretation response. It was agreed to change the response as follows: The standard states the requirements for fprintf which conflict with the ISO C standard. concerns have been raised about this which are being referred to the sponsor. Andrew will update update Austin-161 * Austin-143 ENAMETOOLONG It was agreed that we should add additional rationale to XRAT Add to XRAT for A.4.11 (in D3R A.4.12) When the standard says "Pathname resolution for a given pathname shall yield the same results when used by any interface in this standard as long as there are no changes to any files evaluated during pathname resolution for the given pathname between resolutions", this applies to abolute pathnames or to relative pathnames from the same current working directory. Using the same relative pathname from two different working directories may yield different results. Andrew to update the interprettaion We then moved back to the 2004 aardvark reports http://www.opengroup.org/austin/aardvark/latest/ XBDbug2.txt ERN 45,46,47 complex.h ISO C TC2 changes Reject These were changes required for ISO C TC2, that we had raised concerns with, resulting in ISO C TC3 correcting the situation ERN 53 stddef.h wchar_t definition Accept as marked below ISO C committee has taken the change with a different name. In stddef.h Replace wchar_t entry with the new para as follows: wchar_t which is an integer type whose range of values can represent distinct codes for all members of the largest extended character set specified among the supported locales; the null character shall have the code value zero. Each member of the basic character set shall have a code value equal to its value when used as the lone character in an integer character constant if an implementation does not define __STDC_MB_MIGHT_NEQ_WC__. Add to CH The definition of wchar_t is updated to align with ISO C TC3. Note relating to this item: A merge of ISO C TC 1,2 and 3 is available at: http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1256.pdf ISO C TC3 passed its ballot, we'll need to review it for changes https://www.opengroup.org/austin/plato/protected/doc.tpl?CALLER=index.tpl&gdid=13534 Action: Mark/Geoff to look at TC3 to determine to determine what change we need to make to D3. ERN 64 XBD 4.10 Reject The C committee is currently entertaining proposals in this area and we do not want to diverge from anything that they do, so we will wait on them. ERN 68 limits.h TRACE_NAME_MAX, TRACE_EVENT_NAME_MAX Accept ERN 83 TMP_MAX conflict with ISO C Accept as marked Send down the interpretations track This is in conflict with the ISO C standard, and a defect report has been forwarded to them . Add rationale in the D3R, that There is a conflict between the ISO C and the POSIX definition of the TMP_MAX macro that is addressed by ISO C defect report 336. The POSIX standard is in alignment with the public record of response of the defect report. This changes has not yet been published as part of the C Standard. The DR reference is 336 http://www.open-std.org/jtc1/sc22/wg14/www/docs/dr_336.htm (Ask Cathy in the interp to embed a note in the source saying that in Issue 8 we hope to remove this piece of rationale text) ERN 87 numerical floating limits accept Go down SD5 track as an editorial It was agreed to start the next meeting at XBD ERN 88 Next Steps ----------- Andrew will update the aardvark reports with the latest inbound defect reports. The next meeting is the 27th September, 15:30 start. See http://www.opengroup.org/austin/. An IRC channel will be available for the meeting irc://irc.freestandards.org #austin irc://irc.freestandards.org/austin 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