Goto Statement Debate
The cluster centers on debates about the 'goto' statement in programming, questioning if it's still considered harmful, its uses in error handling and loops versus structured alternatives like break/continue, and references to historical arguments like Dijkstra's paper.
Activity Over Time
Top Contributors
Keywords
Sample Comments
Was the case against the goto statement so good we can't mention it?
Some code are more elegant to write with a goto than a loop.
That goto is considered harmful.
does this mean that goto is not always considered harmful? ;-)
Doesn’t this just boil down to “GOTO may be useful”?
Goto doesn't have a performance benefit over other control flow structures with a modern compiler.
New appreciation for the goto statement.
Good old segmentation and goto's at work! Are goto's still considered harmful?
Only wimps consider goto harmful.
Yes there's nothing wrong with goto if you need it. Of course, if you are just doing a loop, then a loop structure better communicates the intent and is safer. This is just abstraction and its a good thing. An example from functional programming is direct recursion versus maps/folds, again better to use these abstractions when possible, but direct recursion offers the most flexibility.