All
Enclosed are the minutes from yesterdays meeting
regards
Andrew
------------
Minutes of the 15th May 2025 Teleconference Austin-1456 Page 1 of 1
Submitted by Andrew Josey, The Open Group. 16th May 2025
Attendees:
Andrew Josey, The Open Group
Don Cragun, IEEE SA OR
Eric Blake, Red Hat, The Open Group OR
Eric Ackermann, CISPA
Mark Brown
Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR
Geoff Clare, The Open Group
Haelwenn Monnier, The Open Group
* General business
We confirmed the calendar for upcoming meetings, we have a two week
break, then the next meeting is June 5th, followed by June 12th.
Andrew had raised the question with Tom at IEEE on the status
of the PSDO submission and is awaiting the response.
* Open Business
Bug 1876: clarify, whether a trap action that is executed from a OPEN
context where set -e is ignored, would have set -e ignored, too
https://www.austingroupbugs.net/bug_view_page.php?bug_id=1876
Andrew took an action to ask shell developers to comment on this
issue. (completed by sending an email to the reflector:
austin-group-l:archive/latest/37925).
Bug 864: Insufficient specification of storage requirements for synchronization
objects
https://www.austingroupbugs.net/view.php?id=864
AI: Andrew to contact Rich Felker to determine whether or not items
1 an 4 have been resolved by section 2.9.9 and to get suggested
wording for changes to address items 2 and 3. The action was
completed, but no response received as yet.
Bug 1904: LC_TIME era start_date (and end_date) possibly mis-specified
https://www.austingroupbugs.net/bug_view_page.php?bug_id=1904
This was discussed during the 2025-02-13 meeting:
Historically, there was no year 0 and the standard is worded
to reflect this fact. Is this what implementation actually do?
Andrew had completed an action to ask for input on what other
implementations do and some feedback has been received so need to
return to this on a future call.
* Current Business
Bug 1924: New word splitting requirements inappropriate in locales with
non-self-synchronising character encodings
https://www.austingroupbugs.net/view.php?id=1924
Accepted as marked, resolved, tc1-2024 tag
After page 79 line 2388 section 3 Definitions, add:
3.328 Self-synchronizing Character Encoding
A character encoding in which no contiguous subset of bytes
from the encoding of any one character or two adjacent characters
can also represent the encoding of any valid character on its
own.
and renumber the later subsections.
On page 2481 line 80454 section 2.5.3 Shell Variables (IFS), after:
If the value of IFS includes any bytes that do not form part
of a valid character, the results of field splitting, expansion
of '*', and use of the read utility are unspecified.
add a sentence:
If the character encoding used for the characters in IFS is not
self-synchronizing and the value of IFS includes any character
for which the byte encoding can overlap with the byte encoding
of any other sequence of characters, the results of field
splitting, expansion of '*', and use of the read utility are
unspecified. (Note: the UTF-8 encoding is self-synchronizing,
meaning that no character's encoding can be confused with any
other sequence of characters, and thus does not trigger this
exception.)
Bug 1925: c17 -E output is incompatible with existing implementations
https://www.austingroupbugs.net/view.php?id=1925
Accepted as marked, interpretation required, tc1-2024 tag.
Interpretation response:
The standard states the output format for c17 -E, and conforming
implementations must conform to this. However, concerns have been
raised about this which are being referred to the sponsor.
Rationale:
None.
Notes to the Editor (not part of this interpretation):
Change Page 2673 lines 88033-88036 from:
<blockquote>
...
it may contain extra information appropriate for subsequent compilation passes
and shall contain at least one line with the format:
<pre>
"# %d \"%s\"\n", <line>, <pathname>
</pre>
for each file processed as a result of a <b>#include</b> directive, unless no
other output generated from that file is present in the output, where
<i>line</i> is a line number and <i>pathname</i> is the pathname used to open
the file.
</blockquote>
to:
<blockquote>
...
it may contain extra information appropriate for subsequent compilation passes
and shall contain at least one line with the format:
<pre>
"# %d \"%s\"\n", <line>, <pathname>
</pre>
or
<pre>
"# %d \"%s\" %s\n", <line>, <pathname>, <flags>
</pre>
for each file processed as a result of a <b>#include</b> directive, unless no
other output generated from that file is present in the output, where
<i>line</i> is a line number, <i>pathname</i> is the pathname used to open the
file, and <i>flags</i> is an implementation-defined string.
</blockquote>
Next Steps
We will start on bug 1924 next time as some new comments were received
after the bug was resolved above.
The next calls are on
Thu 2025-05-22 No meeting
Thu 2025-05-29 No meeting
Thu 2025-06-05 (WEBEX meeting - general bugs)
Thu 2025-06-12 (WEBEX meeting - 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)
--------
Andrew Josey The Open Group
Austin Group Chair
Email: a.jo...@opengroup.org
Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England
To learn how we maintain your privacy, please review The Open Group Privacy
Statement at http://www.opengroup.org/privacy.
To unsubscribe/opt-out from this mailing list login to The Open Group
collaboration portal at
https://collaboration.opengroup.org/operational/portal.php?action=unsub&listid=2481
