Minutes of the 10th May 2018 Teleconference Austin-867 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 11th May 2018 Attendees: Mark Ziegast, SHware Systems Dev. Joerg Schilling, FOKUS Fraunhofer Geoff Clare, The Open Group Andrew Josey, The Open Group Don Cragun, IEEE PASC OR Eric Blake, Red Hat David Clissold, IBM Martin Rehak, Oracle, The Open Group OR Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR * General news Andrew discussed the IEEE changes regarding adoption of ISO and IEC standards. He has confirmed with IEEE staff that this will not impact the Austin Group. Andrew also mentioned that the group should expect to receive some information on an updated privacy policy for the mailing list which is hosted by The Open Group as a part of the GDPR rollout. * 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 9 March 2018 and earlier) * Current Business Bug 1077: Recommend support for wide-character regcomp and regexec and/or specify multi-byte behavior OPEN http://austingroupbugs.net/bug_view_page.php?bug_id=1077 Andrew has completed the action to ping his Apple contact and is awaiting a reply. Bug 1105: problems with backslashes in awk strings and EREs Re-opened http://austingroupbugs.net/view.php?id=1105 We plan to revisit this item. Bug 1085: "token shall be from the current position in the input" is incorrect Accepted as Marked http://austingroupbugs.net/bug_view_page.php?bug_id=1085 This item is tagged for TC3-2008 After applying the changes from 0001083, change page 2347 lines 74749-74754 from: When it is not processing an io_here, the shell shall break its input into tokens by applying the first applicable rule below to each character in turn in its input. The token shall be from the current position in the input until a token is delimited according to one of the rules below; the characters forming the token are exactly those in the input, including any quoting characters. If it is indicated that a token is delimited, and no characters have been included in a token, processing shall continue until an actual token is delimited. to: When it is not processing an io_here, the shell shall break its input into tokens by applying the first applicable rule below to each character in turn in its input. At the start of input or after a previous token has just been delimited, the first or next token, respectively, shall start with the first character that has not already been included in a token and is not discarded according to the rules below. Once a token has started, zero or more characters from the input shall be appended to the token until the end of the token is delimited according to one of the rules below. When both the start and end of a token have been delimited, the characters forming the token shall be exactly those in the input between the two delimiters, including any quoting characters. If a rule below indicates that a token is delimited, and no characters have been included in the token, that empty token shall be discarded. Bug 1100: Rewrite of Section 2.10 Shell Grammar, of the Shell Standard, to fix previous reports, fix new issues, and improve presentation. OPEN http://austingroupbugs.net/view.php?id=1100 To be continued on the next call. Next Steps ---------- The next call is on May 17th, 2018 (a Thursday) Apologies in advance from Nick Stoughton. Calls are anchored on US time. (8am Pacific) This call will be for the regular 90 minutes. http://austingroupbugs.net An etherpad is usually up for the meeting, with a URL using the date format as below: https://posix.rhansen.org/p/201x-mm-dd username=posix password=2115756#