Hi Bo.

 RT>> I think a better definition would be to #define FALSE 0 and TRUE
 RT>> !FALSE - in other words,  nonzero.

 BS> Hmm.. How could the compiler handle that?

you'd get the same result as

#define FALSE 0
#define TRUE 1

because !FALSE os !0 is equal to 1
so ( 2 == TRUE )  would still be false...


 -=> Bye <=-

---