Minutes of the 15th September 2016 Teleconference Austin-783 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 16th September 2016 Attendees: Mark Ziegast, SHware Systems Don Cragun, IEEE PASC OR Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR Geoff Clare, The Open Group David Clissold, IBM Joerg Schilling, FOKUS Fraunhofer (by phone only) Eric Blake, Red Hat Richard Hansen, Google Martin Rehak, Oracle, The Open Group OR Apologies Andrew Josey, The Open Group * General news Nick reported us on the result of the SC22 meeting attended by Andrew and Nick earlier in the week, the conclusion being that TC2 will get an ISO ballot. * Outstanding actions ( Please note that this section has been flushed to shorten the minutes - to locate the previous set of outstanding actions, look to the minutes from 28 Jan 2016) Bug 0000249: Add standard support for $'...' in shell Reopened http://austingroupbugs.net/bug_view_page.php?bug_id=249 We will return to bug 249 on a future call. Bug 0000953: Alias expansion is under-specified Was Accepted as Marked http://austingroupbugs.net/view.php?id=953 Richard has an action to propose new wording to discuss in a future telecon. * Current Business Bug 1009:"remain in affect after" and "during the execution" are problematic when built-in/function modifies the variable Accepted as Marked http://austingroupbugs.net/view.php?id=1009 This item is tagged for TC3-2008 V7TC2D4 Page 2366, Line 75516, (TC2D3 #75172), Section: 2.9.1 Change: If the command name is a special built-in utility, variable assignments shall affect the current execution environment. to: If the command name is a special built-in utility, variable assignments shall affect the current execution environment before the utility is executed and remain in effect when the command completes; if an assigned variable is further modified by the utility, the modifications made by the utility shall persist. Change V7TC2D4 XCU 2.14, Item 2 (Page 2385, L76309) from: 2. As described in Section 2.9.1, variable assignments preceding the invocation of a special built-in utility remain in effect after the built-in completes; this shall not be the case with a regular built-in or other utility. to: 2. As described in Section 2.9.1, variable assignments preceding the invocation of a special built-in utility affect the current execution environment; this shall not be the case with a regular built-in or other utility. Change the description of set -a (V7TC2D4 P2409 L77097-77103) from: When this option is on, the export attribute shall be set for each variable to which an assignment is performed; see XBD Section 4.23. If the assignment precedes a utility name in a command, the export attribute shall not persist in the current execution environment after the utility completes, with the exception that preceding one of the special built-in utilities causes the export attribute to persist after the built-in has completed. If the assignment does not precede a utility name in the command, or if the assignment is a result of the operation of the getopts or read utilities, the export attribute shall persist until the variable is unset. to: Set the export attribute for all variable assignments. When this option is on, a variable that is assigned a value (see [xref to XBD Section 4.23]), including variables that are assigned a value by the getopts, read, or cd utilities, shall cause that variable to gain the export attribute. Note: As discussed in [xref to XCU 2.9.1], not all variable assignments happen in the current execution environment. When an assignment happens in a separate execution environment the export attribute is still set for the variable, but that does not affect the current execution environment. Bug #1011: Make the binary search tree functions friendlier to use: require balancing, add typing and allow destruction OPEN http://austingroupbugs.net/view.php?id=1011 We started a discussion on this item and will continue next time. Next Steps ---------- The next call is on September 22nd, 2016 (a Thursday) Calls are anchored on US time. (8am Pacific) This call will be for the regular 90 minutes. http://austingroupbugs.net An IRC channel will be available for the meeting irc://irc.freenode.net/austingroupbugs An etherpad is usually up for the meeting, with a URL using the date format as below: http://posix@posix.rhansen.org:9001/p/201x-mm-dd password=2115756#