Why #define TRUE (1==1) in a C boolean macro instead of simply as 1?

Question

I've seen definitions in C #define TRUE (1==1) #define FALSE (!TRUE)Is this necessary? What's the benefit over simply defining TRUE as 1, and FALSE as 0?

Answer 1

I honestly cannot say I have seen this before either....

The only thing I can think of is that the 1 may get trashed inside some calculation

and get mistaken for 0 or something else.

This macro forces a LOGICAL comparison which cannot get trashed or corrupted

accidentally.

Perhaps there is some bit shifting going on and the one may get shifted out to a zero or something.