this post was submitted on 08 Dec 2023
618 points (96.4% liked)
Programmer Humor
36876 readers
152 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Please don't use #2. It is how you get the goto fail bug
But I really need to go.
Then use golang
Should you even be using goto? I was taught to avoid it like the plague
Apple wrote bugged TLS code that broke using unbraced ifs with a goto, hence the name "goto fail". You don't need a goto to break this code though. All you need is a second indented line under the
ifCan you explain? 1 and 2 seem like the same logic? Are they compiled differently?
To me number 2 is just the cleanest and most easy to read. But I really need to get more used to lambda's
#2 is also the most insideous to update. Add another indented line to one of the conditions and the cotrol flow completely breaks while visually appearing fine.
C and a number of other languages have annoying pair of parallel syntax systems that makes it easy for people to read code one way and computers to compile it another. People read the indentation and newlines while compilers count braces and semicolons. #2 gets rid of the braces and makes control flow driven by semicolons making human visual inspection more likely to fail
Thanks for the reply (not really sure why someone would downvote you for answering a question).
10 goto 20
20 goto 10