Minutes of the 19 May 2011 Teleconference Austin-522 Page 1 of 1 Submitted by Andrew Josey, The Open Group. May 21 , 2011 Attendees Andrew Josey, The Open Group Don Cragun, PASC OR Jim Pugsley, Oracle Geoff Clare, The Open Group Mark Brown, IBM, TOG OR Eric Blake, Red Hat Nick Stoughton, USENIX, ISO/IEC OR * Old Business The 2008-TC1 PAR has now been approved at NESCOM. The wording approved is more general than we had originally requested but should not impact the project overall. Once change is that the specific cutoff date is not mentioned, in practice this means that the cutoff will be the date of the first ballot. * New Business We picked up on Bug processing for bugs reported against project 2008-TC1. Bug 0000412: application note suggests impossible return value for input strings of length MAX_INT characters Accept as marked http://austingroupbugs.net/view.php?id=412 Append to the APPLICATION USAGE for puts (page 1723, line 55077), fputs (p908 l30373), and fputws (p912 l30489) as follows: This volume of POSIX.1-2008 requires that successful completion simply return a non-negative integer. There are at least three known different implementation conventions for this requirement: * Return a constant value. * Return the last character written. * Return the number of bytes written. Note that this implementation convention cannot be adhered to for strings longer than {INT_MAX} bytes as the value would not be representable in the return type of the function. For backwards compatibility, implementations can return the number of bytes for strings of up to INT_MAX bytes, and return INT_MAX for all longer strings. Add to the RATIONALE for fputs: The fputs() function is one whose source code was specified in _The C Programming Language_ by Brian W. Kernighan and Dennis M. Ritchie. In the original edition, the function had no defined return value, yet many practical implementations would, as a side effect, return the value of the last character written as that was the value remaining in the accumulator used as a return value. In the second edition of the book, either the fixed value 0 or EOF would be returned depending upon the return value of ferror(); however, for compatibility with extant implementations, several implementations would, upon success, return a positive value representing last byte written. Bug 0000425: typographical error in reference to sysconf() Accepted http://austingroupbugs.net/view.php?id=425 Bug 0000427: Incorrect page and line numbers in XBD changes Accepted http://austingroupbugs.net/view.php?id=427 Bug 0000428: Incorrect page and line numbers in XSH changes Accepted http://austingroupbugs.net/view.php?id=428 Bug 0000429: Minor editorial problems in XSH changes Accepted http://austingroupbugs.net/view.php?id=429 Bug 0000430: Incorrect page and line numbers in XCU changes Accepted http://austingroupbugs.net/view.php?id=430 Bug 0000431: Minor editorial problems in XCU changes Accepted http://austingroupbugs.net/view.php?id=431 Bug 0000432: confusing presentation of O_* list merge Accepted http://austingroupbugs.net/view.php?id=432 Bug 0000433: Interactions between XSH/TC1/D1/0093 and 0092, 0101 Accepted http://austingroupbugs.net/view.php?id=433 Bug 0000434: The getcwd() change has already been applied Accepted http://austingroupbugs.net/view.php?id=434 Bug 0000435: Missing "empty string" text in XSH/TC1/D1/0174 Accepted http://austingroupbugs.net/view.php?id=435 Bug 0000436: Missing "empty string" text in XSH/TC1/D1/0312 Accepted http://austingroupbugs.net/view.php?id=436 Bug 0000437: Interaction between XSH/TC1/D1/0218 and 0219 Accepted http://austingroupbugs.net/view.php?id=437 Bug 0000438: XSH/TC1/D1/0235 partially redundant Accepted http://austingroupbugs.net/view.php?id=438 Bug 0000439: XSH/TC1/D1/0262 redundant Accepted http://austingroupbugs.net/view.php?id=439 Bug 0000440: XCU/TC1/D1/0035 redundant Accepted http://austingroupbugs.net/view.php?id=440 Bug 0000441: Minor editorial problems in XRAT changes Accepted http://austingroupbugs.net/view.php?id=441 Bug 0000442: Rationale improvement for XRAT/TC1/D1/0009 Accepted http://austingroupbugs.net/view.php?id=442 Bug 0000443 2.8.1 Consequences of Shell Errors, 2.14 dot, 2.14 eval Rejected http://austingroupbugs.net/view.php?id=443 Note that we have recategorized this item as an objection. The changes suggested may have merit, but (since they don't reflect existing practice) would not be suitable for a technical corrigenda. The working group believes that this issue should be raised against the current standard and the resolution should be targeted to the next revision. It is recommended that the submitter file a new bug (of type enhancement request) against Issue 7 to address this issue. * Email Issues We discussed an issue raised on the email reflector about shell case statements and the ;& case statement fall through. This was felt to be an issue for a future revision, not a TC item, although further detail is needed. Eric agreed to take an action to file a defect report (completed as bug 449) Next Steps ---------- The editors will update the TC1 with these resolved bug report, reformat some bugs that need to be split out, plus add additional bugs closed since the previous draft. The next draft for 2008-TC1 is due June 30. The next call will be on May 26th at 08:00 Pacific and will continue processing defect reports. This call will be for the regular 90 minutes. 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