Minutes of the 15 June 2011 Teleconference     Austin-526 Page 1 of 1
Submitted by Andrew Josey, The Open Group.    June 16 , 2011

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

Apologies
Nick Stoughton, USENIX, ISO/IEC OR

As a reminder there are some additional meetings based
on a poll of the core participants. These are in the
Austin Group calendar.

http://www.opengroup.org/platform/single_unix_specification/events.tpl

Andrew reported that he had prepared the annual report to SC22 that
will be submitted shortly.

He also reported that the editors had now completed application
of the bugs filed against TC1-2008 draft 1, and had also completed
the initial pass of splitting out all bugs. They expect to start
adding new changes for the bugs filed since draft 1 over the next two
weeks, with the plan to release draft 2 at the end of the month.

* Old Business

Left open from last time

Bug 0000411: adding atomic FD_CLOEXEC support OPEN
http://austingroupbugs.net/view.php?id=411

Eric still has an open action to complete the changes for popen().


Bug 0000416: Message description for "val" is inconsistent Accepted as Marked
http://austingroupbugs.net/view.php?id=416

Jim had completed an action to research the behaviour of the val utility,
(including the correct format strings for STDOUT to match historic practice).
There had been some discussions on the reflector.

This item is tagged for TC1-2008. An interpretation is required.


Interpretation response
The standard states the requirements for val output, and conforming
implementations must conform to this. However, concerns have been
raised about this which are being referred to the sponsor.

Rationale:
The specified format does not match existing practice, although the
example output does.

Notes to the Editor (not part of this interpretation):
In STDOUT at line 110388 change:

    If standard input is used, a line of input shall be written before
    each of the preceding lines for files containing discrepancies:

    "%s:\n", <input line>

to:

    If standard input is used, for each input line yielding a discrepancy,
    the output shall have the following format:

    "%s\n\n %s: %s\n", <input>, <pathname>, <unspecified string>

    where <input> is the input line minus its terminating <newline>.


In EXAMPLES remove the blank line between lines 110423 and 110424.


* New Business

We picked up on Bug processing for bugs reported against project
Issue 7.

Bug 0000452: fflush changes need counterpart unget[w]c changes Duplicate of 87
http://austingroupbugs.net/view.php?id=452

This bug affects the changes instituted for an approved interpretation
0000087 so this bug is closed as a duplicate of it and it is being
reopened.

New proposed changes have been added to bug 87 and it will be
discussed at a future meeting.
http://austingroupbugs.net/view.php?id=87

Bug 0000454: awk default FS  Accepted
http://austingroupbugs.net/view.php?id=454

This item is tagged for TC1-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:
Existing practice differs from the text.

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


Bug 0000455: incorrect type name in readlink example  Accepted
http://austingroupbugs.net/view.php?id=455

This item is tagged for TC1-2008.

Bug 0000456: mandate binary mode of fmemopen  Future Enhancement
http://austingroupbugs.net/view.php?id=456


Bug 	0000457: omitted word in parameter expansions  Accepted
http://austingroupbugs.net/view.php?id=457

This item is tagged for TC1-2008.

An interpretation is required.


Interpretation response:

The standard states that "word" must be present in these cases, and
conforming implementations must conform to this. However, concerns
have been raised about this which are being referred to the sponsor.

Rationale:

The standard's requirements for ${parameter##} expansion do not
match existing practice, which is to treat it as ${parameter##word}
with word as an empty string. The other requested changes also match
existing practice and should be done at the same time for consistency.

Notes to the Editor (not part of this interpretation):
Make the changes suggested by the submitter.

The desired action was updated in the meeting as follows:
At line 72719, change:

${parameter:−word} Use Default Values. If parameter is unset or null, the
  expansion of word shall be substituted; otherwise, the value of
  parameter shall be substituted.
${parameter:=word} Assign Default Values. If parameter is unset or null,
  the expansion of word shall be assigned to parameter.

to:

${parameter:−[word]} Use Default Values. If parameter is unset or null,
  the expansion of word (or an empty string if word is omitted) shall be
  substituted; otherwise, the value of parameter shall be substituted.
${parameter:=[word]} Assign Default Values. If parameter is unset or
  null, the expansion of word (or an empty string if word is omitted)
  shall be assigned to parameter.

At line 72730, change:

${parameter:+word} Use Alternative Value. If parameter is unset or null,
  null shall be substituted; otherwise, the expansion of word shall be
  substituted.

to:

${parameter:+[word]} Use Alternative Value. If parameter is unset or
  null, null shall be substituted; otherwise, the expansion of word (or
  an empty string if word is omitted) shall be substituted.

At line 72749, add a sentence to ${#parameter}:

If parameter is unset and set -u is in effect, the expansion shall fail.

At line 75752, change:

If parameter is ’*’ or ’@’, the result of the expansion is unspecified.

to:

If parameter is ’#’, ’*’, or ’@’, the result of the expansion is
unspecified. If parameter is unset and set -u is in effect, the
expansion shall fail.

At line 72755, add a sentence:

In each variety, if word is omitted, the empty pattern shall be used.

At line 72756, change "${parameter%word}" to "${parameter%[word]}".

At line 72758, add a sentence:

If present, word shall not begin with an unquoted '%'.

At line 72759, change "${parameter%%word}" to "${parameter%%[word]}".

At line 72762, change "${parameter#word}" to "${parameter#[word]}".

At line 72764, add a sentence:

If present, word shall not begin with an unquoted '#'.

At line 72765, change "${parameter##word}" to "${parameter##[word]}".





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

The next call is on June 16th at 08:00 Pacific and
will continue processing defect reports.
This call will be for the regular 90 minutes.

An extra call is scheduled for June 24th at 07:30 Pacific
for one hour only  and will continue processing defect reports.

http://austingroupbugs.net

See the calendar for the list of dialup numbers.

As we have a number of open defects we will investigate holding 
additional meetings. Andrew will setup a poll to identify timeslots.

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