You can use eval to catch, and then do alternate tasks:

use warnings; use strict; my $ok = eval { blah() or die "damn thing failed!"; 1; }; if ($ok){ print "success\n"; } else { print "failed, doing something else\n"; } sub blah { # simulate a fail return 0; }

Now, the error will be in $@, but because there are situations where it can be reset before you get to it, it can be risky to do things like this:

eval { blah() or die "failed"; }; if ($@){ ... }

Regarding my first full example above, if an exception is thrown within the eval, it'll set $ok to undef, otherwise if all of the statements execute successfully, the 1 (ie. true) will be returned.

Inside of the else block, you could check to see what the error is:

if ($@ =~ /timeout/){ ... }

...but again, it's not wise to solely rely on that variable in all cases.


In reply to Re: Error handling by stevieb
in thread Error handling by snehit.ar

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.