To be clear, all the code works well in that it does everything it is supposed to do consistently and within an acceptable time ... I do have test environments so I would not have to break the code whilst it is in production!

What is the current state of your code?

The ideal is to gradually improve your code, one module at a time, always keeping a working system. Typically you would add use strict only when you need to change a module anyway and so need to retest it.

Re when/if to rewrite working legacy code, I keep a long list of previous PM discussions on that tricky topic at: Re: Strategies for maintenance of horrible code? (Legacy Code References)


In reply to Re: Backdating strict by eyepopslikeamosquito
in thread Backdating strict by Bod

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.