JG> #define TRUE  0
JG> #define FALSE !TRUE
PC> ~~~   ^^^^^^^^^^^^^^^^^^
PC> I think defining FALSE to a non-zero value would be a bad habit to get
PC> into, it would be better to always assume FALSE to be zero.

It's a great case for not using macros like that in the first
place.  C already has true/false abilities as part of the language.
BFN.  Paul.
@EOT:

---