News for hackers. Stuff that matters.
Re:The History, Controversy, and Evolution of the Goto State... by goto11 on Tuesday November 20, 2018 @02:14AM (#18492306)
From "Goto considered harmful": The exercice to translate an arbitrary flow diagram more or less mechanically into a jumpless one, however is not recommended.

Djikstras problem with GOTO was that the source code structure does not correspond to the execution path. GOTO turns the execution into a state machine rather than a nice tree. Avoiding GOTO by implementing a state machine with flags is just creating the same problem one level up.

The problem with GOTO is not the keyword itself, it is what it does to the code.

There are no comments on this comment yet.