Hmm, I'm going to play devil's advocaat here (just for fun, you understand, and given the issue that warnings are not being captured in any helpful way)

First, with regard to strict, let's assume that you have a good development environment, where code is never altered directly in production, then the use of strict in the production environment is redundent - a script doesn't suddenly fail strict just because of input (well, not unless you're doing something very silly). If it passes strict in development, it will pass strict in production (which begs the question, why do your coworkers want it removed).

Warnings are more problematic, but, almost invariably, the only warning code of a useable quality ever generates is of the undeclared variable variety - and in almost all cases this will be caught in whatever handling you have for false - in other words, the warning is redundant and the issue handled correctly.

This is not my opinion, humble or otherwise, but it is perhaps a suggestion that the issue is not as critical as all that...

Tom Melly, tom@tomandlu.co.uk

In reply to Re: Warnings and Strict in Production/Performance by Melly
in thread Warnings and Strict in Production/Performance by deep submerge

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.