Subject: Re: Type coersion long->int ?
To: None <email@example.com>
From: der Mouse <mouse@Rodents.Montreal.QC.CA>
Date: 02/03/2000 10:02:04
>> It doesn't have these checks because it's supposed to be fast;
>> that's why all the <ctype.h> functions have undefined behavior for
>> things outside the "standard" range.
> so why the int argument, instead of char?
For the same reason getchar() returns int rather than char: because the
actual range of values is "any value representible as an unsigned char,
I don't know what's done by implementations where int and char are the
same size. seebs? :)
7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B