Minutes of the 17 Feb 2011 Teleconference Austin-513 Page 1 of 1 Submitted by Andrew Josey, The Open Group. February 19 , 2011 Attendees Andrew Josey, The Open Group Don Cragun, PASC OR Nick Stoughton, USENIX, ISO/IEC OR Geoff Clare, The Open Group Mark Brown, IBM, TOG OR Eric Blake, Red Hat Jim Pugsley, Oracle *Old Business carried forward: TC1 PAR: Comments had been received on the PASC PMC criteria and Andrew has the action to submit to the SEC. (Action now completed) * New Business * We picked up on regular Bug processing Bug 0000251: Forbid bytes 1 through 31 (inclusive) in filenames http://austingroupbugs.net/view.php?id=251 We discussed whether a new error should be invented for a newline in a filename error. Don now has enough information to update the bug. Bug 0000162: Determining System Endianess during Preprocessing OPEN http://austingroupbugs.net/view.php?id=162 Nick had submitted a proposal last week, which was discussed on the call. Suggestions for change were made and Nick will take the action to further update the bug. Bug 0000367: interaction between readonly, export, getopts, and read Accept as marked http://austingroupbugs.net/view.php?id=367 Erik had completed his action. An interpretation is required. This item is tagged for Issue 8. Interpretation response: The standard does not speak to this issue, and as such no conformance distinction can be made between alternative implementations based on this. This is being referred to the sponsor. Rationale: The interaction between the readonly status and the built-ins that use read only variables needs to be documented. Notes to the Editor (not part of this interpretation): Before line 5501 [XBD 8.1 Environment Variable Definition], add the following paragraphs: Additionally, a subset of the above variables are manipulated by shell built-in utilities outside of shell assignments. If an attempt is made to mark any of the following variables as readonly, then either the readonly command shall reject the attempt, or readonly shall succeed but the shell can still modify the variables outside of assignment context, or readonly shall succeed but use of a shell built-in that would otherwise modify such a variable shall fail. LINENO PWD OLDPWD OPTARG OPTIND Implementations may provide an implementation-defined set of additional variables which are manipulated by implementation-specific built-in utilities not defined in this standard. The readonly utility shall not reject marking these additional variables as readonly, but when marked readonly, those extension utilities shall either continue to modify the variables, or shall fail because the variable is readonly. None of the variables defined by this standard shall be in this implementation-defined set. At line 74359 [XCU 2.14 readonly DESCRIPTION], change The values of variables with the readonly attribute cannot be changed by subsequent assignment, nor can those variables be unset by the unset utility. to The values of variables with the readonly attribute cannot be changed by subsequent assignment or use of the export, getopts, readonly, or read utilities, nor can those variables be unset by the unset utility. As described in , conforming applications shall not request to mark a variable as readonly if it is documented as being manipulated by a shell built-in utility, as it may render those utilities unable to complete successfully. At line 74396 [XCU readonly EXIT STATUS], change "Zero." to 0 Successful completion. >0 An error occurred, such as an attempt to modify a readonly variable using a name=word operand. At line 74402 [XCU readonly EXAMPLES], change: readonly HOME PWD to: readonly HOME At line 74413 [XCU readonly RATIONALE], add a paragraph: Attempts to set the readonly attribute on certain variables, such as PWD, may have surprising results. Either readonly will reject the attempt, or the attempt will succeed but the shell will continue to alter the contents of PWD during the cd utility, or the attempt will succeed and render the cd utility inoperative (since it must not change directories if it cannot also update PWD). At line 74312 [XCU export EXIT STATUS], change "Zero." to 0 Successful completion. >0 An error occurred, such as an attempt to modify a readonly variable using a name=word operand. At line 90587 [XCU getopts DESCRIPTION], change "a return value greater than zero" to "a return value of one". At line 90595 [XCU getopts DESCRIPTION], add a sentence: An error in setting any of these variables (such as if var has previously been marked readonly) shall be considered an error of getopts processing, and shall result in a return value greater than one. At line 90671 [XCU getopts EXIT STATUS], change >0 The end of options was encountered or an error occurred. to 1 The end of options was encountered. >1 An error occurred. At line 103927 [XCU read DESCRIPTION], prior to "If it is called", insert a sentence: An error in setting any variable (such as if a var has previously been marked readonly) shall be considered an error of read processing, and shall result in a return value greater than one. At line 103977 [XCU read EXIT STATUS], change >0 End-of-file was detected or an error occurred. to 1 End-of-file was detected. >1 An error occurred. Bug 0000377: Semaphore values should be initialized to zero when a semaphore set is created. Accepted http://austingroupbugs.net/view.php?id=377 Don had completed his action and this bug was accepted. This item is tagged for Issue 8. Bug 0000380: Misplaced "restrict" in wcp[n]cpy() prototypes Accepted This item is tagged for TC1-2008 http://austingroupbugs.net/view.php?id=380 Next Steps ---------- The next call will be on March 3rd 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