Re: [Nmh-workers] Compiler warnings and signed vs. unsigned char, again

[Lyndon Nerenberg]

On 2013-02-05, at 8:19 AM, Ken Hornstein wrote:

>           The type "char" is always a distinct type from each of "signed
>           char" or "unsigned char", even though its behavior is always just
>           like one of those two.

The reason for this is to allow the "implementation" to chose the 
representation of 'char' that is the most efficient for the underlying hardware 
architecture.

This is less of an issue today than it was in years gone by, but it's still a 
valid one.  Especially in light of the new crop of embedded processors that are 
turning up, where gate constraints could conceivably expose a difference again.

--lyndon