Can you at least share a code snippet so we have any idea about what we are looking into?
Your teacher is wrong here, at least from what I'm getting the vibe. Those two keywords don't make the program unreadable, they're there to serve a purpose.
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 wormhole through a path of communities [email protected]
Can you at least share a code snippet so we have any idea about what we are looking into?
Your teacher is wrong here, at least from what I'm getting the vibe. Those two keywords don't make the program unreadable, they're there to serve a purpose.
there is no code snippet, it's in general. break = fail. Maybe there are some cases where this isn't true, but I have very little experience with this so far.
Ignore it (edit: obviously not for the purposes of the course, which someone helpfully jumped down my throat presuming). A lot of people somehow in charge of teaching coding couldn't code their way out of a wet paper bag.
They are in a ton of languages in all kinds of different families for a reason: they are a logical and fairly consistent expression of two fairly consistently logical ways to deal with control flow in the specific case of a loop. Also there's the switch-case case in C-style languages.
Now, there are legitimate arguments for avoiding tons of of exotic control flow shenanigans, but if someone doesn't understand break/continue, then the problem is 100% theirs and nobody should take their advice on anything much, let alone relating to programming.