Eric Pouech wrote:
> in a strict portability consideration, I agree. But, since most code is
> first written on Linux with GCC (thus meaning char == signed char), I
> really think this ia an easier solution to enforce char == signed char
> in the core Wine implementation.
Careful; "Linux with GCC" doesn't necessarily mean char == signed char ...
Of course "Linux *on Intel* with GCC" implies this, but there are at
least two Linux architectures I know of where gcc defaults to char ==
unsigned char (those are PowerPC and S/390).
B.t.w. there is typcially a good reason why the architecture might choose
to set char == unsigned char; normally this is done because unsigned
char comparisons can be more efficiently implemented than signed ones
on this architecture. So enforcing the less efficient type to be used
where not really necessary might not be a good idea.
Bye,
Ulrich
--
Dr. Ulrich Weigand
[EMAIL PROTECTED]
