All
Enclosed are the minutes from our last call this year. Happy Holidays!
regards
Andrew
---------------
Minutes of the 19th December 2019 Teleconference Austin-993 Page 1 of 1
Submitted by Andrew Josey, The Open Group. 20th December 2019
Attendees:
Mark Ziegast, SHware Systems Dev.
Don Cragun, IEEE PASC OR
Joerg Schilling, FOKUS Fraunhofer
Andreas Grapentin, HPI, University of Potsdam
Eric Ackermann, HPI, University of Potsdam
Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR
Geoff Clare, The Open Group
Andrew Josey, The Open Group
* General news
This was the last meeting for this year. Happy Holidays to all!
* 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
http://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.
Bug 1216 - Eric to ask if The Open Group is willing to sponsor this interface,
referencing bug note 4478.
* Current Business
Bug 1298: ed CONSEQUENCES OF ERRORS unclear about diagnostic message Accepted
http://austingroupbugs.net/view.php?id=1298
This bug was re-opened to look at bugs 606 and 1290.
606 was closed as a duplicate of bug 0001290 since, although it
predates that bug, 1290 is tagged tc3-2008 whereas this was originally
tagged issue8.
The relationship on 1290 was replaced to note the duplicate.
Bug 1300: clarify GLOB_MARK behavior Accepted as Marked
http://austingroupbugs.net/view.php?id=1300
This item is tagged for Issue 8.
An interpretation is required (which also impacts bug 1301).
Note that the changes specified below address the issues raised in
this bug report and in 0001301.
Interpretation response:
The standard states "Each pathname that is a directory that matches
pattern shall have a <slash> appended.", and conforming implementations
must conform to this. However, concerns have been raised about this
which are being referred to the sponsor.
Rationale:
Requiring the pathname "/" to be converted to "//" and the pathname
"//" to be converted to "///" was not considered when this issue
was first standardized.
Notes to the Editor (not part of this interpretation):
On page 1109 line 37544 section glob(), change:
Each pathname that is a directory that matches pattern shall
have a <slash> appended.
to:
For each pathname that matches pattern and is determined to be
a directory after pathname resolution, process the pathname so
the result is as if the following steps are applied in order:
If the pathame is <slash>, do not modify the pathname and
skip the remaining steps.
If the pathname is <slash><slash> and the implementation
handles pathname resolution of a pathname starting with
exactly two successive <slash> characters differently than
it handles a pathname starting with only a single <slash>,
do not modify the pathname and skip the remaining steps.
If the pathname does not end with a <slash>, append a <slash>
to the pathname and skip the remaining steps.
A <slash> may be appended to the pathname.
If there are multiple <slash> characters at the end of the
pathname, all but one of those trailing <slash> characters
may be removed from the pathname.
Append the following new paragraphs to the glob() rationale after
P1112, L37648:
Earlier versions of this standard defined the behavior associated
with the flag GLOB_MARK as:
Each pathname that is a directory that matches pattern shall
have a <slash> appended.
This was undesirable if the matched pathname was <slash> or if
the matched pathname was <slash><slash> and the implementation
treats a leading <slash><slash> differently than it treats a
pathname with a single leading <slash>. Only a few implementations
were known to conform to this requirement (maybe only one) and
there was a lot of variation in the way other implementations
behaved. The current wording allows many of the alternative
behaviors that were observed, except that the pathnames "/" and
"//" (if it is treated differently than "/") must not be modified.
Implementations should consider the following much simpler
requirement (which is allowed by the current standard) when
processing the GLOB_MARK flag:
Each pathname that matches pattern, is determined to be a
directory after pathname resolution, and does not end with
a <slash> shall have a <slash> appended.
Bug 1301: clarify glob("/", GLOB_MARK, ...) behavior Accepted as marked.
http://austingroupbugs.net/view.php?id=1301
(see 1300)
Next Steps
----------
Apologies in advance:
Geoff Clare 2020-01-06, 2020-01-09
Mark Ziegast 2020-01-06, 2020-01-09
The next calls are on:
January 6 2020 (Monday)
This call will be for 60 minutes.
January 9 2019 (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.
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#
--------
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
