Minutes of the 17th February 2022 Teleconference Austin-1196 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 19th February 2022 Attendees: Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR (partia) 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 Tom Thompson, IEEE Apologies Eric Ackermann, HPI, University of Potsdam * 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 1538: what -s is poorly described, uses the word "quit" Accepted as Marked https://austingroupbugs.net/view.php?id=1538 This item is tagged for TC3-2008. An interpretation is required. Interpretation response: The standard states the output produced by the what utility includes the name of the file for each occurrence of the pattern found and that no output is produced for a file that has no occurrences of the pattern, and conforming implementations must conform to this. However, concerns have been raised about this which are being referred to the sponsor. Rationale: Implementations write the pathname once for each file, regardless of how many identification strings are found in it. Notes to the Editor (not part of this interpretation): On page 3437 line 116038 (-s option), change: Quit after finding the first occurrence of the pattern in each file. to: Skip to the next file operand (if any) after finding the first occurrence of the pattern in each file. On page 3437 line 116063 (STDOUT), change: The standard output shall consist of the following for each file operand: "%s:\n\t%s\n", , to: The standard output for each file operand shall consist of: "%s:\n", followed by one line for each identification string (if any) found in the file, in the following format: "\t%s\n", Bug 1541: Overabundance of parentheses in atoi() example Accepted https://austingroupbugs.net/view.php?id=1541 This item is tagged for TC3-2008. Bug 1542: A certain example for puts, fputs, time, localtime, and localtime_r isn't consistent between them all OPEB https://austingroupbugs.net/view.php?id=1542 This was discussed during the call. Each of the examples cited show output that is consistent with the format strings given. (So there is no bug here.) Half of those present wanted to reject this request; the other half thought we could remove "still" from the place(s) where it appears (rather than add "still" to the place(s) where it does not appear. We decided keep this open and defer it to a time when we have nothing else to do. Next Steps ---------- The next calls are on: Mon 2022-02-21 (gettext) Thu 2022-02-24 (general bugs) 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)