Spiros:

> > Standarising C in such a way that int is at least 16-Bit, has this
> > made C both slow and memory-hungry for embedded systems programming?
>
> What's stopping you from using (unsigned) char on such systems ?


I write fully-portably in C89, paying no attention to the particulars
of the platform. If I was to start using char instead of int, I'd
introduce inefficiency on systems whose optimal int type is >= 16
bits.

I think a fair few embedded programmers are starting to use things
like int_fastest_at_least_8 which are defined in C99.

To be a fully-portable programmer both for PC's and for embedded
systems, should we start using these <stdint.h> types?

Martin