Minutes of the 31st October 2022 Teleconference Austin-1267 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 2nd November 2022 Attendees: Don Cragun, IEEE PASC OR Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR Eric Ackermann, HPI, University of Potsdam Andrew Josey, The Open Group Geoff Clare, The Open Group Mark Ziegast, SHware Systems Dev. Eric Blake, Red Hat, The Open Group OR Apologies: Tom Thompson, IEEE * General news A reminder that the calls this week are one hour earlier in Europe due to the end of Summer time! This was a call dedicated to general bugs. * Carried Forward This section trimmed -- see Austin/1264 * Current Business Bug 1593: specify whether struct sockaddr_un.sun_path can be a flexible array member OPEN https://austingroupbugs.net/view.php?id=1593 Wait for Eric to complete his action on bug 561 Bug 1561: clarify what kind of data shell variables need to be able to hold Accepted as Marked https://austingroupbugs.net/view.php?id=1561 This item is tagged for TC3-2008 On page 155 line 5331 section 8.1 Environment Variable Definition, change: The value of an environment variable is a string of characters. to: The value of an environment variable is an arbitrary sequence of bytes, except for the null byte. On page 155 line 5335 section 8.1 Environment Variable Definition, change: names shall not contain the character '='. to: names shall not contain any bytes that have the encoded value of the character '='. On page 155 line 5336 section 8.1 Environment Variable Definition, change: shall be composed of characters from the portable character set to: shall be composed of bytes that have the encoded value of characters from the portable character set On page 155 line 5342 section 8.1 Environment Variable Definition, change: Other characters may be permitted by an implementation to: Other characters, and byte sequences that do not form valid characters, may be permitted by an implementation On page 2314 line 74531 section 2.5 Parameters and Variables, add a new paragraph: Parameters can contain arbitrary byte sequences, except for the null byte. The shell shall process their values as characters only when performing operations that are described in this standard in terms of characters. On page 2316 line 74612 section 2.5.3 Shell Variables, insert: Shell variables shall be initialized only from environment variables that have valid names. before: If a variable is initialized from the environment, ... On page 2321 line 74857 section 2.6.2 Parameter Expansion, change: ... for substring processing. to: ... for character substring processing. After page 3626 line 125374 section C.2.5.3 Shell Variables, add a new paragraph: Since shell variables are parameters denoted by a name, the shell cannot initialize shell variables from environment variables that do not have a valid name. However, the shell may initialize parameters that do not have valid names from such environment variables. Bug 1560: clarify wording of command substitution Accepted as Marked https://austingroupbugs.net/view.php?id=1560 This item is tagged for TC3-2008 On page 2323 line 74944 section 2.6.3 Command Substitution, change: replacing the command substitution (the text of the commands string plus the enclosing "$()" or backquotes) with the standard output of the command(s), removing sequences of one or more characters at the end of the substitution. Embedded characters before the end of the output shall not be removed; however, they may be treated as field delimiters to: replacing the command substitution (the text of the commands string plus the enclosing "$()" or backquotes) with the standard output of the command(s); if the output ends with one or more bytes that have the encoded value of a character, they shall not be included in the replacement. Any such bytes that occur elsewhere shall be included in the replacement; however, they might be treated as field delimiters On page 2325 line 75034 section 2.6.5 Field Splitting, change: The shell shall treat each character of the IFS as a delimiter to: The shell shall treat a byte sequence forming any of the characters in the IFS value as a delimiter On page 2325 line 75038 section 2.6.5 Field Splitting, change: any sequence of , , or characters at the beginning or end of the input shall be ignored and any sequence of those characters within the input shall delimit a field to: any sequence (zero or more instances) of bytes that have the encoded values of , , or characters at the beginning or end of the input shall be ignored and any sequence (one or more instances) of such bytes within the input shall delimit a field On page 2326 line 75046 section 2.6.5 Field Splitting, change: The term ``IFS white space'' is used to mean any sequence (zero or more instances) of white-space characters that are in the IFS value (for example, if IFS contains //, any sequence of and characters is considered IFS white space). to: The term ``IFS white space'' is used to mean any sequence (zero or more instances) of the byte sequences that form any of the white-space characters in the IFS value (for example, if IFS contains //, any sequence of bytes that have the encoded values of and characters is considered IFS white space). On page 2326 line 75051 section 2.6.5 Field Splitting, change: Each occurrence in the input of an IFS character that is not IFS white space to: Each occurrence in the input of a byte sequence that forms an IFS character that is not IFS white space Next time we will start on Bug 1548. Next Steps ---------- The next calls are on: Thu 2022-11-03 (general bugs) Mon 2022-11-07 (general bugs) The calls are for 90 minutes Apologies in advance: Eric Blake: 2022-11-03 Calls are anchored on US time. (8am Pacific) Please check the calendar invites for dial in details. Bugs are at: https://austingroupbugs.net An etherpad is usually up for the meeting, with a URL using the date format as below: https://posix.rhansen.org/p/20xx-mm-dd (For write access this uses The Open Group single sign on, for those individuals with gitlab.opengroup.org accounts. Please contact Andrew if you need to be setup)