Read the commit message for some info.

Okay, read that, and it helped, but I can't say that I understood it all. DB is the debugger package, right? So I guess CORE::caller is setting up ... something ... that helps the debugger do ... something ... and folks who override CORE::GLOBAL::caller have to do the same thing or chaos will ensue? Am I getting that right? :-)

That's because code was added to 5.14 to identify where the bad code is located ($where).

Yeah, I saw that, but, in my case, $where was blank anyway, so I didn't see any point in including that code in retrospect. ;->

In reply to Re^2: Trying to understand (caller($i))[4], a.k.a. $hasargs [diagnostic] by Oberon
in thread Trying to understand (caller($i))[4], a.k.a. $hasargs by Oberon

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.