All
Enclosed are the minutes from the thursday meeting this week
regards
Andrew
------------------------
Minutes of the 4th February 2021 Teleconference Austin-1100 Page 1 of 1
Submitted by Andrew Josey, The Open Group. 5th February 2021
Attendees:
Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR
Joerg Schilling
Don Cragun, IEEE PASC OR
Geoff Clare, The Open Group
Eric Blake, Red Hat, The Open Group OR
Richard Hansen
Mark Ziegast, SHware Systems Dev.
Andrew Josey (joined late)
Apologies:
Eric Ackermann
Tom Thompson
* General news
None
* Outstanding actions
(Please note that this section has been flushed to shorten the minutes -
to locate the previous set of outstanding actions, look to the minutes
from 13th June 2019 and earlier)
Bug 1254: "asynchronous list" description uses "command" instead of "AND-OR
list" OPEN
https://austingroupbugs.net/view.php?id=1254
Action: Joerg to investigate how his shell behaves.
Bug 700 - Nick to raise this issue with the C committee
Bug 713 - Nick to raise with the C committee.
Bug 739 - Nick to raise with the C committee.
* Current Business
0001392: find(1): clarify whether -perm ops - and + should follow chmod
Accepted as Marked
https://austingroupbugs.net/view.php?id=1392
This item is tagged for Issue 8.
An interpretation is required.
Interpretation response:
The standard does not speak to this issue, and as such no conformance
distinction can be made between alternative implementations based
on this. This is being referred to the sponsor.
Rationale:
None.
Notes to the Editor (not part of this interpretation):
On page 2797 lines 91951-91959 change:
The mode argument is used to represent file mode bits. It shall
be identical in format to the symbolic_mode operand described
in chmod, and shall be interpreted as follows. To start, a
template shall be assumed with all file mode bits cleared. An
op symbol of <tt>'+'</tt> shall set the appropriate mode bits
in the template; <tt>'−'</tt> shall clear the appropriate bits;
<tt>'='</tt> shall set the appropriate mode bits, without regard
to the contents of the file mode creation mask of the process.
The op symbol of <tt>'−'</tt> cannot be the first character of
mode; this avoids ambiguity with the optional leading <hyphen-minus>.
Since the initial mode is all bits off, there are not any
symbolic modes that need to use <tt>'−'</tt> as the first
character.
to:
The mode argument is used to represent file mode bits. It shall
be processed in an identical matter to the symbolic_mode operand
described in chmod, except that:
The changes to file mode bits shall be applied to a template
instead of to any files. The template shall initially have
all file mode bits cleared.
The op symbol <tt>'-'</tt> cannot be the first character
of mode; this avoids ambiguity with the optional leading
<hyphen-minus>. Since the initial mode is all bits off,
there are not any symbolic modes that need to use <tt>'-'</tt>
as the first character.
On page 2801 lines 92128-92130 (find example #3), change:
find . −perm −o+w,+s
prints (−print is assumed) the names of all files in or below
the current directory, with all of the file permission bits
S_ISUID, S_ISGID, and S_IWOTH set.
to:
find . −perm −o+w,+s
prints (−print is assumed) the names of all files in or below
the current directory, with all of the file permission bits
S_ISUID, S_ISGID, and S_IWOTH set, regardless of the value of
the file creation mask. (Note that the file creation mask is
only specified for the file permission bits, and not S_ISUID,
S_ISGID or S_ISVTX.)
On page 2801 after line 92130 insert a new example #4 and renumber the
remaining examples:
The following command:
find . −perm −+w
prints (−print is assumed) the names of all files in or below
the current directory, with S_IWUSR set if the file creation
mask does not have S_IWUSR set (otherwise the S_IWUSR bit is
ignored), S_IWGRP set if the file creation mask does not have
S_IWGRP set (otherwise S_IWGRP is ignored), and S_IWOTH set if
the file creation mask does not have S_IWOTH set (otherwise
S_IWOTH is ignored).
Bug 1395: awk radix character in alternative conversion to atof() Accepted as
Marked
https://austingroupbugs.net/view.php?id=1395
This item is tagged for TC3-2008.
An interpretation is required.
Interpretation response:
The standard states the requirements for string to number conversion
in awk, and conforming implementations must conform to this. However,
concerns have been raised about this which are being referred to
the sponsor.
Rationale:
As stated in the RATIONALE the intent was to allow implementations
to recognize floating-point constants according to either the ISO/IEC
9899: 1990 standard or ISO/IEC 9899: 1999 standard. The use of
<period> in the text was an oversight.
Notes to the Editor (not part of this interpretation):
On page 2486 line 79925 section awk, change:
... optionally containing a <period>
to:
... optionally containing a radix character
On page 2486 line 79928 section awk, change:
The sequence starting with the first digit or the <period>
(whichever occurs first) is interpreted as a floating constant
of the C language, and if neither an exponent part nor a <period>
appears, a <period> is assumed to follow the last digit in the
string.
to:
The sequence starting with the first digit or the radix character
(whichever occurs first) is interpreted as a floating constant
of the C language, except that the radix character shall be
used in place of a <period>, and if neither an exponent part
nor a radix character appears, a radix character is assumed to
follow the last digit in the string.
On page 2487 lines 79966-79967, change:
Each occurrence of the decimal point character from the current
locale is changed to a <period>.
to:
Each occurrence of the radix character from the current locale is changed
to a <period>.
On page 2507 line 80823, add a sentence:
Note that these forms do not use the radix character from the
current locale; they always use a <period>.
Gettext draft.
We will return to this on a future call.
The gettext draft in the etherpad is at
https://posix.rhansen.org/p/gettext_draft
https://posix.rhansen.org/p/gettext_split
Next Steps
----------
The next calls are on:
February 8th 2021 (Monday)
This call will be for 60 minutes.
February 11th 2020 (Thursday)
This call will be 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
