Minutes of the 10th February 2022 Teleconference Austin-1196 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 12th February 2022 Attendees: Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR Don Cragun, IEEE PASC OR Mark Ziegast, SHware Systems Dev. Andrew Josey, The Open Group Eric Blake, Red Hat, The Open Group OR Geoff Clare, The Open Group Apologies Eric Ackermann, HPI, University of Potsdam Tom Thompson, IEEE * General news This was a call dedicated to general bugs. * Outstanding actions Bug 1533: struct tm: add tm_gmtoff (and tm_zone) field(s) OPEN https://austingroupbugs.net/bug_view_page.php?bug_id=1533 This was discussed in the February 3, 2022 teleconference. Leave it open until we get a more complete suggestion for the Desired Action. * Current Business Bug 1535: Poor description of declaration (all really) utility argument processing Accepted as Marked https://austingroupbugs.net/bug_view_page.php?bug_id=1535 This item is tagged for Issue 8. Change item 2 from: The words that are not variable assignments or redirections shall be expanded. If any fields remain following their expansion, the first field shall be considered the command name and remaining fields are the arguments for the command. If the command name is recognized as a declaration utility, then any remaining words that would be recognized as a variable assignment in isolation shall be expanded as a variable assignment (tilde expansion after the first and after any unquoted , parameter expansion, command substitution, arithmetic expansion, and quote removal, but no field splitting or pathname expansion); while words that would not be a variable assignment in isolation shall be subject to regular expansion. For all other command names, all subsequent words shall be subject to regular expansion (tilde expansion for only a leading , parameter expansion, command substitution, arithmetic expansion, field splitting, pathname expansion, and quote removal). to: The first word (if any) that is not a variable assignment or redirection shall be expanded. If any fields remain following its expansion, the first field shall be considered the command name. If no fields remain, the next word (if any) shall be expanded, and so on, until a command name is found or no words remain. If there is a command name and it is recognized as a declaration utility, then any remaining words after the word that expanded to produce the command name, that would be recognized as a variable assignment in isolation, shall be expanded as a variable assignment (tilde expansion after the first and after any unquoted , parameter expansion, command substitution, arithmetic expansion, and quote removal, but no field splitting or pathname expansion); while remaining words that would not be a variable assignment in isolation shall be subject to regular expansion (tilde expansion for only a leading , parameter expansion, command substitution, arithmetic expansion, field splitting, pathname expansion, and quote removal). For all other command names, words after the word that produced the command name shall be subject only to regular expansion. All fields resulting from the expansion of the word that produced the command name and the subsequent words, except for the field containing the command name, shall be the arguments for the command. Bug 1536: Unimplemented requirements in fd duplication Accepted as Marked https://austingroupbugs.net/bug_view_page.php?bug_id=1536 This item is tagged for TC3-2008. In line 75394 delete the words: for input and append after the words (before the terminating period): see Section 2.8.1 a new clause: ; if the file descriptor denoted by word represents an open file descriptor that is not open for input, a redirection error may result In line 75404 delete the words: for output and append after the words (before the terminating period): see Section 2.8.1 a new clause: ; if the file descriptor denoted by word represents an open file descriptor that is not open for output, a redirection error may result On XRAT page 3736 line 128244 section C.2.7.5 change: There is no additional rationale provided for this section. to: The file descriptor duplication redirection operators, [n]<&word and [n]>&word, make a copy of one file descriptor as another. If the operation is successful, the new file descriptor has the same access mode as the source (old) file descriptor, because the access mode is determined by the open file description to which both file descriptors point. To avoid a redirection error, applications need to ensure that they use the appropriate redirection operator for the access mode of the file descriptor being duplicated. On XRAT page 3736 line 128246 section C.2.7.6 change: There is no additional rationale provided for this section. to: See [xref to C.2.7.5]. Next Steps ---------- The next calls are on: Mon 2022-02-14 (gettext) Thu 2022-02-17 (general bugs) The calls are for 90 minutes Apologies in Advance: Mark Ziegast, 02-14 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)