Programming

17373 readers

254 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]

founded 1 year ago

MODERATORS

[email protected]

-6

Real quick question about the "break" (sh.itjust.works)

submitted 11 months ago by [email protected] to c/[email protected]

65 comments fedilink hide all child comments

I'm studying programming, and I don't agree woth my teacher. She basically said that if we use break (and continue too maybe) our test is an instant fail. She's reasoning is that it makes the code harder to read, and breaks the flow of it or something. (I didn't get her yapping tbh)

I can't understand why break would do anything of the sorts. I asked around and noone agreed with the teacher. So I came here. Is there a benefit to not using breaks or continues? And if you think she's wrong, please explain why, briefly even. We do enough down talking on almost all teachers she doesn't need more online.

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

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

Thanks, it makes sense. I just don't yet see how I'd reduce the number of ifs*, but I guess it's a case by case thing.

simplest I can think of is let's say we need different logic based on a number's parity. How do I avoid if x % 2 == 0?

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

What would be an example where you need different logic based on a number's parity? Why wouldn't you write logic that ignores the number's parity?

Part of getting better as a programmer is realizing which stuff doesn't matter, and writing less code, as a result.

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

oh, okay, I hear you. Thanks

[–] [email protected] 2 points 11 months ago

Good luck