>Unfortunately, people forget about signed-ness issues. I actually wish
>that GCC would warn more about this type of unportable code. (eg,
>detecting an assignment or test between a bare "char" type and a
GCC already warns about comparison between an unsigned type and a negative
constant. It also has the capability to warn about any comparison between a
signed type and an unsigned one, though I don't think this is used by default
when building the kernel because it generates a lot of noise.
There doesn't seem to be any warning for assignment of a negative value to an
unsigned variable, though I don't imagine it would be hard to add.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Apr 30 2000 - 21:00:07 EST