The only reason to prevent something dying is where its maintenance is, at least temporarily, beyond your control. So IMO best practice is, yes, patch around it with one of the techniques already mentioned, but I'd avoid too routine a habit of patch and forget - be sure to have bug-reporting/follow-up built in to your dev cycle.

In regard to warnings, they should be corrected. If a CPAN module produces a warning and it is a result of giving it duff parameters, I'd be inclined to force it to die and fix the root cause in my code. 'use strictures 2;' is a shorthand for the following:- 

use strict;
use warnings FATAL => 'all';
use warnings NONFATAL => qw(
  exec
  recursion
  internal
  malloc
  newline
  experimental
  deprecated
  portable
);

[download]
which is not necessarily the best match for either your code or a given CPAN module. So it is worth maintaining a site policy on these settings.

Finally, if you are convinced a warning is wrong, best post it here for discussion.

In reply to Re: Best practices for handling exceptions in die/eval style by TheloniusMonk
in thread Best practices for handling exceptions in die/eval style by krautcat

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.