Minutes of the 17th October 2022 Teleconference Austin-1263 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 21st October 2022 Attendees: Don Cragun, IEEE PASC OR Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR Eric Blake, Red Hat, The Open Group OR Eric Ackermann, HPI, University of Potsdam Mark Ziegast, SHware Systems Dev. Geoff Clare, The Open Group Apologies: Andrew Josey, The Open Group Tom Thompson, IEEE * General news This was a call dedicated to general bugs. * Carried Forward Bug 1560: clarify wording of command substitution https://austingroupbugs.net/view.php?id=1560 Leave this and related bugs 1561 and 1564 open awaiting reviews/discussion. Bug 1273: glob()'s GLOB_ERR/errfunc and non-directory files OPEN https://austingroupbugs.net/view.php?id=1273 We will leave this open awaiting feedback. Bug 768: add "fd-private" POSIX locks to spec OPEN https://austingroupbugs.net/view.php?id=768 Linux has now had OFD locks for several years, and more code in the wild is starting to use it - so we have existing practice (see note 2508) https://www.gnu.org/software/libc/manual/html_mono/libc.html#Open-File-Description-Locks Starting point of resolution at https://posix.rhansen.org/p/bug768 AI to EricB - take the GNU documentation and turn it into a desired action Bug 739: CX requirements for strftime seem to conflict with ISO C OPEN https://austingroupbugs.net/view.php?id=739 Nick completed his action to liaise with the C committee on this issue. C23 is about to go to ballot, so the way to raise the issue would be as a ballot comment. This could be done either as a UK or US national body comment. Andrew confirmed with the UK C Panel that we can submit comments. Bug 728: Restrictions on signal handlers are both excessive and insufficient OPEN https://austingroupbugs.net/view.php?id=728 The alignment with C17 changes the requirements in this area. There is still no allowance for accessing const objects or string literals, so that is something we could consider adding as an extension to C. Or we could raise the issue with the C committee if we want to stay in sync with the C standard. Suggestion: raise it as a C23 ballot comment. Depending on the answer, we could implement what they plan to do, or diverge (or leave things as they are). AI Nick and Geoff: File ballot comments on C23 (through the US and/or UK national bodies to WG14). Bug 708: Make mblen, mbtowc, and wctomb thread-safe for alignment with C11 OPEN https://austingroupbugs.net/view.php?id=708 This was discussed with WG14: https://www.open-std.org/jtc1/sc22/wg14/www/docs/n2148.htm#dr_498 DR 498 (URL above) seems to have an agreed wording change from April 2017, but it has not been applied. Nick asked the WG14 convenor what happened to that DR. It appears the item was discussed but in the end the C committee could not agree an acceptable change, and no alternate proposal was available. We will need to accept the C wording for now. Bug 700: Clarify strtoul's behaviour on strings representing negative numbers OPEN https://austingroupbugs.net/view.php?id=700 AI: Nick and Geoff to work together on a C23 ballot comment (against N3047 7.24.1.7 para 5). Bug 689: Possibly unintended allowance for stdio deadlock OPEN https://austingroupbugs.net/view.php?id=689 Change needs to be coordinated with C23. AI: Nick and Geoff to work together on a C23 ballot comment (against N3047 7.23.3 para 3). Bug 618: require isatty and friends to set errno on failure OPEN https://austingroupbugs.net/view.php?id=618 Action item to EricB: email to various lists to collect results for sample program (see bug 503 comment 1005 for starting point) for current errno behavior on various OS Bug 375: Extend test/[...] conditionals: ==, <, >, -nt, -ot, -ef OPEN https://austingroupbugs.net/view.php?id=375 This bug was reviewed, and the following added as note. Given the difficulties identified with the matching operations performed by == and =~ in [[ ... ]] there would seem to be two options for progressing this bug: 1. Keep [[ ... ]] but without =~ and with == "neutered" such that it can only be used portably for fixed-string comparisons. 2. Omit [[ ... ]] altogether but perhaps add -nt, -ot, and -ef to test/[ instead. We would welcome feedback on whether option 1 is an acceptable compromise or is too limiting. We need to resolve this bug by no later than 2022-11-13 if it is to make it into draft 3. After that, only option 2 will be possible (because draft 3 will be "feature complete"). * Current Business Bug 267: time (keyword) Accepted as Marked https://austingroupbugs.net/view.php?id=267 This item is tagged for TC3-2008. An interpretation is required. 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: It is clear that the intent is to allow the reserved word implementation (as evidenced by use of time in pipelines being unspecified, and explicit mention in the rationale of the time utility), but the conditions under which the behavior is unspecified are insufficient to allow this. Notes to the Editor (not part of this interpretation): Make the changes in Note: 0005990 Bug 249: Add standard support for $'...' in shell OPEN https://austingroupbugs.net/view.php?id=249 This item was continued and has its own etherpad. See also https://posix.rhansen.org/p/bug249 Geoff took an action to copy the etherpad content to a bug note. Bug 247: Add nullglob (null globbing) support to shell's "set" and glob() Rejected https://austingroupbugs.net/view.php?id=247 Various suggestions have been made in this bug, but there have been valid objections to all of them. Therefore this bug is rejected on the basis of no consensus. Bug 220: FD_ISSET can use const keyword Accepted as Marked https://austingroupbugs.net/view.php?id=220 This item is tagged for Issue 8. Make the change in the desired action, and also the following change: On 2018 edition page 1553 line 50827 section pselect(), change: int FD_ISSET(int fd, fd_set *fdset); to: int FD_ISSET(int fd, const fd_set *fdset); Bug 144: Standard lacks a (possibly XSI) interface to associate a session to a TTY; tcsetsid() OPEN https://austingroupbugs.net/view.php?id=144 We discussed bug 144 and will pick it up again after we resolve bug 249. Next Steps ---------- The next calls are on: Thu 2022-10-20 (general bugs) WEBEX Mon 2022-10-24 (general bugs) The calls are for 90 minutes Apologies in advance: Nick Stoughton: 2022-10-20 Eric Blake: 2022-10-27, 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)