Path: utzoo!attcan!uunet!snorkelwacker!bloom-beacon!primerd!WL1!WL9!DSTONE From: DSTONE@WL9.Prime.COM Newsgroups: comp.lang.c Subject: Re: Difference between char and unsigne Message-ID: <20900004@WL9.Prime.COM> Date: 19 Jul 90 09:59:00 GMT References: <34292@ut-emx.UUCP> Lines: 20 Nf-ID: #R:ut-emx.UUCP:-3429200:WL9:20900004:000:815 Nf-From: WL9.Prime.COM!DSTONE Jul 19 09:59:00 1990 Karl Heuer writes: > Now, since all normal% characters are contained within the intersection of > `char' and `unsigned char', you can safely ignore this botch if you *know* > you're dealing with the most restrictive kind of text. > % Besides being true of all ASCII characters, this guarantee is also extended > to the entire C source character set in non-ASCII alphabets. Basically this > forbids an EBCDIC implementation from making `char' a signed 8-bit type. I thought this was true, too: but where is it in the standard? I have RTFS without success. The only place I can find it is in K&R I Reference Manual section 6.1 ("it is guaranteed that a member of the standard character set is non-negative"). David Stone speaking for myself, and not Prime Computer.