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.

  • arthur@lemmy.zip
    ·
    2 months ago

    I would use an Enum if available in the language:

    • More meaningful
    • Extendable
    • Lower chance of misuse
    • No naming problem
  • thepiguy@lemmy.ml
    ·
    2 months ago

    It shouldn't matter if the user is leaning or jumping or whatever. If the variable says "is_person_standing" then the only information I get out of it is whether the person is standing or not. It would be much simpler to use enums to represent the state if there are such other options. If you don't have enums in your language, then use constants.

  • ℕ𝕖𝕞𝕠@midwest.social
    ·
    2 months ago

    is_person_standing is a good use case for enumeration, not a bool, if you care about whether they're sitting or lying prone or hovering &c.

  • lapis [fae/faer, comrade/them]
    ·
    2 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).

  • ____@infosec.pub
    ·
    2 months ago

    PolicyCancelledByCarrier

    If canx notice has been received, processed, blah blah, eventually it’s set to true.

    If/when a reinstatement is received, set to false.

    Zero ambiguity, something along that line saved my tail when working with devs in different countries with different insurance customs.

    Carrier sent letter telling policy holder to get bent because “fuck you, pay me?” Field is true.

    Otherwise, or with reinstatement letter, field true.