note Eliya <blockquote> <i> Lumping strict and warnings together is a mistake. </i> </blockquote> <p> I beg to disagree.&nbsp; Many times (not only here, but at my workplace, too) I've seen people hunting for bugs for way too long, simply because they thought "<b>I</b> don't need no stinking warnings".&nbsp; Had they had them enabled, they would have been pointed to the root cause of the problem more or less directly. &nbsp; And if you feel annoyed by the "use of uninitialized value"s (and you know what you're doing), it's no big deal to disable those specifically with <c>no warnings "uninitialized";</c> &#8212; at least that doesn't qualify as "a lot of work" in my opinion. </p> <p> I agree there are rare circumstances where you don't want them &#8212; for example, I've seen a few cases (very few actually) where leaving warnings enabled in production environments has led to more problems than it solved &#8212; but as a development tool, I'd always recommend <c>use warnings;</c> </p> 952446 952529