"Sander Vesik" <sander@haldjas.folklore.ee> writes:
|>
|> C has no character type - it just has a (usually, as such is not
|> guranteed by the standards) ultra-short integer type that is called
|> char. There isn't much special about that type in fact many functions
|> that appear to be character related return or take int arguments
|> instead.
|>
|> sizeof(long) == sizeof(int) == sizeof(short) == sizeof(char) == 64 bits
|> is a valid, standards-conformant (even if slightly odd) choice for
|> a C runtime - and one that has i think been made at least once.

There is a problem here for hosted implementations (i.e. ones that
support the library): the macro EOF. The consensus seems to be that
that choice is permitted only for free-standing (embedded) C
implementations. But it definitely is for them, and I have heard of
such implementations, too.