104
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 19 May 2024
104 points (97.3% liked)
Programming
17314 readers
8 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
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 !webdev@programming.dev
founded 1 year ago
MODERATORS
Languages don't have goto because they mindlessly copied it.
True it wasn't mindless - just idiotic
It's not idiotic. You can do a lot of performance optimizations with GOTO so providing it as a "use it if you know what you're doing" option is fine. And some things are easier to read with GOTO.
FWIW the Linux source code is full of GOTO statements. Nearly 200,000 of them in fact.
There's a solid reason for goto in C.
Bringing goto into Java was (and is) idiotic.
If you're trying to squeeze every ounce of performance out of your code then you'll need those optimizations.
But any higher level language than C the entire point is to write easily maintainable and useful code that any idiot can go, read and update. A goto is antithetical to readability.
It can be, sure. But when used in a limited manner where it makes sense it can be the more readable option. I've used it in a try/catch to retry the operation after changing a variable. One label ("reconnect"), one goto, totally easy to understand on a surface level.