Well that all depends -- how often has it been run in the past 5 months? In how many different scenarios? Why is the poster looking at it again after this much time? Are there changes that need to be made? Is it going into heavier use?

I say again, if the developer didn't expect to see warnings then they are a sign that the developer overlooked something. I don't care if it has been running right for the past 5 months; code that spews warnings when I don't expect it to makes me worry.

Hmm, I wonder what I will see if I put in use strict... <tappity tap> Yikes! Where are all these warnings coming from?! <thinks> Oh well, if I remove the use strict they go away. <tappity tap... slams head into hole in sand.>

In reply to Re: Re: Use strict _encouraged_, but not mandated :-) by Sifmole
in thread Use Strict needed? by Anonymous Monk

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.