Minutes of the 14 May 2009 Teleconference Austin-453 Page 1 of 1 Submitted by Andrew Josey, The Open Group. May 15 , 2009 Attendees Andrew Josey, The Open Group Don Cragun, PASC OR Geoff Clare, The Open Group Mark Brown, IBM, TOG OR Nick Stoughton, USENIX, ISO/IEC OR Ulrich Drepper, Red Hat * ISO status Andrew had responded back to ISO that we do want to retain the line numbers. No response has been received as yet. * Bugzilla At the end of the call we had a lengthy review of the Mantis bug reporting prototype that Mark has put together. Mark captured a number of suggestions to incorporate. We agreed that all should trial its use, and we will try and use it in parallel on the next call. data centre. * Aardvark review We picked up again on the latest rdvk reports. http://www.opengroup.org/austin/aardvark/latest/ XCUbug2 ERN 183 time keyword interpretation Accept as marked below Andrew will merge the details from mail seq 12082 into the aardvark report (xcubug2.txt) XSHbug3 ERN 33 mktime EOVERFLOW Accept XSHbug3 ERN 34 strtod Accept Action item on Nick Forward to the C Committee for their information XSHbug3 ERN 35 time() error handling Accept as marked below Add to clock_gettime Page 668 after line 22669 The clock_gettime() function shall fail if: [EOVERFLOW] The current value of time will not fit in an object of type time_t." On the time() page: Add a may fail case. Change: "No errors are defined." on P2107, L66673 in the ERRORS sections to: "The time() function may fail if: [EOVERFLOW] The current value of time will not fit in an object of type time_t." Add to RATIONALE on time() On some systems the time() function is implemented using a system call that does not return an error condition in addition to the return value. In this case it is impossible to differentiate between a valid and invalid return value and hence overflow conditions cannot be detected. Next meeting ------------ The next call will be on May 28 at 16:00 UK time/08:00 Pacific to carry on with the aardvark. We will discuss AI-122 We will also trial use of the Mantis bugtracker. 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