OK, first of all, I am not a programmer. (yes, I heard the “thank god”) Perhaps I could make the top example simpler.
But anyway, I kind of like goto too much. I find it more intuitive to just jump around and re-use parts rather than think about how to do loops without too much nesting.
In high school, we only did Python. I really wanted to do goto in Python as well, but all I found was this April fools’ goto module.
Now in college we’re starting with C, and I am starting with Bad HabitsTM.
Anyway, tagging every line was BASICally just for the joke, but it is useful to just jump to any random line.
Functions to the rescue!
I’m glad you included the April Fool’s Day link. Comefrom is the worst thing I’ve ever seen.
That is until you’re doing something more complex, then goto becomes no-go.
Except for error handling, perhaps
Not even that. Switching code flows means potential void of state integrity. Error handling should either terminate discarded states or not interfere at all.
By the way, imagine smart pointers with goto jumps.
Got a bit too much into BASIC?
You should try assembly. Pure goto hell
It’s always fun to get your offset slightly wrong, and jump into the middle of an instruction.
