Hmmm.   I guess CCS C is not ANSI C.  This makes me Antsy, see?  (groan).

But seriously,  In CCS, integers default to Unsigned integers unless
otherwise specified (according to my book. So far, opinions vary on this!)

So INT is not already a signed type.  It seems the CCS compiler must be
converting the unsigned INT to a signed INT, then assuming it is a negative
number.

I may have the real lowdown from the CCS help line tomorrow.

CCS also doesn't seem to be case sensitive (if it was then I turned it off
long ago and forgot about it.)  Case sensitivity bugs drive me nuts.  My
brain, you see, is not cAsE seNsITivE whEn tYpiNG CoDe.


-- Lawrence


----- Original Message -----
From: "Bob Ammerman" <RAMMERMAN@prodigy.net>
To: "Lawrence Lile" <llile@toastmaster.com>
Sent: Monday, October 16, 2000 4:08 PM
Subject: Re: Signed Int vs Int


> I don't know about CCS "C", but in ANSI "C":
>
> "int" _is_ already a signed type.
>
> "Signed"  _isn't_ a valid type qualifier, although "signed" is.
>
> in ANSI "C":
>
> given:
>
> int an_int;
> unsigned int an_unsigned_int;
>
> then comparisons between 'an_int' and 'an_unsigned_int' will be treated as
> an unsigned comparison.
>
> (per "Standard C, A Reference" by Plauger and Brodie, pp88-89).
>
> Bob Ammerman
> RAm Systems
> (contract development of high performance, high function, low-level
> software)
>
>

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.