Minutes of the 6th October 2022 Teleconference Austin-1260 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 7th October 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 Eric Ackermann, HPI, University of Potsdam * General news This was a call dedicated to general bugs. Andrew noted that there are still no bugs have been received to date for the new APIs part 2 document. For details of the review see https://collaboration.opengroup.org/platform/single_unix_specification/documents.php?action=view&gdid=54267 * Current Business Bug 1122: POSIX should include gettext() and friends OPEN and https://posix.rhansen.org/p/gettext_draft Also https://austingroupbugs.net/file_download.php?file_id=64&type=bug Geoff has uploaded a new PDF and has applied the changes from it in the Issue8NewAPIs branch in gitlab, except for the global NLSPATH change. AJ and Geoff took an action to start work on preparing a company review draft within The Open Group for new APIs. 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"). Bug 336: Add recursive variable indirection in makefiles Accepted as Marked https://austingroupbugs.net/view.php?id=336 This item is tagged for Issue 8 On D2.1 page 2943 line 98700 section make, change: Macro expansions in string2 of macro definition lines shall be performed according to the form used to define the macro. Immediate-expansion forms (including appending to an existing immediate-expansion macro) shall be expanded in the macro definition line, and shall not be re-expanded when used in a rule or command. Delayed-expansion forms (including appending to an existing delayed-expansion macro, and conditional assignment to a macro not previously existing) shall be expanded when the macro identified by string1 is expanded in a rule or command, and the result of the expansion shall be scanned for further macros. to: Macro expansions in string2 of macro definition lines shall be performed according to the form of macro definition used. In immediate-expansion forms (including appending to an existing immediate-expansion macro), they shall be expanded in the macro definition line and the result of the expansion shall not be scanned for further macros when the macro identified by string1 is expanded. In delayed-expansion forms (including appending to an existing delayed-expansion macro, and conditional assignment to a macro not previously existing), they shall not be expanded in the macro definition line; they shall be expanded when the macro identified by string1 is expanded, and the result of the expansion shall be scanned for further macros. Implementations shall support at least 100 levels of indirection. On D2.1 page 2943 line 98720, 98726 section make, change: If string1 in a macro expansion contains a macro expansion, the results are unspecified. to: If string1 in a macro expansion contains a macro expansion, that inner macro expansion shall be performed as described above and the result substituted into string1 to produce the macro name used for the outer macro expansion. Bug 328: Auto-Dependency Generation Duplicate of Bug 1325 https://austingroupbugs.net/view.php?id=328 This issue was revisited when we resolved bug 1325, which provides a way to achieve equivalent results by post-processing the output of c99 -E. This was chosen over -M due to the syntax issue with -MM. The suggestion to use -M -M will not work, as existing implementations treat -M -M the same as -M (not -MM). This bug is being rejected as a duplicate of 1325. Bug 267: time (keyword) OPEN https://austingroupbugs.net/view.php?id=267 Action: Geoff took an action for some word-smithing and formatting of note 4794. Bug 249: Add standard support for $'...' in shell OPEN https://austingroupbugs.net/view.php?id=249 See also https://posix.rhansen.org/p/bug249 We will start on this item next time. Next Steps ---------- The next calls are on: Mon 2022-10-10 (general bugs) Thu 2022-10-13 (general bugs) The calls are for 90 minutes Apologies in advance: Andrew Josey, 2022-10-10 Geoff Clare might have no power 2022-10-10 and 2022-10-13 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)