Austin Group Minutes of the 27 Sep 2007 Teleconference Austin-399 Page 1 of 1
Submitted by Andrew Josey, The Open Group. Sep 28, 2007
Attendees
Andrew Josey, The Open Group
Geoff Clare, The Open Group
Mark Brown, IBM, TOG OR
Eric Blake
Ulrich Drepper, Red Hat
Nick Stoughton, USENIX, ISO/IEC OR
Apologies
Don Cragun , Sun, PASC OR
Mats Wichmann, Intel
Mark/Geoff had an action to review ISO C TC3 and
report back on changes needed. It was reported that
no changes are required for ISO C TC3 apart from those
already in the 2004 edition aardvark reports. Andrew
noted that since this is ISO C alignment he would ensure
they are recorded in the SD5 changes arising for D4R.
(Andrew has added XBD bug ERN 53 to the latest set of
SD5 changes)
Andrew has submitted XBD ERN (TMP_MAX conflict with ISO C)
down the interpretations track as Austin-172.
We picked up again on the 2004 aardvark reports.
XBD ERN 88 hold until Don is back
XCU ERN 167 find Accept as marked below
At line 17503, add the following sentence to the Description paragraph:
Each path operand shall be evaluated unaltered as it was provided,
including all trailing slashes; all pathnames for other files encountered
in the hierarchy shall consist of the concatenation of the current path
operand, a slash if the current path operand did not end in one, and
the filename relative to the path operand. The relative portion shall
contain no dot or dot-dot components, no trailing slashes, and only
single slashes between pathname components.
At line 17748, add a new example:
8. Except for the root directory, and "//" on implementations where
"//" does not refer to the root directory, no pattern given to -name
will match a slash, because trailing slashes are ignored when computing
the basename of the file under evaluation. Given two empty directories
named foo and bar, the following command:
find foo/// bar/// -name foo -o -name 'bar?*'
prints only the line "foo///".
XBD ERN 89 XBD section 5 file format notation Accept as marked below
At line 3492, change
"pad to the field width; no space padding is performed."
to
"pad to the field width rather than performing space padding,
except when converting an infinity or NaN."
After line 3519 add a new paragraph
"A floating-point number argument representing an infinity shall
be converted in one of the styles "[-]inf" or "[-]infinity"; which
style is implementation-defined. A floating-point number argument
representing a NaN shall be converted in one of the styles
"[-]nan(n-char-sequence)" or "[-]nan"; which style, and the
meaning of any n-char-sequence, is implementation-defined. The F
conversion specifier produces "INF", "INFINITY", or "NAN" instead
of "inf", "infinity", or "nan", respectively."
After line 3529 add a new paragraph
"A floating-point number argument representing an infinity or NaN
shall be converted in the style of an f or F conversion specifier."
After line 3535 add a new paragraph
"A floating-point number argument representing an infinity or NaN
shall be converted in the style of an f or F conversion specifier."
In addition:
In XCU printf change bullet 6
6. The e, E, f, g, and G conversion specifiers need not be supported.
to
6. The a, A, e, E, f, F, g, and G conversion specifiers need not be supported.
Add new text to XBD section 5
a, A
The floating-point number argument representing a floating-point number
shall be converted in the style "[−]0xh.hhhhp±d", where there is
one hexadecimal digit (which shall be nonzero if the argument is a
normalized floating-point number and is otherwise unspecified) before
the decimal-point character and the number of hexadecimal digits after
it is equal to the precision; if the precision is missing and FLT_RADIX
is a power of 2, then the precision shall be sufficient for an exact
representation of the value; if the precision is missing and FLT_RADIX is
not a power of 2, then the precision shall be sufficient to distinguish
different floating-point values in the internal representation used by
the utility, except that trailing zeros may be omitted; if the precision
is zero and the ’#’ flag is not specified, no decimal-point character
shall appear. The letters "abcdef" shall be used for a conversion and the
letters "ABCDEF" for A conversion. The A conversion specifier produces
a number with ’X’ and ’P’ instead of ’x’ and ’p’. The
exponent shall always contain at least one digit, and only as many more
digits as necessary to represent the decimal exponent of 2. If the value
is zero, the exponent shall be zero. A double argument representing an
infinity or NaN shall be converted in the style of an f or F conversion
specifier. A floating-point number argument representing an infinity
or NaN shall be converted in the style of an f or F conversion specifier."
In XBD Chap 5, #
change
For e, E, f, g, and G conversion specifiers, the
to
For a, A, e, E, f, F, g, and G conversion specifiers, the
0 flag
change
For d, i, o, u, x, X, e, E, f, g, and G conversion
to
0 For d, i, o, u, x, X, a, A, e, E, f, F, g, and G conversion
f flag
change
f The floating-point
to
f,F The floating-point
XBD ERN 90 limits.h Accept
XBD ERN 91-94 are duplicates of earlier ERNs
XBD ERN 95 File times update accept
Next Steps
-----------
Andrew will update the aardvark reports with the latest inbound
defect reports.
The next meeting is the 4th October, 16:00 start.
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