The arguments in that essay are a poor rendition of the arguments that Knuth gave in Structured Programming with Go To Statements. However if you read that essay carefully you will realize that modern exception handling is better for handling errors than goto, and the remaining efficiency points are all addressed completely by labeled loop control. (In fact Knuth refers to a paper proving the second point, however at the time that point was theoretical only since no languages had that feature back then. However Perl does.)

That is not to say that there are not cases where goto is still useful. But they are very rare. I can only think of 3 that I have ever seen in Perl, and none of them were in code that I wrote.

In reply to Re^2: GOTO or not GOTO by tilly
in thread GOTO or not GOTO by jflevi

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.