Austin Group Minutes of the 13 May Teleconference Austin-211 Page 1 of 1
Submitted by Andrew Josey, The Open Group.              May 14, 2004

Attendees

Andrew Josey, The Open Group
Don Cragun , Sun, PASC OR
Ulrich Drepper, Red Hat
Joanna Farley, Sun 
Mark Brown, IBM, TOG OR 
Nick Stoughton, USENIX, WG15 OR
Natarajan Krishnaswami IBM

Apologies
Dave Butenhof, HP


Draft Status
---------------
Andrew reported that the 2004 Edition was published on April 30
and a hardcopy run has gone to the printers.

The final ISO version of Technical Corrigendum 2 (just the changes document) 
document has been sent to ANSI. Andrew noted that
at the ISO level this will be designated TC1 to ISO/IEC 9945:2003.

Andrew reminded folks that he is doing a fresh run of Austin Group Shirts,
and that he recommends folks club together to save shipping costs
(i.e. shipping for 2 or more items is reduced over just 1)
[Also I have a number of clearance sets of the old
standard see http://www.opengroup.org/pubs/catalog/un.htm ]


Defect Report Processing
-------------------------
The group picked up on the latest batch of defect reports,
which are available at the following URL:
http://www.opengroup.org/austin/aardvark/latest/

XBD ERN 7 , BRE nested subpatterns (XBD BRE defn vs regcomp()) OPEN
The group felt it needed more time to research existing behavior.

XBD ERN 8  aio_suspend needs restict in prototypes REJECT
The propose change is not necessary.  Since the arguments are const,
they can not be affected by aliases.

XBD ERN 9 option constants  Accept as Marked below
The standard requires that if a symbolic constant 
is not defined in the unistd.h header, then a runtime method
(sysconf()/pathconf() or getconf) must be used to  determine at runtime
if the associated option is supported; absence of a
symbolic constant does not imply that the associated
headers and functions will be available.

This allows for example, additional packages to be added
to a system to add support for new options without having to
update unistd.h.

This request may relate to a misunderstanding of the current rationale in
unistd.h.  The unistd.h rationale relates to the values -1,0 and 200112L
for the macro. The rationale does not talk to the macro not being defined.

The following change to the unistd.h rationale is recommended for
a future edition:

Change from:
"Any application must consider the following three cases for each option:"

to

"If the corresponding symbolic constant is defined in the header,
applications must consider the following three cases for each option:"

And at at the end of the section:
"If the corresponding symbolic constant for an option is not defined
in the header, applications must query at runtime to determine which
of the three cases as above describe the support for the option in the
current implementation."


XBD ERN 10  wording in XBD Character Set OPEN

The group felt that the wording was not ambiguous. There
was consideration floated for a possible change of the words
"byte order" -> "byte sequence" but conclusion was not
reached as yet. This is left open for the next call.



Next Steps
-----------
Andrew  will update the aardvark reports with the latest inbound
defect reports.

There are a number of open action items outstanding:
1. Don Cragun Pathname Resolution proposal
2. Larry Dwyer system() and threads
3. Joerg Schilling wording for XCU ERN 1 pax
4. Further investigation for XCU ERN 18.

The next teleconference call is scheduled for May 20 2004