> So we might want to consider making UT_UCSChar 32 bit by
> default, and add a compile-time option for those who would want 16-
> bit version only. This should not amount to much more than
> changing the typedef for UT_UCSChar and cleaning up any poorely
> designed code that has got the size of UT_UCSChar hardwired, but
> from what I recall, there should be hardly any.
Isn't the real problem where we want to do
UT_UCSChar c = 0x10000;
etc. (which is probably the case at the moment)? Making the jump to 32 bit
is probably a lot saner & safer than maintaining both 16 & 32-bit.
Frank, who's out of his depth
Francis James Franklin
[EMAIL PROTECTED]
It's getting them wrong that is living, getting them wrong and wrong and
wrong and then, on careful reconsideration, getting them wrong again.
That's how we know we're alive: we're wrong.
--- Philip Roth
