Minutes of the 22nd September 2011 Teleconference     Austin-538 Page 1 of 1
Submitted by Andrew Josey, The Open Group.    September 26 , 2011

Attendees
Andrew Josey, The Open Group
Don Cragun,  PASC OR
Mark Brown, IBM, TOG OR 
Jim Pugsley, Oracle
Geoff Clare, The Open Group
Nick Stoughton, USENIX, ISO/IEC OR
Eric Blake, Red Hat


Andrew reported he received feedback from IEEE on the
mandatory editorial coordination. Draft 4 is now being
prepared on an IEEE template. In parallel we have also now
started a merged version of the Base specifications with the
TC1 changes integrated. The ideal plan would be to
have that out at or prior to the Draft 4 review.

Nick reported that at SC22 we will need to reaffirm the
current standard within the next year.

He also reported that the ISO POSIX Advisory Group had
been disbanded by SC22, and that the ISO Organizational
Representatives would make recommendations direct to
SC22 when necessary.

* New Business

Bug 0000449: add ;& case statement fallthrough to sh  Accepted as marked
http://austingroupbugs.net/view.php?id=449

This item is tagged for Issue 8


At line 73307 [XCU 2.9.4.3 Case Conditional Construct], change:

The control operator ')' terminates a list of patterns corresponding
to a given action. The compound-list for each list of patterns, with
the possible exception of the last, shall be terminated with ";;".

to:

The control operator ')' terminates a list of patterns corresponding
to a given action. The terminated pattern list and the following
compound-list is called a case statement <i>clause</i>. Each case
statement clause, with the possible exception of the last, shall be
terminated with either ";;" or ";&".

At line 73322, change:

After the first match, no more patterns shall be expanded, and the
compound-list shall be executed.

to:

After the first match, no more patterns in the case statement shall be
expanded, and the compound-list of the matching clause shall be executed.
If the case statement clause is terminated by ";;", no further clauses
shall be examined. If the case statement clause is terminated by ";&",
then the compound-list (if any) of each subsequent clause shall be
executed, in order, until either a clause terminated by ";;" is reached
and its compound-list (if any) executed or there are no further clauses
in the case statement.

At line 73326, change:

Otherwise, the exit status shall be the exit status of the last command
executed in the compound-list.

to:

Otherwise, the exit status shall be the exit status of the last command
executed in the compound-list of the last clause to be executed.

At line 73501 [XCU 2.10.2 Shell Grammar Rules], change:

%token AND_IF OR_IF DSEMI
/* '&&' '||' ';;' */

to:

%token AND_IF OR_IF DSEMI SEMI_AND
/* '&&' '||' ';;' ';&' */

At line 73588, change:

case_item : pattern ')' linebreak DSEMI linebreak
            | pattern ’)’ compound_list DSEMI linebreak
            | ’(’ pattern ’)’ linebreak DSEMI linebreak
            | ’(’ pattern ’)’ compound_list DSEMI linebreak

to:

case_item : pattern ')' linebreak DSEMI linebreak
            | pattern ’)’ compound_list DSEMI linebreak
            | ’(’ pattern ’)’ linebreak DSEMI linebreak
            | ’(’ pattern ’)’ compound_list DSEMI linebreak
            | pattern ')' linebreak SEMI_AND linebreak
            | pattern ’)’ compound_list SEMI_AND linebreak
            | ’(’ pattern ’)’ linebreak SEMI_AND linebreak
            | ’(’ pattern ’)’ compound_list SEMI_AND linebreak

At line 124793 [XRAT C.2.9.4 Compound Commands], change:

Consideration was given to requiring break inside the compound-list to
prevent falling through to the next pattern action list. This was
rejected as being nonexisting practice. An interesting undocumented
feature of the KornShell is that using ";&" instead of ";;" as a
terminator causes the exact opposite behavior—the flow of control
continues with the next compound-list.

to:

Consideration was given to requiring break inside the compound-list to
prevent falling through to the next pattern action list. This was
rejected as being nonexisting practice. Instead, the standard now
requires a feature first added in KornShell that using ";&" instead of
";;" as a terminator causes the exact opposite behavior—the flow of
control continues with the next compound-list.

Although the standard is explicit that the order of side-effects due
to pattern expansion within a single clause is unspecified, it is clear
that patterns are expanded in clause order, and that no further pattern
expansions are attempted after the first match. That is, the following
example is required to output "1.0":

x=0 y=1
case 1 in
  $((y=0)) ) ;;
  $((x=1)) ) ;&
  $((x=2)) ) echo $x.$y ;;
esac 



Bug 0000465: is the list of special built-ins exhaustive (is "local" special)? OPEN
http://austingroupbugs.net/view.php?id=465

This was discussed during the meeting. Don took an action
to add a note to the bug recording the discussions and
recommendations submitted by David Korn (this action
was completed)

It was agreed to request the submitter, Jonathan to submit
suggested word changes. (Andrew will take the action
to contact him)


Bug 0000466: date +%C problem  Accepted as Marked
http://austingroupbugs.net/view.php?id=466

This item is tagged Issue 8.

Replace lines 82877-82957 [XCU date DESCRIPTION] with:

+format When the format is specified, the output shall be formatted
as if by strftime() with the specified format string, and a timeptr
argument that is the equivalent of localtime(&now) if -u is not
specified or gmtime(&now) if -u is specified, where now is an object
of type time_t containing the return value of time(0).
A <newline> shall always be appended to the output of strftime(). 


Bug 0000493: Behaviour of getpwent() after endpwent() is not clear  Accepted
http://austingroupbugs.net/view.php?id=493

This item is tagged TC2-2008

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:
These sets of interfaces should act consistently.

Notes to the Editor (not part of this interpretation):
Make the changes suggested in the Desired Action.


Bug 0000494: PPID shell variable should not be dependent on UP option Accepted
http://austingroupbugs.net/view.php?id=494

This item is tagged TC2-2008

It was noted that the UP option is actually mandatory in issue 7,
so everyone must have implemented this anyway.


Bug 0000374: malloc(0) and realloc(p,0) must not change errno on success  OPEN
http://austingroupbugs.net/view.php?id=374

This item is open pending resolution of a C1x defect report.

Bug 0000331: Add 'x' mode to fopen and freopen to force O_EXCL (and declare that fdopen ignores 'x')  Duplicate
http://austingroupbugs.net/view.php?id=331

This item has been closed as a duplicate of 411


Next Steps
----------

The next call is on October 6th at 08:00 Pacific and
will continue processing defect reports.

This call will be for the regular 90 minutes.

http://austingroupbugs.net

See the calendar for the list of dialup numbers.

An IRC  channel will be available for the meeting
 irc://irc.freestandards.org #austin

ICAL: http://www.google.com/calendar/ical/nvctqtstkuni3fab9k3jqtrt4g@group.calendar.google.com/public/basic
XML: http://www.google.com/calendar/feeds/nvctqtstkuni3fab9k3jqtrt4g@group.calendar.google.com/public/basic