Minutes of the 14th April 2022 Teleconference Austin-1214 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 15th April 2022 Attendees: Don Cragun, IEEE PASC OR Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 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 Tom Thompson, IEEE Eric Ackermann, HPI, University of Potsdam * General news This was a call dedicated to general bugs. A reminder that there is NO meeting on Monday April 18th. * 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 1544: uudecode: standardise or at least reserve - as another special symbol for decoding to stdout https://austingroupbugs.net/view.php?id=1544 Accepted as Marked This item is tagged for Issue 8. Page and line numbers are for Issue 8 draft 2.1 On page 3275 line 111239 change: The uudecode utility shall scan the input file, searching for data compatible with one of the formats specified in uuencode, and attempt to create or overwrite the file described by the data (or overridden by the −o option). The pathname shall be contained in the data or specified by the −o option. to: The uudecode utility shall scan the input file, searching for data compatible with one of the formats specified in uuencode, and determine the pathname for the output file from the -o option if given, otherwise from the input data. If the pathname for the output file is either of the magic cookies − or /dev/stdout, uudecode shall write the decoded file to standard output, otherwise it shall attempt to create or overwrite the file named by the pathname. On Page 3275 line 111259 change: /dev/stdout to: - or /dev/stdout Change page 3276 lines 111285-111287 from: If the file data header encoded by uuencode is − or /dev/stdout, or the −o /dev/stdout option overrides the file data, the standard output shall be in the same format as the file originally encoded by uuencode. Otherwise, the standard output shall not be used. to: If the pathname specified for the output file is − or /dev/stdout, the standard output shall be in the same format as the file originally encoded by uuencode. Otherwise, the standard output shall not be used. On page 3276, after line 111305, Application Usage, add a paragraph: In order to create an output file named - it needs to be specified using an alternative pathname, for example, -o ./-, since - alone is considered a magic cookie by uudecode. Likewise, in order to write to an output file named /dev/stdout it also needs to be specified as, for example, -o ///dev/stdout. On Page 3276 lines 111314-111318, change: In early drafts, the [−o outfile] option-argument allowed the use of − to mean standard output. The symbol − has only been used previously in POSIX.1-202x as a standard input indicator. The standard developers did not wish to overload the meaning of − in this manner. The /dev/stdout concept exists on most modern systems. The /dev/stdout syntax does not refer to a new special file. It is just a magic cookie to specify standard output. to: In early drafts, the [−o outfile] option-argument allowed the use of − to mean standard output. The standard developers did not wish to overload the meaning of − in this manner, resulting in previous versions only using /dev/stdout for this purpose. POSIX.1-202x now allows it as most implementations were already supporting − as an extension. The file /dev/stdout exists as a special file on most modern systems. However, the /dev/stdout syntax in uudecode does not refer to a new file. It is just a magic cookie to specify standard output. On page 3278 at line 111357 change: /dev/stdout to: - or /dev/stdout On page 3281 after line 111490 add a new paragraph: Since uudecode treats a decode_pathname of - to mean decode to standard output, in order to specify that a file named - is to be created, decode_pathname should be specified using an alternative pathname, for example ./-. Likewise, in order to specify that a file with the pathname /dev/stdout is to be written, decode_pathname should be specified as, for example, ///dev/stdout. Bug 1550: clarifications/ambiguities in the description of context addresses and their delimiters for sed OPEN https://austingroupbugs.net/view.php?id=1550 Geoff had completed his action to propose wording as suggested in bugnote 5756 Leave open for feedback (ongoing discussion). Bug 1551: sed: ambiguities in the how BREs/EREs are parsed/interpreted between delimiters (especially when these are special characters) OPEN https://austingroupbugs.net/view.php?id=1551 Geoff had completed his action to propose wording as suggested in bugnote 5756 This is expected to be closed as a dup of 1550. Bug 1556: clarify meaning of \n used in a bracket expression in a sed context address or s-command OPEN https://austingroupbugs.net/view.php?id=1556 Aim to close as a dup of 1550 when we resolve 1550. Bug 1560: clarify wording of command substitution OPEN https://austingroupbugs.net/view.php?id=1560 Leave this ans related bugs 1561, 1562 and 1564 open pending reviews/discussions. Bug 1563: Wording for what seem to imply odd behavior. "all occurrences of @(#)" Accepted as Marked https://austingroupbugs.net/view.php?id=1563 An interpretation is required. This item is tagged for TC3-2008. Interpretation response: The standard states the identification strings written by what, and conforming implementations must conform to this. However, concerns have been raised about this which are being referred to the sponsor. Rationale: The description in the standard does not match existing practice when the number of identification strings in a file is not one. Additionally, an end-of-file condition was not listed as a delimiter. Notes to the Editor (not part of this interpretation): On page 3437 line 116031 section what, change: The what utility shall search the given files for all occurrences of the pattern that get (see [xref to get]) substitutes for the %Z% keyword ( "@(#)" ) and shall write to standard output what follows until the first occurrence of one of the following: " > newline \ NUL to: The what utility shall search the given files for all occurrences of the pattern that get (see [xref to get]) substitutes for the %Z% keyword ( "@(#)" ). The what utility shall write to standard output what follows until the first occurrence of one of the following: ('"') , (' >') , , (' \\') , ('\0'), or an end-of-file condition on the input file. If not at end-of-file, the what utility shall then look for the next occurrence of "@(#)" after one of those characters. On page 3437 line 116063 section what, change: The standard output shall consist of the following for each file operand: "%s:\n\t%s\n", , to: For each file operand, the standard output shall consist of: "%s:\n", followed by zero or more of: "\t%s\n", one for each identification string located. Next Steps ---------- Mon 2022-04-18 NO MEETING The next calls are on: Thu 2022-04-21 (general bugs) Mon 2022-04-25 (gettext) Apologies in Advance: Don Cragun, 2022-04-25 Andrew Josey, 2022-04-25 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)