Written earlier, emphasis added ...

... Error::Simple subclasses (Error objects henceforth) ...

... as in ... 

#  In ModErr.pm ...

package ModErr;

use base 'Error::Simple';

1;


# Elsewhere ...

use ModErr qw[ :try ];

try
{
  1 == int( rand(2) )
  ? call_me()
  : wont_you_call()
  ;
}
catch ModErr with
{
  my ( $err ) = @_;

  my $text = $err->text;
  throw ModErr "No call back."
    unless $text =~ /your call/i;
};

print "Everything is ok after all!\n";

sub call_me
{
  throw ModErr "Here is your call!";
}

sub wont_you_call
{
  throw ModErr 'please?';
}

[download]

In reply to Re^2: Error::Simple or eval{} use to capture &Carp::croak by Anonymous Monk
in thread Error::Simple or eval{} use to capture &Carp::croak 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.