I was testing that out and I realized something. It only gives you the exact line number of the error if you are using eval BLOCK, it gives much different (but still very useful) warnings if you are using eval EXPR 
use Carp ();
$SIG{__WARN__} = \&Carp::cluck;
eval {
    use warnings;
    undef =~ m#1#;
};
$string = q{
    use warnings;
    undef =~ m#1#;
};
eval $string;

__OUTPUT__
Use of uninitialized value in pattern match (m//) at temp.pl line 5.
        eval {...} called at temp.pl line 3
Use of uninitialized value in pattern match (m//) at (eval 1) line 3.
        eval '
    use warnings;
    undef =~ m#1#;

;' called at temp.pl line 11

[download]
That is a very handy thing to remember.

--

flounder

In reply to Re^2: warnings within eval{} by flounder99
in thread warnings within eval{} by shemp

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.