-7
Real quick question about the "break"
(sh.itjust.works)
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 !webdev@programming.dev
Okay, I want to clarify two different but highly similar syntaxes:
break;
andbreak 3;
. The latter syntax of break #number is fucking awful and you should never use it. In most languages it'll only count loops and not conditionals so it can be extremely hard to tell how many levels of indentation you're unrolling and it's probably a code smell about having an overly complex function anyway.However, good old single level break and continue are awesome and useful for making it really clear what preconditions exist in complex situations when looping. It's much easier to read a series of elementary if break statements than one single gigantic if statement with half a dozen conditions.
Most tools in our toolbox are useful... oh, except goto (unless you're programming in assembly language). Fuck goto.
haha I personally like both gotos and multi layered breaks, I know it's bad practice, and I avoid them, but it's fun.
That aside, you summed up what we are thinking pretty accurately.