> Actually, the size of unsigned char doesn't matter, as C language > rules require that all types be promoted to 'int' before math > takes place, unless that promotion would have no affect on the > final result.
I was not aware of such a rule. In fact, on the platform on which I learned C, "sizeof (char)" returned 1, while "sizeof (int)" returned 2. But let's not argue about that - I'll just believe you (and I don't feel like digging in the ANSI C specification right now). Still, it doesn't change the essence of what I said. Fine, let it be "unsigned int" instead of "unsigned char" - the rest is still true. If the macro is modified in the way I suggested, it will work correctly both in a PNO and in a 68k application, without generating any additional code (compared to what it generates now) in a PNO. That is the better solution, IMNSHO. If not that, at least the documentation needs to be changed to say clearly that this macro works only in PNO applications, so that people like me and Benjamin don't bang our heads onto silly compiler errors when trying to use it... :-) Regards, Vesselin -- For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
