hi All
Happy New Year! Attached are the minutes of our first meeting of the year
regards
Andrew
---------------------
Minutes of the 4th January 2024 Teleconference Austin-1373 Page 1 of 1
Submitted by Andrew Josey, The Open Group. 5th January 2024
Attendees:
Don Cragun, IEEE PASC OR
Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR
Andrew Josey, The Open Group
Geoff Clare, The Open Group
Mark Ziegast, SHware Systems Dev.
Eric Blake, Red Hat, The Open Group OR
Apologies
Tom Thompson, IEEE
* General news
Draft 4 is now in review at The Open Group and IEEE,
with the review closing on January 31 2024. No comments
have been received as yet.
The draft was submitted to ISO/IEC, and after the meeting
some comments have been received from the ISO editors that need to be
addressed, to set the document on A4 (from US Letter),
also to remove any reviewers notes (there is on in ยง1.6 Terminology).
Andrew completed the action to issue a status report (Austin/1372).
Andrew reported he has been added to the IEEE CS MSC mailing list
(the successor to the PASC). A meeting is scheduled for January 9th.
An item for the meeting is to confirm that Don will continue
as the IEEE SA representative to the Austin Group.
* Current Business
Bug 1785: Conflict in specification of processing of declaration utilities
Accepted as Marked
https://austingroupbugs.net/view.php?id=1785
This item is tagged for TC1-2024.
On page 2483 line 80766 section 2.9.1.1, change:
The first word (if any) that is not a variable assignment or
redirection shall be expanded. If any fields remain following
its expansion, the first field shall be considered the command
name. If no fields remain, the next word (if any) shall be
expanded, and so on, until a command name is found or no words
remain. If there is a command name and it is recognized as a
declaration utility, then any remaining words after the word
that expanded to produce the command name, that would be
recognized as a variable assignment in isolation, shall be
expanded as a variable assignment (tilde expansion after the
first <equals-sign> and after any unquoted <colon>, parameter
expansion, command substitution, arithmetic expansion, and quote
removal, but no field splitting or pathname expansion); while
remaining words that would not be a variable assignment in
isolation shall be subject to regular expansion (tilde expansion
for only a leading <tilde>, parameter expansion, command
substitution, arithmetic expansion, field splitting, pathname
expansion, and quote removal). For all other command names,
words after the word that produced the command name shall be
subject only to regular expansion. All fields resulting from
the expansion of the word that produced the command name and
the subsequent words, except for the field containing the command
name, shall be the arguments for the command.
to:
The first word (if any) that is not a variable assignment or
redirection, and any subsequent words, shall be processed as
follows:
The first word may be matched lexically against the names
of declaration utilities.
The first word shall be expanded.
If any fields remain following expansion of the first word,
the first field shall be considered the command name. If
no fields remain, the next word (if any) shall be expanded,
and so on, until a command name is found or no words remain.
If the above optional matching against the names of declaration
utilities was not performed and there is a command name,
the command name shall be matched lexically against the
names of declaration utilities.
If whichever of the matching operations that was performed
produced a successful match, any remaining words after the
word that expanded to produce the command name, that would
be recognized as a variable assignment in isolation, shall
be expanded as a variable assignment (tilde expansion after
the first <equals-sign> and after any unquoted <colon>,
parameter expansion, command substitution, arithmetic
expansion, and quote removal, but no field splitting or
pathname expansion); while remaining words that would not
be a variable assignment in isolation shall be subject to
regular expansion (tilde expansion for only a leading
<tilde>, parameter expansion, command substitution, arithmetic
expansion, field splitting, pathname expansion, and quote
removal). If the matching operation did not produce a
successful match, words after the word that produced the
command name shall be subject only to regular expansion.
All fields resulting from the expansion of the word that
produced the command name and the subsequent words, except
for the field containing the command name, shall be the
arguments for the command.
[Note to the editor: use letters a, b, c, etc. for the above list.]
On page 2483 line 80790 section 2.9.1.1, delete:
When determining whether a command name is a declaration utility,
an implementation may use only lexical analysis. It is unspecified
whether assignment context will be used if the command name
would only become recognized as a declaration utility after
word expansions.
Bug 1788: The meaning of "Daylight Saving Time" should be clarified OPEN
https://austingroupbugs.net/view.php?id=1788
We started this item and notes are in the etherpad.
We will continue on this on the next call.
Next Steps
----------
The next call is on:
Mon 2024-01-08 (Zoom meeting - general bugs)
Thu 2024-01-11 (Zoom meeting - general bugs)
The calls are for 90 minutes
Calls are anchored on US time. (8am Pacific)
Apologies in Advance:
Geoff Clare, 2024-01-15 to 2024-01-22 inclusive
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
