Reason for using custom true false values in frameworks

user_11252200 0
Viewed 262

I was reading the GLFW library and I noticed they use GLFW_TRUE(1) and GLFW_FALSE(0). Now I've already seen that in other frameworks as well,making their own custom true/false identifiers. Is there any reason in creating your own custom true/false enums or classes in a framework? Does it make the code more readable for example? Is it a compatibility issue?

Another programmer speculated that they probably wouldn't want to #include <stdbool.h> but that header is in fact very small and wouldn't overcomplicate dependencies

glfw software-quality software-design frameworks c
4 Answers

I guess it is for backward compatibility reasons. The stdbool.h header was introduced in the C99 standard.

user_178520970

Is there any reason in creating your own custom true/false enums or classes in a framework?

  • support of old or broken compilers (C99 incompatible, do not have stdbool.h and _Bool type)
  • static type checks with external tools (like cppcheck)
  • strong type checking by compiler (thinking of C++ classes with custom conversion)
  • subjective code readability

Does it make the code more readable for example?

Is subjective. For someone, not for someone else.

Is it a compatibility issue?

Most probably yes.

In case of GLFW it was written for windows in ~2002 (according to this site https://www.glfw.org/changelog ). My guess the windows compiler the author used didn't have stdbool.h. Either way, ask the author of the library.

user_90727530

I was reading the GLFW library and I noticed they use GLFW_TRUE(1) and GLFW_FALSE(0). Now I've already seen that in other frameworks as well,making their own custom true/false identifiers. Is there any reason in creating your own custom true/false enums or classes in a framework? Does it make the code more readable for example? Is it a compatibility issue?

If you plan to use your library in different environments, you can easily get to one that lacks those definitions in a header file. The earliest notable case of this, is when the curses library was developded (there was no <stdbool.h> yet, not the bool type defined in the standard library)

In those cases, it would be better to provide one definition yourself, but if you don't want to class with the standard ones, you have to define yours with some prefix that allows you to distinguish your definition from other libraries.

In C, bool is simply a subset of int, and true continues to mean != 0 while false is always 0. If you need to assing some value, some authors have inclined to use -1 as a value for true (which is not normally the case, 1 and -1 are obviously different)

user_38994310

Probably for readability issues and controlling the flow of the framework.

user_178524990
Related