Re: [cc65] why this doesn't work?

On Sun, Jun 6, 2010 at 11:25 PM, Ullrich von Bassewitz <uz@musoftware.de> wrote:
> The C standard doesn't define the signedness of type "char", this decision is
> up to the implemention. Because of obvious reasons, cc65 implements them as
> unsigned chars. Any code that makes an assumption about the signedness of
> plain char is non portable.
Ah yes, that's got to be the most absurd thing about a language known for its
portability.  As a programmer, you can't even count on the size your
variables.
(Nothing against any particular implementation of a C compiler, of
course.)  I guess
this refers more to int and long, etc., but it's all in the same vein.

>> Every C compiler I have ever used, including CC65, has considered it
>> signed (at least by default).
>
> For cc65, this is wrong.   .....
Thanks for the correction...  Better to get that drilled in now than
later.  BTW, a
good choice IMO.

Thanks,
// Steve
----------------------------------------------------------------------
To unsubscribe from the list send mail to majordomo@musoftware.de with
the string "unsubscribe cc65" in the body(!) of the mail.