I also find this far, far from beautiful. It reminds me of the awful error handling in Visual Basic.

I think goto is a useful construct, but an error handler built on control reaching a label from multiple places, then reacting to a couple of globals (you've got them as globals) is a recipe for disaster. Imagine yourself staring at the output of your show_error_page routine, and realizing that the error_code and error_msg don't match. Now you have another problem: who clobbered them? An error handler whose context information can be changed from different places is too unreliable to be useful.

If all you're looking for is an error handling technique that can receive some state information and not return to the calling context, exceptions are a much better answer, as others have pointed out above.

In reply to Re: goto with some arguments by VSarkiss
in thread goto with some arguments by Anonymous Monk

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.