🚀 go-pugleaf

Why should anyone want to eliminate goto ?
And why by a mechanism that is even less clear than goto.
Must we extend a language just to make it "politically correct" ??

If you cannot avoid goto's :: dont avoid them.
If you can only avoid goto's by obscure constructs or
flag-spagetty :: just stick with the goto's ; they provide
more clearity in such cases. 
Note that most (human) readers are better at finding out
the flow of control of a progam than at understanding the flow of
data/status/flags/indicators. The intention of the writer should be
just to make it lean and clear: just by keeping the number of "names
in scope" (including labels and unnamed loops) low. If I can reduce the
number of bracepairs, or sourcelines, can avoid repeating the same
expressions/statements/function-calls/etc ,or can avoid to fiddle with
some loop-conditions, I feel no shame to use a goto.

BTW I'm not religious.
Adriaan van Kessel.