In fact, after reading eyepopslikeamosquito’s response I'm reminded of this kind of approach. It’s not very hard, it can DWIW a little with overload, and it can be very useful/robust compared to matching for content against error strings–

use 5.014; # Safer eval+$@ handling.
use strictures;
package HURR_DERR_ERR {
    use Moo;
    use Devel::StackTrace;
    use overload '""' => sub { +shift->as_string };
    has code =>
        is => "ro",
        default => sub { "[uncoded]" };
    has message =>
        is => "ro",
        required => 1;
    has stacktrace =>
        is => "ro",
        default => sub { Devel::StackTrace->new->as_string };
    sub as_string {
        my $self = shift;
        join ": ", $self->code, $self->message;
    }
};

for ( 1 .. 100 )
{
    eval {
        die HURR_DERR_ERR->new( message => "Unlucky number encountered
+: $_" )
            if /\b4\b/; # You'll have to localize if you don't want Ch
+inese values.
    };

    if ( $@ )
    {
        # If you want it -> say $@->stacktrace;
        die "Got an error -> $@";
    }
    else
    {
        say;
    }
}

[download]
1
2
3
Got an error -> [uncoded]: Unlucky number encountered: 4 at example.pl
+ line 33.

[download]

Update: changed “script name” in error output. Update #2: changed version per suggestion.

In reply to Re: Best practices for handling errors by Your Mother
in thread Best practices for handling errors by v_melnik

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.