If you want to be creative, and can actually stand the function prototypes, you can do this: 
sub try (&@) {
  my($code, $error_handler) = @_;
  eval {
    $code->();
  };
  $error_handler->() if $@;
}

sub catch (&) {
  return @_;
}

[download]
The & allows you to pass code blocks directly without the sub keyword. You can then write: 
my $msg;
try {
  open (FILE, "strangefilename") || die "$!";
  $msg = <FILE>;
} catch {
  print "File could not be opened because of: $@\n";
  $msg = "BAAAAH";
}

[download]
This code is from the perlsub perldoc page.

In reply to Re: Re: Style Point: Catching eval { } errors by dref
in thread Style Point: Catching eval { } errors by hardburn

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.