Hi Monks,
Please do the following:
1. Download Devel::Trace and install it.
2. Take the code below into a file.
print "line 1\n"; # line 2bug print "line 3\n"; print "line 4\n";
3. Execute "perl -d:Trace your_file.pl"

See that after the line "# line 2bug" the file name found by caller() in Trace.pm is the "bug" string.
>> /usr/local/aig/common/db/Development/scripts/pf/script1.pf:1: print + "line 1\n"; line 1 >> bug:2: print "line 3\n"; line 3 >> bug:3: print "line 4\n"; line 4

Who did this job ???
Perl5-porters wherever you are - can you explain ?
I there a solution (that not mean "do not write such lines...")

TIA,
shushu

update (broquaint): title change (was A F***ing bug in caller())


In reply to A bug in caller() with Devel::Trace? by shushu

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.