Minutes of the 7 Oct 2010 Teleconference Austin-499 Page 1 of 1 Submitted by Andrew Josey, The Open Group. October 8 , 2010 Attendees Andrew Josey, The Open Group Don Cragun, PASC OR Nick Stoughton, USENIX, ISO/IEC OR Mark Brown, IBM, TOG OR Geoff Clare, The Open Group Joe George, Oracle Darrin Johnson, Oracle Eric Blake, Red Hat Pradhap Devarajan, Sun/Oracle * SC22 Status Keld had raised a correction to last weeks minutes by email. The location of the SC22 meeting was Ottowa, Canada. * Old Business Geoff reported that all the Issue 7 interpretations that were being reviewed as candidates for TC1-2008 are completed. * We picked up on regular Bug processing Bug 0000196: improved getsubopt example Accept as marked. http://austingroupbugs.net/view.php?id=196 This was tagged for Issue 8, however after discussion it was agreed to re-tag for TC1-2008. Bug 0000249: Add standard support for $'...' in shell OPEN http://austingroupbugs.net/view.php?id=249 Don agreed to take an action to propose the changes to address supporting \u and \U. This item is still open and needs more time to complete. Bug 0000327: time_t should be integral Accepted as marked http://austingroupbugs.net/view.php?id=327 This has been tagged for TC1-2008. An interpretation is needed. THE "DEFECT" SITUATION (i.e. the balloting group appears to have gotten it wrong): Interpretation response The standard states that time_t is allowed to be a floating type, and conforming implementations must conform to this. However, concerns have been raised about this which are being referred to the sponsor. Rationale: Although time_t is allowed to be a floating type, all known implementations use an integral type and many applications assume that it is an integral type. Therefore, the C requirement is being strengthened in this standard. Notes to the Editor (not part of this interpretation): Implement the desired action. Bug 0000309: find -exec a b{} {} + Accepted as marked http://austingroupbugs.net/view.php?id=309 Tagged for TC1-2008, and interpretation is needed. 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: Option 2 in the desired action seems the most appropriate. Notes to the Editor (not part of this interpretation): At line 89178 change: If more than one argument containing only the two characters "{}" is present, the behavior is unspecified. to: If more than one argument containing the two characters "{}" is present, the behavior is unspecified. Delete the following text from line 89180 and append it to line 89164: If a utility_name or argument string contains the two characters "{}", but not just the two characters "{}", it is implementation-defined whether find replaces those two characters or uses the string without change. Bug 0000310: Missing word "only" in find -exec description Accepted http://austingroupbugs.net/view.php?id=310 This is tagged for TC1-2008. Bug 0000311: _POSIX2_VERSION and profiles with no shell and utilities Accepted http://austingroupbugs.net/view.php?id=311 This is tagged for TC1-2008. Bug 0000312: not following handle activation rules invokes undefined, not unspecified behavior Accepted as Marked http://austingroupbugs.net/view.php?id=312 This is tagged for TC1-2008. Since lines 16842-16843 cover both handles, it is clear that the statements on lines 16878 and 16893 are redundant (as well as contradictory). Delete lines 16878 and 16893. Bug 0000323: interpretation of the undefinedness of range expressions Reject http://austingroupbugs.net/view.php?id=323 The Working Group believes that the standard is clear; outside of the POSIX locale the behavior is unspecified and cannot be relied upon (Page 185, Lines 5968-5970). Should you wish to propose a specification for what the behavior should be outside of the POSIX locale, you may re-open this issue with a detailed proposal. The WG cautions that such a proposal would have many technical and portability issues to successfully address before it would be acceptable. Bug 0000324: Clarify that ENOTDIR is for existing non-directory files OPEN http://austingroupbugs.net/view.php?id=324 We need some research undertaken on what current implementations do before we can recommend a change. Bug 0000325: tr and m4 translit behavior when string1 has repeated characters OPEN http://austingroupbugs.net/view.php?id=325 We need some research undertaken on what current implementations do before we can recommend a change. Next Steps ---------- The next call will be on October 14th at 16:00 UK time/08:00 Pacific and will continue processing defect reports. http://austingroupbugs.net See the calendar for the list of dialup numbers. An IRC channel will be available for the meeting 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