> > I agree with you that people such be $#@! explicit about the > > signedness of their chars, based on my limited experience :-) > > Make that declare as 'char' or 'unsigned char' and (cast) as > appropriate. Spelling 'signed char' out in full looks messy. Yea, I think that's at the root of my visceral reaction to char signedness. Back when there was no ANSI standard, there was also no "signed" keyword, making it absolutely impossible on those platforms that chose to make "char" unsigned by default to get a signed small integer type. (Actually, the other hole in signedness that also "bit" me many times when trying to port code was bit fields - some compilers implement 3 possible signed states for bit fields - signed, unsigned, and "extracted as unsigned, but treated as signed thereafter" - bleh!)