Most of your points are accurate.

But (you knew that was coming) the exact question which started this dicussion was you recommending the use of $Carp::CarpLevel for wrapping a module. Which is exactly what you said that you don't do.

Despite your assertion that you don't hardcode $Carp::CarpLevel, your example did. If you want to let your caller be more flexible in what they are going to do, you need to: 

{
  local $Carp::CarpLevel = $Carp::CarpLevel + 2;
  carp("That isn't nice!");
}

[download]
If you do that, then someone calling your code can decide to edit themselves out of the calling stack. Else they can't.

Further than that, I note that while it may be possible to figure out the call-level that an error will be called from, that imposes extremely strong requirements on the structure of the code. And even where you had that structure once, it generally doesn't last. (It didn't for Exporter.)

As for longer term solutions, please download the current development series and take a look at what is offered in its Carp. If that doesn't offer the control that you want, now is the time to raise your voice...

In reply to Re (tilly) 6: Confusion about properly using Carp by tilly
in thread Confusion about properly using Carp by jeffa

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.