From your code: 
    # (by the way, i _do_ hate having to see
    # that 'sub' word right after try...
    # since there's no other way to
    # pass a block of code as an argument other than
    # via the anonymous sub/closure)
    #
    # try sub {
    #     foo();
    # };

[download]

You can use prototypes to enable passing sub-refs without the 'sub' keyword. See, for example, the perlsub manpage, and/or some of the other exception handling modules:Exception::Class, Error, and the older Exception for variations on try{}catch{} examples (actually, Exception::Class doesn't implement try/catch directly but you can use it in conjunction with Error.pm (according to the docs) to get that syntax with it). The (&) prototype is one of the few useful uses of prototypes (in certain circumstances).

In reply to Re: Exception handling (alternatives) by danger
in thread Exception handling (alternatives) by vladb

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.