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.

  • lapis [fae/faer, comrade/them]@hexbear.net
    link
    fedilink
    English
    arrow-up
    5
    ·
    7 months ago

    a boolean named is_person_standing seems fine when person states other than standing don’t matter to the program, except for the fact they are not standing.

    which leads to: name the boolean based on the thing relevant to what you’re building (this applies to other variable types, as well).