What I mean is: some boolean flags are perfect for the real world phenomenon they are representing e.g. is_light_on makes you understand perfectly that when it is true the light is on and when it is false the light is off.
There are other cases in which if you didn’t write the code and you don’t read any additional documentation, everything is not clear just by looking at the variable name e.g. is_person_standing, when true it’s clear what that means but when false, is the person sitting? Lying? Kneeling?
I’m obviously not talking about cases in which there are more states, boolean would of course not be a good solution in those cases. I’m talking about programs in which there are only two states but it’s not obvious, without external knowledge, which ones they are.
In your example, it’s implied that any pose other than standing is irrelevant in that context. Why do you need to care if you don’t need to care?
Maybe I explained myself poorly, what I was asking is about cases in which there are only two states e.g. standing and sitting and they are equally important so is_person_standing would not be a good name
Couldn’t you just add a comment that says that if the variable is false, then the person is sitting?
Or if the programming language supports it, you could add a getter called is_person_sitting that returns !is_person_standing.
If that sort of distinction is important, it’s best practice to eschew the boolean type and instead define an enumerated type in order to remove such ambiguity.
Makes sense, forget booleans my new best friends are enums
Yup. If a boolean were to be used in this case, it’d be an additional variable that you need to update in addition to Enum stance.
No need to deal with the bool, if you can instead just check if (stance == 'standing ')
Probably better to use enums instead of strings