Defect report from : Andrew Josey , The Open Group
(Please direct followup comments direct to yyyyyyyyyyyyyy@xxxxxxxxxxxxx)
@ page 343 line 13238 section ed objection {nine-bit-bytes}
Problem:
Edition of Specification (Year): 2003
Defect code : 1. Error
Here and elsewhere in XCU we come across statements
of the form : "If the size of a byte on the system is greater than
nine bits, the ... is implementation-defined".
This appears to be for systems outside of the standard, which
requires support for 8 bit bytes
Such occurrences should be stricken.
Action:
In ed, p343 l 13238
delete
"If the size of a byte on the system is greater than nine bits, the format
used for non-printable characters
is implementation-defined."
In ex p380 l14708
delete
"If the size of a byte on the system is greater than 9 bits...
implementation-defined."
In file p448 l17345
delete
"If the size of a byte on the system is greater than 9 bits...
implementation-defined."
In lex table 4-10 p540 l20802
delete
"If the size of a byte on the system is greater than nine bits...
implementation-defined."
In the RATIONALE for lex l21021 p544
Change from
"The description of octal and hexadecimal-digit escape sequences
agrees with the ISO C standard use of escape sequences. See the RATIONALE for
ed for a discussion of bytes larger than 9 bits
being represented by octal values. Hexadecimal values can
represent larger bytes and multi-byte
characters directly, using as many digits as required."
to
"The description of octal and hexadecimal-digit escape sequences
agrees with the ISO C standard use of escape sequences."
In the RATIONALE for ed p348 l13451-13458
Delete
"Systems with bytes too large to fit into three octal digits must
devise other means of displaying non-printable characters.
Consideration was given to requiring that the number of octal
digits be large enough to hold a byte, but this seemed to be too
confusing for applications on the vast majority of systems where
three digits are adequate. It would be theoretically possible for
the application to use the getconf utility to find out the CHAR_BIT
value and deal with such an algorithm; however, there is really no
portable way that an application can use the octal values
of the bytes across various coded character sets, so the
additional specification was not worthwhile."
In od, p682 l 26379
delete
"If the size of a byte on the system is greater than nine bits...
implementation-defined."
In sed p845 l32699
delete
"If the size of a byte on the system is greater than 9 bits...
implementation-defined."
In tr, p927 l35871
delete
If the size of a byte on the system is greater than nine bits...
implementation-defined."
|