Alas, I notice the result of an == operation is an int, not a Boolean. Odd,
since it can only return true or false. I fear I'll have a cast on every line
if I want to eliminate all warnings :(
That's a C rule. If you're using C++ and have the 'bool' type turned on,
an equals operation is a bool.
Ben Combee a écrit :
> At 08:22 AM 10/24/2003, Luc Le Blanc wrote:
> >I erroneously assigned a > 255 defined symbol to a UInt8. Shouldn't the
> >CW 8.3 compiler warn me about this truncation that can be detected
> >before runtime? I found the error while debugging:
>
> Did you have "implicit arit
At 08:22 AM 10/24/2003, Luc Le Blanc wrote:
I erroneously assigned a > 255 defined symbol to a UInt8. Shouldn't the
CW 8.3 compiler warn me about this truncation that can be detected
before runtime? I found the error while debugging:
Did you have "implicit arithmetic conversions" turned on in the
I erroneously assigned a > 255 defined symbol to a UInt8. Shouldn't the
CW 8.3 compiler warn me about this truncation that can be detected
before runtime? I found the error while debugging:
// resources.h
#define KeypadNumbersButton 2216
// code.c
#include "resources.h"
UInt8 tab = KeypadNum
