Minutes of the 5th May 2022 Teleconference Austin-1219 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 5th May 2022 Attendees: Mark Ziegast, SHware Systems Dev. Don Cragun, IEEE PASC OR Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR Eric Blake, Red Hat, The Open Group OR Geoff Clare, The Open Group Andrew Josey, The Open Group Apologies: Eric Ackermann Tom Thompson, IEEE * General news This was a call dedicated to general bugs. Eric had completed his action to send a mail to The Open Group to call for sponsorship of the gettext interface. * 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 1560: clarify wording of command substitution OPEN https://austingroupbugs.net/view.php?id=1560 Leave this and related bugs 1561, and 1564 open pending reviews/discussions. Bug 1578: sed y-command: error in description about the number of characters in string1 and string2 Accepted as Marked https://austingroupbugs.net/view.php?id=1578 This item is tagged for TC3-2008 On P3138, L106249-106251 (sed Extended Description), change:
If the number of characters in string1 and string2 are not equal, or if any of the characters in string1 appear more than once, the results are undefined.
to:
If (after resolving any escape sequences) the numbers of characters in string1 and string2 are not equal, or if any of the characters in string1 appear more than once, the results are undefined.
Bug 1579: some minor improvementes to BRE Expression Anchoring Accepted https://austingroupbugs.net/view.php?id=1579 This item is tagged for TC3-2008 Bug 1580: add a hint that env vars with invalid names might be passed on to the environments of programs/utilities Accepted https://austingroupbugs.net/view.php?id=1580 This item is tagged for TC3-2008 Bug 1581: “time” vs. Korn Shell flavours Duplicate of 267 https://austingroupbugs.net/view.php?id=1581 Bug 1582: Algorithm for computing addresses for "address chains" is not clearly specified Accepted as Marked https://austingroupbugs.net/view.php?id=1582 This item is tagged for TC3-2008 An interpretation is proposed: Interpretation response: The standard is unclear on this issue, and no conformance distinction can be made between alternative implementations based on this. This is being referred to the sponsor. Rationale: In order to evaluate the address list ",," two rules need to be applied, and it is unclear how they interact. Line 87365 states: If more than the required number of addresses are provided to a command that requires zero addresses, it shall be an error. Otherwise, if more than the required number of addresses are provided to a command, the addresses specified first shall be evaluated and then discarded until the maximum number of valid addresses remain, for the specified command. If the "omitted addresses" rule is applied first, then "the addresses specified first" are those that result from that rule, leading to ",," being evaluated as "1,$ 1,$", which is invalid syntax for an address list (unless the implementation accepts this as an extension). If it is applied during the address counting performed for the above rule, then the first ',' becomes "1,$" and then the second ',' is evaluated after this, leading to the above rule being applied to "1,$,$". It is clear from the rationale in the standard, that it is intended for the latter to be used, but the normative text does not say so. Notes to the Editor (not part of this interpretation): After line 87382 add a new paragraph: If an address is omitted between two separators, the rule shall be applied to the first separator and the resulting second address shall be used as the first address for the second separator. For example, with the address list ",," the first ',' becomes "1,$" and the '$' is treated as the first address for the second ',', resulting in "1,$,$". Next Steps ---------- The next calls are on: Mon 2022-05-09 (gettext) Thu 2022-05-12 (general bugs) Apologies in Advance: Geoff Clare, 2022-05-09 Tom Thompson, 2022-05-09 The calls are for 90 minutes 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)