Programmer Humor

37235 readers

30 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

Posts must be relevant to programming, programmers, or computer science.
No NSFW content.
Jokes must be in good taste. No hate speech, bigotry, etc.

founded 5 years ago

MODERATORS

cat_programmer@lemmy.ml

457

Infallible Code (europe.pub)

submitted 2 days ago by sirico@feddit.uk to c/programmerhumor@lemmy.ml

160 comments fedilink hide all child comments

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

[–] Croquette@sh.itjust.works 6 points 2 days ago (1 children)

I am working with C in embedded designs and I still use 1 or 0 for a bool certain situations, mostly lines level.

For whatever pea-brained reason, it feels yucky to me to set a gpio to true/false instead of a 1/0.

[–] xthexder@l.sw0.com 6 points 2 days ago* (last edited 2 days ago) (1 children)

GPIOs are usually controlled by a single bit of a register anyway. Most likely you need to do something like:

// Set high
PORTB |= 1 << PINB5;
// Set low
PORTB &= ~(1 << PINB5);

[–] Croquette@sh.itjust.works 2 points 2 days ago (1 children)

I am a lazy dev (not really, clients always want fast code), so I use the provided HAL libraries 99.9% of the time.

But I have seen code where someone would write something like

gpio_write(PIN_X, true)

and it always stood out to me.

[–] JackbyDev@programming.dev 1 points 1 day ago (1 children)

Define on as true or something? Or maybe that's more confusing. I'm not a C dev so I'm not gonna pretend to understand idiomatic microcontroller code lol.

[–] Croquette@sh.itjust.works 1 points 1 day ago

Sometimes, people do that. But using 0/1 is explicit enough since you can refer to a line as '1' or '0' for high/low on the hardware as well