Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!unixhub!ditka!comeau
From: comeau@ditka.Chicago.COM (Greg Comeau)
Newsgroups: comp.lang.c++
Subject: Re: 64 bit architectures and C/C++
Message-ID: <38475@ditka.Chicago.COM>
Date: 8 May 91 18:39:16 GMT
References: <12563@dog.ee.lbl.gov> <312@nazgul.UUCP> <184@shasta.Stanford.EDU>
Sender: news@ditka.Chicago.COM (Pulitzer at ditka)
Reply-To: comeau@csanta.attmail.com (Greg Comeau)
Organization: Comeau Computing
Lines: 26

In article <184@shasta.Stanford.EDU> shap@shasta.Stanford.EDU (shap) writes:
>In article <312@nazgul.UUCP> bright@nazgul.UUCP (Walter Bright) writes:
>>The most aggravating problem we have is it seems we (Zortech) are the only
>>compiler for which: 	char signed char unsigned char
>>are all distinct types! For example,
>My reading of the ANSI standard was that 'char' was identically equally
>to exactly one of 'unsigned char' or 'signed char', but that the choice
>was up to the compiler.

That may be so, but that doesn't say that it's not another type in and
of itself even though we don't know its sign or which one "it's like".

I any event ANSI C tells us "The three types char, signed char, and unsigned
char are collectively call the ``character types''." while the ARM
tells us "Plain char, signed char, and unsigned char, are three distinct
types.".

Remember also we've got "unsigned preserving" vs "value preserving"
mess to contend with (of which I currently forget which C++ follows).

- Greg
-- 
	 Comeau Computing, 91-34 120th Street, Richmond Hill, NY, 11418
                          Producers of Comeau C++ 2.1
          Here:attmail.com!csanta!comeau / BIX:comeau / CIS:72331,3421
                     Voice:718-945-0009 / Fax:718-441-2310