Minutes of the 21 January 2010 Teleconference Austin-474 Page 1 of 1 Submitted by Andrew Josey, The Open Group. January 23 , 2010 Attendees Andrew Josey, The Open Group Don Cragun, PASC OR Mark Brown, IBM, TOG OR Ulrich Drepper, Red Hat Nick Stoughton, USENIX, ISO/IEC OR Apologies Geoff Clare, The Open Group We picked up on the current bugs Bug #162 Determining System Endianess during preprocessing OPEN http://austingroupbugs.net/view.php?id=162 Nick reported that the C committee hasn't shown enthusiasm to introduce macros for endianess handling. They are not opposed but somebody needs to do the work and preferably before the April C committee meeting. If any of the people commenting here has interest, please provide a little paper describing the new feature with justification and changes to the spec. Either post it to the C committee mailing list directly or post it to the Austin Group mailing list and it will be appropriately forwarded. Bugs #180,#183 Action: Andrew to work on online pubs bugs and report back Bug #205 Action: Andrew to send Dave Korn a reminder Bug #206 Typo in Change History Accepted http://austingroupbugs.net/view.php?id=206 Bug #207 unnecessary types used only in XSI Accepted http://austingroupbugs.net/view.php?id=207 Bug #0000208: SIG_HOLD marked as CS not XSI Accepted http://austingroupbugs.net/view.php?id=208 Bug #0000209 lockf is XSI, constants not Accepted http://austingroupbugs.net/view.php?id=209 Bug #0000210 fsblkcnt_t and fsfilcnt_t incorrectly marked XSI Accepted http://austingroupbugs.net/view.php?id=210 Bug #0000211 inttypes should provide wchar_t Accepted http://austingroupbugs.net/view.php?id=211 Bug #0000212 editorial errors in Accepted http://austingroupbugs.net/view.php?id=212 Bug #0000213 Definition of pututxline() is slightly too restrictive to allow flexible implementations OPEN http://austingroupbugs.net/view.php?id=213 We considered this during the 2010-01-21 conference call. We agree with Bugnote: 375 and plan to address that issue. We are concerned that the main change proposed for this issue would have observable effects on existing applications, and may lead to breaking such applications. We are willing to remove the absolute requirement to implement pututxline with getutxid, but not to go as far as suggested. Proposed new wording: If the process has appropriate privileges, the pututxline( ) function shall write out the structure into the user accounting database. It shall search for a record as if by getutxid() that satisfies the request. If this search succeeds, then the entry shall be replaced. Otherwise, a new entry shall be made at the end of the user accounting database. Bug #0000214 "dot" should mention the effect of `return' Accept as Marked http://austingroupbugs.net/view.php?id=214 Page 2342 line 74074 add (return special built-in utility) Page 2356 line 74480 add to the see also list references to: Section 2.9.5 Function Definition Command dot special built-in Page 2324 line 73400 after the word return add: (a cross-reference to the return special built in utility) p 2355 l74432 add to the end of the line: "or dot script" Action: Andrew review the bugs for any interpretations ready to start their review cycle Next Steps ---------- The next call will be on February 11 at 16:00 UK time/08:00 Pacific to carry on with the 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