Austin Group Minutes of the 6 Nov 2007 Teleconference Austin-405 Page 1 of 1
Submitted by Andrew Josey, The Open Group. Nov 6 , 2007
Attendees
Andrew Josey, The Open Group
Geoff Clare, The Open Group
Nick Stoughton, USENIX, ISO/IEC OR
Don Cragun , Sun, PASC OR
Apologies
Ulrich Drepper, Red Hat
Mark Brown, IBM, TOG OR
Status update
---------------
* PASC P&P
A vote is in progress on approving a revised PASC policy and
procedures and will pass.
* P1003.27 PAR question from NESCOM
Additional questions had been received from NESCOM about the P1003.27 PAR.
Add C++0X explanation to 7.4
Response: Accept
Make the Purpose clear.
Response:
Change
In 5.4
change
The purpose is to allow portable C++ applications to make use of the POSIX
standard interfaces
to
This standard provides a method to allow
portable C++ applications to make use of the POSIX
standard interfaces
7.2: Is there a contact person for ISO/IEC JTC1 22?
Response:
John Hill
Sun Microsystems
Phone: 717 503 7936
Fax: 717 221 8563
Email: john.hill@sun.com
The SCC2 secretariat details are:
Sally Seitz, ANSI
ISO/IEC/JTC 1/SC 22 Secretariat
25 West 43rd Street
New York NY 10036
Phone: (212) 642-4918
Fax: (212) 840-2298
Andrew completed the action to respond within the IEEE myballot system.
* Austin-175
We updated this interp to add rationale and reword one part.
This is now as follows:
Add to the editors notes
In XCU printf change from:
The argument operands shall be treated as strings if the
corresponding conversion specifier is b, c, or s; otherwise, it
shall be evaluated as a C constant, as described by the ISO C
standard, with the following extensions:
* A leading plus or minus sign shall be allowed.
* If the leading character is a single-quote or double-quote, the
value shall be the numeric value in the underlying codeset of
the character following the single-quote or double-quote.
To:
The argument operands shall be treated as strings if the
corresponding conversion specifier is b, c, or s, and shall be
evaluated as if by the [xref to strtod()] function if the
corresponding conversion specifier is a, A, e, E, f, F, g, or G.
Otherwise, they shall be evaluated as unsuffixed C integer constants, as
described by the ISO C standard, with the following extensions:
* A leading plus or minus sign shall be allowed.
* If the leading character is a single-quote or double-quote, the
value shall be the numeric value in the underlying codeset of
the character following the single-quote or double-quote.
* Suffixed integer constants may be allowed
Suggested rationale:
Earlier versions of this standard specified that arguments for
all conversions other than b, c and s were evaluated in the same
way (as "C constants" but with stated exceptions). For
implementations supporting the floating-point conversions it was
not clear whether integer conversions need only accept integer
constants and floating-point conversions need only accept
floating-point constants, or whether both types of conversions
should accept both types of constants. Also by not distinguishing
between them, the requirement relating to a leading single-quote
or double-quote applied to floating-point conversions even
though this provided no useful functionality to applications that
was not already available through the integer conversions.
The current standard clarifies the situation by specifying that
the arguments for floating-point conversions are evaluated as if
by strtod(), and the arguments for integer conversions are
evaluated as C integer constants, with the special treatment of
leading single-quote and double-quote applying only to integer
conversions.
Austin-092:
Geoff will take an action to provide further additions for uniq,
and changes from last weeks proposals so the editors can track
the differences.
* 2004 Aardvark reports
XCU ERN 106 diff Accept
This needs to be submitted down the interpretations track
The standard is clear, standard is wrong, defect, concerns
are being forwarded to the sponsors.
XCU ERN 107 touch Accept as marked below
On XCU page 920 line 35645, change:
touch [-acm] [-r ref_file | -t time] file...
to:
touch [-acm] [-r ref_file | -t time | -d date_time] file...
Change lines 35651-35655 from:
The time used can be specified by the -t time option-argument, the
corresponding time fields of the file referenced by the -r ref_file
option-argument, or the date_time operand, as specified in the
following sections. If none of these are specified, touch shall
use the current time (the value returned by the equivalent of the
time() function defined in the System Interfaces volume of
IEEE Std 1003.1-2001).
to:
The time used can be specified by the -t time option-argument, the
corresponding time fields of the file referenced by the -r ref_file
option-argument, or -d date_time option-argument, as specified in
the following sections. If none of these are specified, touch shall
use the current time.
After line 35674 add:
-d date_time
Use the specified date_time instead of the current time.
The option-argument shall be a string of the form:
YYYY-MM-DDThh:mm:ss[.frac][tz]
or
YYYY-MM-DDThh:mm:ss[,frac][tz]
where:
YYYY are at least four decimal digits giving the year,
MM, DD, hh, and mm are as with -t time,
ss is the second of the minute [00,60],
T is the time designator, and can be replaced by a single space,
[.frac] is either empty, or a period ('.') or comma (',') followed
by one or more decimal digits, specifying a fractional second,
[tz] is either empty, signifying local time, or the
letter 'Z', signifying UTC.
If the resulting time precedes the Epoch, the behavior is
implementation-defined. If the time cannot be represented as
the file's timestamp, 'touch' shall exit immediately with an
error status.
Add to APP USAGE
If the T time designator is replaced by a space for the -d date_time
option argument the application the space must be quoted
to avoid splitting the argument.
Add to RATIONALE:
The -d date_time format is an ISO 8601 complete representation of date
and time extended format with an optional decimal point followed by a
string of digits following the seconds portion in the seconds format to
specify fractions of a second. It is not necessary to recognize
[+/-]hh:mm and [+/-]hh to specify timezones other than local time and UTC.
The T time designator
in the ISO 8601 extended format may be replaced by space.
Add to EXAMPLES
touch -d 2007-11-12T10:15:30 dwc
touch -d 2007-11-12T10:15:30Z nick
touch -d 2007-11-12T10:15:30,002Z gwc
touch -d "2007-11-12 10:15:30.002Z" ajosey
touch -t 200711121015 cathy
touch -t 200711121015.30 drepper
touch -t 0711121015.30 drepper
touch -a -r mark eggert
XCU ERN 108 dup of 107
Next Steps
-----------
Andrew will update the aardvark reports with the latest inbound
defect reports.
The next calls is Thursday 8 Nov at 16:00 UK
08:00 pacific, 11:00 new york. The calls will last for
90 minutes
See http://www.opengroup.org/austin/.
An IRC channel will be available for the meeting
irc://irc.freestandards.org #austin
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