Minutes of the 13th December 2018 Teleconference Austin-896 Page 1 of 1
Submitted by Andrew Josey, The Open Group. 15th December 2018
Attendees:
Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR
Joerg Schilling, FOKUS Fraunhofer
Don Cragun, IEEE PASC OR
Andrew Josey, The Open Group
Geoff Clare, The Open Group
Eric Blake, Red Hat
Apologies
Mark Ziegast, SHware Systems
* General news
We discussed when the next meeting would be, and agreed to break
now until January 3rd 2019.
We discussed moving to two weekly meetings at the start of 2019.
This is an action to help with addressing the backlog. Andrew will
setup a poll to find out the core team preferences. The call would
be at the usual timeslot in the day, but we would need to decide
which day of the week and the duration. The thursday call would
continue as usual.
* 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 9 March 2018 and earlier)
Bug 1077: Recommend support for wide-character regcomp and regexec and/or specify multi-byte behavior OPEN
http://austingroupbugs.net/bug_view_page.php?bug_id=1077
Andrew has completed the action to ping his Apple contact and is
awaiting a reply.
Bug 1122: POSIX should include gettext() and friends OPEN
http://austingroupbugs.net/view.php?id=1122
Left open as an action is still in progress to flesh out a complete proposal.
* Current Business
Bug 1134: Add getentropy interface OPEN
http://austingroupbugs.net/view.php?id=1134
Status: Andrew has called for any final objections to adding this to the 2019 workplan
for the Base Working Group.
Bug 1138: Add strsignal(), sig2str() and str2sig() to the standard. OPEN
http://austingroupbugs.net/view.php?id=1138
Status: Andrew has called for any final objections to adding this to the 2019 workplan
for the Base Working Group.
Bug 1150: exit status of command substitution not properly specified Accepted as Marked
http://austingroupbugs.net/view.php?id=1150
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:
None.
Notes to the Editor (not part of this interpretation):
On page 2350 line 74877 section 2.5.2, change:
Expands to the decimal exit status of the most recent pipeline (see [xref to 2.9.2]).
to:
Expands to the decimal exit status of the most recent pipeline
(see [xref to 2.9.2]) that was not within a command substitution
(see [xref to 2.6.3]).
Note: In var=$(some_command); echo $? the output is
the exit status of some_command but this is because
its exit status becomes the exit status of the assignment command
var=$(some_command) (see [xref to 2.9.1]) and this
assignment command is the most recent pipeline.
On page 2366 line 75543 section 2.9.1, change:
with the exit status of the last command substitution performed
to:
with the exit status of the command substitution whose exit
status was the last to be obtained
On page 2410 line 77132 section 2.14 set, change:
The failure of any individual command in a multi-command pipeline
shall not cause the shell to exit. Only the failure of the
pipeline itself shall be considered.
to:
The failure of any individual command in a multi-command pipeline,
or of any subshell environments in which command substitution
was performed during word expansion, shall not cause the shell
to exit. Only the failure of the pipeline itself shall be
considered.
On page 2410 line 77145 section 2.14 set, add:
In
set -e; echo $(false; echo one) two
the false command causes the subshell in which the command
substitution is performed to exit without executing echo
one; the exit status of the subshell is ignored and the
shell then executes the word-expanded command echo two.
Bug 1152: Effect of modifications to buffer underlying a memory stream Duplicate of 1144
http://austingroupbugs.net/view.php?id=1152
We believe the changes made in the resolution of bugid:1144 also
resolve this issue. Therefore this is being closed as a duplicate
of bug 1144.
Bug 1153: fread/fwrite to/from buffer underlying the memory stream Accepted as Marked
http://austingroupbugs.net/view.php?id=1153
This item is tagged TC3-2008
Add a new paragraph (CX shaded) to page 496 line 17237 section 2.5:
When a standard I/O stream has an associated memory buffer (whether
allocated internally, supplied to setvbuf(), or supplied to
fmemopen()), the behavior is undefined if that buffer overlaps with
the destination buffer passed to a call that reads from the stream
or with the source buffer passed to a call that writes to the stream.
Bug 1154: Add 'rm -v'
http://austingroupbugs.net/view.php?id=1154 Accepted as Marked
This item is tagged for Issue 8.
At page 3198 line 107245 [rm SYNOPSIS], change:
rm [−iRr] file...
rm -f [-iRr] [file...]
to:
rm [−iRrv] file...
rm -f [-iRrv] [file...]
At line 107284 [DESCRIPTION], change:
If this fails for any reason, rm shall write a diagnostic message
to standard error, do nothing more with the current file, and
go on to any remaining files.
to:
If rm successfully performed the above actions on the current
file, and the -v option is specified, rm shall write a message
containing the pathname of the current file to the standard
output. If the actions fail for any reason, rm shall write a
diagnostic message to standard error, do nothing more with the
current file, and go on to any remaining files.
After line 107298 [OPTIONS], insert a new paragraph:
-v
After file has been removed, write a message to standard output indicating that it has been removed.
Change STDOUT section (page 3200 line 107331 from
None.
to:
If the -v option is specified, information about the file being
removed shall be written to standard output in an unspecified
format.
After line 107404 [RATIONALE], add a paragraph:
The addition of the −v option allows a user of rm to see which
files have been deleted.
Next Steps
----------
The next call is on January 3rd 2019 (Thursday).
Calls are anchored on US time. (8am Pacific)
This call will be for the regular 90 minutes.
http://austingroupbugs.net
An etherpad is usually up for the meeting, with a URL using the date format as below:
https://posix.rhansen.org/p/201x-mm-dd
username=posix password=2115756#