My first thought when looking at this is that you seem to be mixing "errors" and "warnings". To me, an error is something that generally needs to be handled right away (I.E. anything that dies).

If you can really avoid handling these errors until object destruction, and even then you are OK "gently proding" developers into handling them by just printing the "error" as a warning of sorts (via carp), are they really errors at all? If they really must be handled, I would lean towards a more heavy handed approach. It's hard to ignore a die/croak/confess, but all too easy to ignore a warn/carp/cluck.

In reply to Re: Carping about object destruction when errors are unprocessed? by duckyd
in thread Carping about object destruction when errors are unprocessed? by radiantmatrix

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.