Austin Group Minutes of the 13 October Teleconference Austin-269 Page 1 of 1 Submitted by Andrew Josey, The Open Group. October 14, 2005 Attendees Andrew Josey, The Open Group Don Cragun , Sun, PASC OR Nick Stoughton, USENIX, ISO/IEC OR Ulrich Drepper, Red Hat Apologies Mark Brown, IBM, TOG OR Mats Wichmann, Intel We also had an IRC channel open for this call irc://irc.freestandards.org/austin Action item review --------------------- Just the updates on Austin/240r1 are noted here. ACTION AI-2005-01-09 Andrew Josey & Mats Wichmann to propose a time and place for a joint Austin group/LSB Workgroup meeting to consider LSB/POSIX conflicts, to be held as soon as conveniently possible. Status: OPEN Nick still has an action to prepare an agenda for a teleconference. ACTION: Andrew: Do final review pass on the Technical Report document when the ISO LSB has been submitted, probably the next change is to change LSB 3.0 to IS 23360-200x. This will be done around end October 2005. ISO Status: -------------- Nick gave an update on two recent ISO meetings he had attended (ISO C and SC22). -The WG14 ISO C meeting had addressed a number of defect reports. +XSH ERN 95 perror (from Nick's email on the topic slightly edited) We discussed XSH ERN 95 on perror() during the WG 14 committee meeting this week. The message below summarizes the discussion and the resulting new proposed TC. One way to summarize the new position is that an implementation that conforms to the current POSIX requirement of not altering the orientation of stderr should still conform to C. The perror function will be removed from the list of byte oriented functions (returning to the pre-TC2 state). It will be permitted (but not required) to set the orientation of an un-oriented stderr to narrow, and has what C calls "undefined" behavior if stderr was previously set to wide. This permits the POSIX required behavior. Message: The problem with perror is the statement in Posix: "The perror() function shall not change the orientation of the standard error stream." As your proposed DR suggests, you *can* write something like save_errno = errno; or = fwide(stderr, 0); errno = save_errno; actual_perror("error identifying string") freopen("", "w", stderr); fwide(stderr, or); But this is not portable code. You cannot, in general, put a stream back in its unbound state with the freopen/ fwide trick. Thus, in Standard C, we have to accept that a call to perror will change the state of an unbound stream (to byte-oriented, or narrow). Our TC made perror a byte output function to reflect this. A proposed fix is for WG14 to undo the designation of perror as a byte output function. Instead, we'd say that perror is permitted to fail if stderr is already wide oriented. Making the failure undefined behavior gives Posix the latitude to specify perror as it does, gives current Standard C implementations the latitude to remain unchanged, and gives more meticulous implementations the latitude to try harder to get the error message out to a wide stream. +XBD ERN 53 stddef.h wchar_t definition The defect report has been accepted (the ISO C DR # is 321) by WG14 but the macro name has been changed. -SC22 Plenary Meeting The POSIX Advisory Group (PAG) report was given and essentially accepted. Nick has put reports on the SC22PAG plato site. These are now available at public visibility level, http://www.opengroup.org/projects/sc22pag/ 03-Oct-05 Cross reference - PAG recommendations to SC22 resolutions http://www.opengroup.org/projects/sc22pag/doc.tpl?gdid=8689 02-Oct-05 Resolutions of the SC 22 plenary meeting, 2005 http://www.opengroup.org/projects/sc22pag/doc.tpl?gdid=8683 Regarding the Canada position on the Austin Group, Nick reported that Canada received no support for its position. We noted during the teleconference that it might be of help for Canada if we were to ensure that the next meeting is announced in good time to ISO SC22, and possibly we should look to get it hosted in Canada. Defect Report Processing ------------------------- The group picked up on the latest batch of defect reports, which are available at the following URL: http://www.opengroup.org/austin/aardvark/latest/ XSH ERN 89 setpgrp Reject The text is straight from the SVID. We expect to deprecate the interface in the next revision and to extend the rationale (based on wording proposed -- to be completed after we close this item). Recollection is that the description was short since that was all that could be agreed to when this was brought into the standard. We attempted to contact the requestor for more information but that was not forthcoming, so we have closed this item. XSH ERN 102 connect and sendto Accept as marked below Accept option A from the original proposed resolution within the aardvark. On page 60 line 2499 change: "in which case calls to output functions shall send to the pre-specified peer" to: "in which case calls to output functions that do not specify a peer address shall send to the pre-specified peer" On page 1297 line 40671 change: "If the socket is connectionless-mode, the message shall be sent to the address specified by msghdr." to: "If the socket is connectionless-mode, the message shall be sent to the address specified by msghdr if no pre-specified peer address has been set. If a peer address has been pre-specified, either the message shall be sent to the address specified in msghdr (overriding the pre-specified peer address), or the function shall return -1 and set errno to EISCONN." On page 1300 line 40782 change: "If the socket is connectionless-mode, the message shall be sent to the address specified by dest_addr." to: "If the socket is connectionless-mode, the message shall be sent to the address specified by dest_addr if no pre-specified peer address has been set. If a peer address has been pre-specified, either the message shall be sent to the address specified by dest_addr (overriding the pre-specified peer address), or the function shall return -1 and set errno to EISCONN." XSH ERN 107 Section 2.2.1.2 undefining _POSIX_C_SOURCE Accept XSH ERN 108 rename dot and dot-dot OPEN Leave open till next call to validate that the choice of the EINVAL error is correct in the proposal below Before line 38638, add a new paragraph: If either pathname argument refers to a path whose final component is either dot or dot-dot, rename() shall fail. At line 38667, expand the EINVAL paragraph: The new directory pathname contains a path prefix that names the old directory, or either pathname argument contains a final component that is dot or dot-dot. XRAT ERN 7 B2.11.10 Overrun in Dumping Trace Streams into Trace Logs OPEN Leave this open pending the item being forwarded to the PASC SSWG for comment. Other Business -------------- Andrew contact ICSC to see if they plan to submit anything for the revision. Others to identify any other groups we should be contacting regarding the revision. Next Steps ----------- Andrew will update the aardvark reports with the latest inbound defect reports. The next call is Thursday October 27 2005 at the regular timeslot (the end of day light saving time is synchronized for the USA and UK/Europe on 30 October). irc://irc.freestandards.org/austin