Hacker News Reader

#define FALSE 0 is the common one

Doh, you're right. I had '#define FALSE 0' in my mind. '#define FALSE 1' actually is insane.

In C99 #include <stdbool.h> has the type bool and the constants true and false (even in the "freestanding" flavor). Of course this doesn't save you if you are dealing with old/non-conformant compilers and/or legacy codebases.

It actually defines TRUE and FALSE, and not G_TRUE/G_FALSE. But it does indeed define the gboolean type - it does make code easier to read.

People don't have to invent them, and it's generally annoying as hell when they chose to.

So then what are they supposed to do, require a library X which has already invented them, while your app is using library Y which already does the same thing as X?

Use 0 and 1, like everyone else. Those #defines are just meaningless syntactical sugar that get in the way.