Austin Group Minutes of the 30 Oct 2007 Teleconference Austin-403 Page 1 of 1 Submitted by Andrew Josey, The Open Group. Oct 31 , 2007 Attendees Andrew Josey, The Open Group Geoff Clare, The Open Group Mark Brown, IBM, TOG OR Nick Stoughton, USENIX, ISO/IEC OR Don Cragun , Sun, PASC OR Ulrich Drepper, Red Hat Status update --------------- * C++ PAR status We received some queries about the C++ PAR that had been submitted 5.4 As written, this is not appropirate as a "purpose" clause in a document for submittal to RevCom. If the document will have a "purpose" clause, revise as appropriate. If the document will not have a "purpose" clause, so state. Response: Change 5.4 to: The purpose is to allow portable C++ applications to make use of the POSIX standard interfaces And move the existing words from 5.4 to 7.4 Explanatory section This standard will provide a method for using all the POSIX C APIs in a consistent fashion in C++ applications, and will provide a basis for applications developed in C++ for POSIX platforms to work in a consistent, portable, and efficient manner. The standard is intended to address the issue of mixing C and C++ translation units in the same application. 6.1.b Explain the meaning of "... more than just normative references". What new category of reference are you intending to create? Response: This standard will be merging substantial parts of both of these standards into a new standard. In that sense, these two standards are "more than just normative references" ... though in a formal sense they are exactly that (normative references). However, the new standard will likely include text directly derived from both. So we suggest updating 6.1.b to IEEE Standard 1003.1 is joint copyright between IEEE and The Open Group. ISO/IEC Standard 14882 (C++ language) is copyright ISO/IEC. Both of these are more than just normative references; it is expected that text from both of these standards will be incorporated into the new standard. 7.1 Explain "C++0X". Response: The C++ standard, ISO/IEC IS 14882 is currently undergoing revision, with an anticipated publication date in 2009. The term "C++0x" is used to refer to this, as yet unpublished, revision of the standard, since the publication date is uncertain and future. Action on Andrew to response to PAR queries. Action completed October 31. * Draft Status The 3.2 snapshot was made available on 19 October . Comments from Geoff have been received. * Next Face to Face meeting Andrew noted that the Austin Group meeting has now been moved to the week commencing March 3rd. Send out a revised meeting notice for March ( do that when the ISO ballot results are received). Action: Andrew update web site - completed October 31. * Timeline update We reviewed Austin 389 (timeline), we agreed that the D4 review should be a 45 day review at IEEE. Action Andrew to update Austin/389. Completed October 31st * 2004 Aardvark reports XCU ERN 168 STDIN, STDOUT, STDERR Accept as marked below This needs to go down the interps track. The standard is ambiguous but concerns are being fwd. Change the definition of "Character Special File" to: A file that refers to a device (such as a terminal device file) or that has special properties (such as /dev/null). Change the first sentence of 2.1.1 item 4 from: The system may provide additional utilities, functions, or facilities not required by IEEE Std 1003.1-2001. to: The system may provide non-standard extensions. These are features not required by IEEE Std 1003.1-2001 and may include but are not limited to: - Additional functions - Additional headers - Additional symbols in standard headers - Additional utilities - Additional options for standard utilities - Additional environment variables - Additional file types - Non-conforming file systems (for example legacy file systems for which _POSIX_NO_TRUNC is false, case-insensitive file systems or network file systems) - Dynamically populated file systems (for example /proc) - Additional character special files with special properties (for example /dev/stdin, /dev/stdout and /dev/stderr) XSH ERN 218 poll Open This item is still open and carried forward from a previous meeting * Interpretations Austin-092: Geoff raised an issue on about whether AI-092 goes far enough and proposed the following additional changes on the reflectors It was agreed to update the editors notes for AI-092 as follows: In the STDIN section of asa (P141 L5412), cksum (P248 L9684), fold (P461 L17884), grep (P496 L19192), head (P503 L19420), od (P679 L26323), sed (P842 L32626), and wc (P1046 L40340) change "The standard input shall be used only if no file operands are specified" to "The standard input shall be used if no file operands are specified, and may be used if a file operand is '-'. Otherwise the standard input shall not be used" and if there is a semicolon after the text to be changed, change it to a full stop (period). In the STDIN section of file (P445 L1722) change "Not used." to "The standard input may be used if a file operand is '-'. Otherwise the standard input shall not be used." In the STDIN section of nl (P668 L25892) and tsort (P935 L36239) change "The standard input ... a text file that is used if no file operand is given." to "The standard input shall be used if no file operand is specified, and may be used if the file operand is '-'. Otherwise the standard input shall not be used. See the INPUT FILES section." In the INPUT FILES section of nl (P668 L25894) and tsort (P935 L36241) change "The input file named by the file operand is a text file." to "The input file shall be a text file." In the OPERANDS section of tail (P898 L34871) change "operands are" to "operand is" In the STDIN section of tail (P898 L34874) change "The standard input shall be used only if no file operands are specified." to "The standard input shall be used if no file operand is specified, and may be used if the file operand is '-'. Otherwise the standard input shall not be used." Action Andrew to pass these additional changes onto Cathy for the next draft (since AI-092 has already been actioned). Austin-171 : Additional changes were proposed by Ulrich on the reflector and it was agreed these should be added to this interpretation. These are additional to those already in interp 171. The page and line numbers are relative to the D3.2r draft. XBD page 234, line 7724: Add after line 7724 new line: F_DUPFD_CLOEXEC Duplicate file descriptor with the close-on-exec flag FD_CLOEXEC set. XSH page 803, line 26722: Add new paragraph after line 26722 F_DUPFD_CLOEXEC Like F_DUPFD, but the FD_CLOEXEC flag associated with the new file descriptor shall be set. XSH page 805, line 26832: Add new line after line 26832: F_DUPFD_CLOEXEC A new file descriptor. XSH page 806, line 26857: Change is F_DUPFD to is F_DUPFD or F_DUPFD_CLOEXEC XSH page 806, line 26861: Changes is F_DUPFD to is F_DUPFD or F_DUPFD_CLOEXEC Action: Andrew add this to AI-171 (addition) and update AI-171 Austin-187: The proposed edits include: Update the interpretation: Since no return value is reserved to indicate a strerror() error, implementations can return a null pointer, a pointer to an empty string, or a pointer to a meaningful string that can be printed. To: Since no return value is reserved to indicate a strerror() error, but all calls (whether successful or not) must return a pointer to a message string, on error strerror() can return a pointer to an empty string or a pointer to a meaningful string that can be printed. Change from: 1. Error (with no error message): errno is set to EINVAL, the return value is a null pointer. To: 1. Error (with no meaningful message): errno is set to EINVAL, the return value is a pointer to an empty string. Action Andrew to update AI-187 Next Steps ----------- Andrew will update the aardvark reports with the latest inbound defect reports. The next meeting is the Thu 1st Nov 2007. 16:00 UK. Note the different TZ offsets for this week, as the UK has reverted back to UTC as its localtime. The meeting will last for 90 minutes. 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