Asklemmy

43989 readers

586 users here now

A loosely moderated place to ask open-ended questions

Search asklemmy 🔍

If your post meets the following criteria, it's welcome here!

Open-ended question
Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
Not ad nauseam inducing: please make sure it is a question that would be new to most members
An actual topic of discussion

Looking for support?

Looking for a community?

Lemmyverse: community search
sub.rehab: maps old subreddits to fediverse options, marks official as such
[email protected]: a community for finding communities

~Icon~ ~by~ ~@Double_[email protected]~

founded 5 years ago

MODERATORS

[email protected]

I know that naming variables is one of the biggest unsolved problems of Computer Science but how would you name a boolean flag to be self explanatory? (lemmy.ml)

submitted 6 months ago* (last edited 6 months ago) by [email protected] to c/[email protected]

22 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 14 points 6 months ago (1 children)

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?

[–] [email protected] 0 points 6 months ago (2 children)

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

[–] [email protected] 17 points 6 months ago* (last edited 6 months ago) (2 children)

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.

[–] [email protected] 5 points 6 months ago

Makes sense, forget booleans my new best friends are enums

[–] [email protected] 2 points 6 months ago (1 children)

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 ')

[–] [email protected] 3 points 6 months ago

Probably better to use enums instead of strings

[–] [email protected] 2 points 6 months ago* (last edited 6 months ago)

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.