Minutes of the 8th October 2009 Teleconference     Austin-467 Page 1 of 1
Submitted by Andrew Josey, The Open Group.             October 9 , 2009

Attendees
Andrew Josey, The Open Group
Don Cragun,  PASC OR
Geoff Clare, The Open Group
Mark Brown, IBM, TOG OR 
Nick Stoughton, USENIX, ISO/IEC OR

Apologies
Ulrich Drepper, Red Hat


We discussed the interpretations that were circulated on August 29th
and which completed their review on September 30th.
We noted that all can be approved apart from #74 which was modified
during the review period. The 30 day clock should be extended
for #74 from the date of modification.

Action: Andrew to update the remaining interpretations, to move
Interpretation Status to Approved, and to use Mantis bug # 109
bugnote 214 as a template. Where possible we should edit the
existing bugnote field, otherwise add a new final accepted text if
we felt that might cause some information to be lost.


We looked at the mailing list for topics not yet reported as bugs.
Mail sequence 12714 on trap rationale was discussed and a new
bug entered, bug #163
http://austingroupbugs.net/view.php?id=163
Action: on Geoff to propose a resolution

We proceeded to review the bugs in Mantis

Mantis #114 , dot exit status  OPEN
http://austingroupbugs.net/view.php?id=114

Action: Andrew to contact David Korn.
Completed. David's response follows:

--quote--
The wording is somewhat ambiguous, but the intent was not.

In Bourne shell and ksh88, if a readable file is not found,
this is an error.  With an interactive script it is fatal and
with an interactive script it is not.  Since it is an error, it
must have a non-zero exit status.  It is not a syntax error therefore
cannot be found with sh -n.

The Exit Status line refers to the case where the file is readable.
If the file is empty (or just comments), and therefore no command
is executed, then the exit status will be zero.

It would make no sense for a command that terminates due to an
error to return a zero exit status.

One could argue that the exit status should be 127 in the case the file
file was not foud, and 126 if it is not readable, but this would
represent a change.

As far as the proposed change:

The proposed change for dot is incorrect in that an interactive script will
abort if the file is not found or is not readable as currently described.
In the case that the . script has a syntax error, I don't think that
the shell should abort, but this is debatable.

For eval, a syntax error should cause eval to have a non-zero exit status.
I would eliminate "and the shell did not abort".  I don't know why eval
should cause the shell to abort.

For trap, the value of $? after the trap should be the value before
the trap so a syntax error would not effect $?
I don't understand why the shell would abort.  I don't think that a syntax
error should effect the value of $?.  It doesn't with historical practice.

--end quote--

#124 Tilde Expansion Accept as marked
http://austingroupbugs.net/view.php?id=124


#146 symlinkat failure cases OPEN
http://austingroupbugs.net/view.php?id=146
Action: Geoff to propose  a resolution.

#159 getopts Accept as marked
http://austingroupbugs.net/view.php?id=159
See note http://austingroupbugs.net/view.php?id=159#c244

#160 web page issue  OPEN
http://austingroupbugs.net/view.php?id=160
We decided we need to add a new project for web site issues
and html translation etc.

#161  mkdir -p through dangling symlink Accept as marked
http://austingroupbugs.net/view.php?id=161
See note http://austingroupbugs.net/view.php?id=161#c247

#162  Determining System Endianess during Preprocessing OPEN
http://austingroupbugs.net/view.php?id=162
We were leaning towards a reject on this issue as we feel it
should be based on existing practice. In the end we decided
the item should be forwarded to the C committee.
Action on Nick to forward.


Next Steps
----------
The next call will be on October 15 at 16:00 UK time/08:00 Pacific
to carry on with the defect reports

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