Programming

17651 readers

365 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 2 years ago

MODERATORS

[email protected]

-5

Real quick question about the "break" (self.programming)

submitted 1 year ago by UnRelatedBurner to c/[email protected]

64 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

[–] litchralee 8 points 1 year ago (1 children)

There will always be some instructors that are more dogmatic than pragmatic. All the same, there will be instructors that have pearls of wisdom to offer. Regarding the "break" and "continue" keywords, this lays somewhere in the middle.

One of the purposes of higher-level programming language is to remove from the low-level, machine-specific language of assembly, by offering other, more descriptive constructs, like "while", "for", and "switch". In the C language, "break" is almost mandatory in a "switch" statement but only occasionally shows up in a "for" loop, excepting drivers. In Python, "break" only exists in loops, but there are lots of loops which can be replaced more efficiently with comprehensions, so "break" can be a sign of poorly organized logic.

If you can specify which programming language you're learning, it would help to understand what your instructor might have meant to teach.

[–] UnRelatedBurner 1 points 1 year ago

This rule will apply for C# only I think (I hope). I also like your optimistic points, thanks.