This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: proposed Opengroup action for c99 command (XCU ERN 76)
- From: rridge at csclub dot uwaterloo dot ca (Ross Ridge)
- To: Geoffrey Keating <geoffk at geoffk dot org>
- Cc: Ross Ridge <rridge at csclub dot uwaterloo dot ca>, gcc at gcc dot gnu dot org
- Date: Wed, 12 Oct 2005 14:59:34 -0400 (EDT)
- Subject: Re: proposed Opengroup action for c99 command (XCU ERN 76)
> > Not really a problem for a number of reasons. First, it's LC_CTYPE
> > you're thinking of. Second, the narrow character set can only be 16-bits
> > wide if "char" is 16-bits. Thirdly, if the character set that LC_CTYPE
> > selects isn't superset of the POSIX portable character set then result
> > is undefined. So if <stdio.h> happens to writen using characters only
> > from C basic character set (which is a subset of the portable character
> > set), there isn't a problem.
>
> My concern would be that it would be written using only characters
> "from the basic C character set", but the actual byte values that
> represent those characters might differ. For instance, if POSIX
> allows LC_CTYPE=EBCDIC (or equivalent).
If setting LC_CTYPE=EBCDIC selects a character set that is a superset of
the POSIX portable character set on that POSIX system then there isn't
a problem. If it selects a character set that isn't a superset, say
because the POSIX portable character set is encoded using ASCII on that
system, then the effect is undefined, and so there's also isn't a problem.
Ross Ridge
--
l/ // Ross Ridge -- The Great HTMU
[oo][oo] rridge@csclub.uwaterloo.ca
-()-/()/ http://www.csclub.uwaterloo.ca/u/rridge/
db //