Minutes of the 4 March 2010 Teleconference Austin-476 Page 1 of 1
Submitted by Andrew Josey, The Open Group. March 6 , 2010
Attendees
Andrew Josey, The Open Group
Don Cragun, PASC OR
Mark Brown, IBM, TOG OR
Ulrich Drepper, Red Hat
Nick Stoughton, USENIX, ISO/IEC OR
Geoff Clare, The Open Group
Eric Blake, Red Hat
Andrew reported that interpretations 173,185,187 and 188 were running
until March 14th, and that some discussions had occurred on the
mailing list at least and 173 and 188. It was agreed to let these
complete their review period before discussing them further.
Andrew also noted that he had done the minor refresh to the html
as planned on February 12 to sweep up known formatting issues reported.
We picked up on the current bugs
Bug #216 Control characters must have single-byte encodings
http://austingroupbugs.net/view.php?id=216 OPEN
Action:Don reported he was still working on this.
Bug #217: The "single subshell" rule for $(( is not sufficient OPEN
Action:Geoff will take an action to propose wording
Bug #218 218: Inconsistencies in pread() and read() errors Accepted
Interpretation required.
The standard states the current pread() and read() error conditions , and
conforming implementations must conform to this. However, concerns have been
raised about this which are being referred to the sponsor.
Notes to the Editor (not part of this interpretation):
Make change suggested by Submitter. This interpretation should be considered
in tandem with 0000215 .
Action:Eric agreed to take an action to look at other uses of ENXIO
for consistency.
Bug #219: Missing statement about pwrite() on file incapable of seeking
Description Accepted
Bug #220: FD_ISSET can use const keyword Rejected
The standard developers felt this was a change not worth doing.
FD_ISSET() _can_ _be_ only a macro. I.e. there doesn't have to be an
underlying function.
The reason the requested change is not worth doing mainly derives
from this statement on the pselect() page:
[...] FD_CLR(), FD_ISSET(), FD_SET(), and FD_ZERO(). It is
unspecified whether each of these is a macro or a function. If a
macro definition is suppressed in order to access an actual
function [...] the behavior is undefined.
Bug #221: poor wording about even quotes in double quoted parameter expansion
OPEN
This item is still be actively discussed on the mailing list
Bug #222: C.2.6.2 needs a reference to C.2.2.3 Accepted
This is an editorial
Bug #223: mq_* routines use char * for data buffer Rejected
The standard developers agree that it would have been better if these
functions had been designed this way to begin with, however they believe
that making the change now will break existing, conforming code with no
real benefit.
Bug #224: awk -F and FS Accepted as Marked
See bugnote 396.
An Interpretation is required@
The standard states the requirements for awk -F, and conforming
implementations must conform to this. However, concerns have been raised about
this which are being referred to the sponsor.
Notes to the Editor (not part of this interpretation):
Change
-F ERE
Define the input field separator to be the extended regular
expression ERE, before any input is read; see [xref to
Regular Expressions].
to
-F sepstring
Define the input field separator. This option shall be
equivalent to
-v FS=sepstring
except that if -F sepstring and -v FS=sepstring
are both used, it is unspecified whether the FS assignment
resulting from -F sepstring is processed in command line
order or is processed after the last -v FS=sepstring.
See the description of the FS built-in variable, and how it is
used, in the EXTENDED DESCRIPTION section.
In the SYNOPSIS change
-F ERE
on lines 77077 and 77078 to
-F sepstring
On line 77091 change
-F ERE
to
the -F sepstring option
At line 77514 change
An extended regular expression can be used to separate fields by
using the -F ERE option or by assigning a string containing the
expression to the built-in variable FS.
to
An extended regular expression can be used to separate fields by
assigning a string containing the expression to the built-in
variable FS, either directly or as a consequence of using the
-F sepstring option.
Next Steps
----------
The next call will be on March 25 at 15:00 UK time/08:00 Pacific
to carry on with the defect reports
(note the timezone difference change)
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