I wrote CMC> Assuming that char is unsigned may be fine if you can
when, of course, I meant to say that assuming that char is either signed *or* unsigned is a bad idea. Whoops. C. P.S. If you want a signed char, you should declare it as `signed char'; for an unsigned char, declare it as `unsigned char'. Code with the wrong assumptions for a given platform can still be compiled on that platform by using the `-fsigned-char' or `-funsigned-char' options to gcc. Even better, since most of the broken code assumes that char is signed, simply using `-fsigned-char' for all platforms will solve the problem by telling the compiler to always assume that char is signed. That's still not as good a solution as having the code use sensible types such as `int8_t', `uint8_t', and so on. +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ Behind the counter a boy with a shaven head stared vacantly into space, a dozen spikes of microsoft protruding from the socket behind his ear. +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ C.M. Connelly [EMAIL PROTECTED] SHC, DS +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
