🚀 go-pugleaf

John Noland (sinan@cyberramp.net) wrote:

[snip]
:  DON'T use a goto unless it's the only solution to the problem.
:  You have many alternatives to a goto in your above code. 

Wrong.  'goto' will never be the only solution.  When the 'goto'
solution is more elegant than the other choices (which is entirely
possible), use 'goto'.

:  A subroutine should have at most one label.

Arbitrary number.  Does a subroutine with exactly *two* labels
automatically and magically become unreadable?

:  All goto's should be above that label in the code.

Above?  You mean all 'goto's should be forward jumps?  Why?

:  The label should be in the same code block or at a more outer
:  nesting level than the goto itself.

: Your code could be easily reorganized to not use a goto.

That's the point against using 'goto's.  Realize however that a
good engineer is usually smarter than blind guidelines.  The
rules you raised have obvious drawbacks.  Personally, the rule
I impose upon myself is: "If you use a 'goto', you better have
a damn good reason for it and be prepared to explain why all
other constructs make the program uglier."