Minutes of the 12 March 2009 Teleconference     Austin-449 Page 1 of 1
Submitted by Andrew Josey, The Open Group.             March 13 , 2009

Attendees
Andrew Josey, The Open Group
Don Cragun,  PASC OR
Mark Brown, IBM, TOG OR  
Nick Stoughton, USENIX, ISO/IEC OR
Geoff Clare, The Open Group
Ulrich Drepper, Red Hat
David Korn, AT&T

* Bugzilla

We did not discuss this at the call this week.
Mark had circulated a workflow to a small group for some initial
review and comment.


We discussed the set -e issue which had generated much discussion
on the reflector.

We discussed the pros and cons of the two proposals circulated by
Geoff to the austin-mar2008 reflector.

We agreed that the proposed rewording be as follows:


    -e  When this option is on, when any command fails for any of the
        reasons listed in 2.8.1 or returns an exit status greater than zero,
        then the shell immediately shall exit with the following exceptions:

        1)      The -e setting is ignored  when executing
                the compound list following the while, until, if, or elif
                reserved word, a pipeline beginning with !, or any command
                of an AND or OR list other than the last.

        2)      If the exit status of a compound command other than subshell
                command was the result of a failure while -e was being ignored,
                then -e will not apply to this command.

        This requirement applies to the shell environment and each
        subshell environment separately.  For example, in
 
                 set -e; (false; echo one) | cat; echo two
 
        the false command causes the subshell to exit without executing
        echo one; however, echo two is executed because the exit status
        of the pipeline (false; echo one) | cat is zero.  For the
        purposes of -e, all commands within a multi-command pipeline
        are considered to be executed in a subshell environment.

        When a function is executed, its behavior with respect to -e
        shall be as if the function body had appeared in place of the
        function name.

Action: Geoff will submit an aardvark to cover the set -e issue

Action: Don will report back on related changes to the time man page.

* Aardvark

We picked up on the aardvark reports, which are located at
http://www.opengroup.org/austin/aardvark/latest/

XSHbug3 ERN 26 posix_openpt Reject

As no more information was forthcoming the review group has rejected this
item. The rationale is  that they do not think the change is necessary.


XCUbug3 ERN 7  sh exit status OPEN

We had a long discussion. It was suggested that an exit of $? should
cause the shell to exit with an indication of whether it was terminated
from a signal or not.  We agreed that Geoff should rework and resubmit
the proposed changes for the next meeting.

Action: Geoff to circulate revised proposal


Next meeting
------------
The next call will be on March 26 at 15:00 UK time/08:00 Pacific
to carry on with the aardvark. 
NOTE the Timezone changes for DST

See the calendar for the extensive 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