|omg DON'T get me started on *that* mess (grin).|
Even the !FALSE trick doesn't work:
if (x == TRUE)…
if (x) …
Still give different results, since !FALSE to the compiler is !0 which is 1, so the first if is really "if (x == 1) …" for most compilers.
On Jul 1, 2013, at 4:20 PM, Sean Conner <firstname.lastname@example.org> wrote:
Actually, I've seen plenty of C code improperly define the value for true.