I know you're working on a deadline (and I'll go in to that later) but that would be the wrong way around. The absolutely very first thing I recommend when inheriting bad code (and we have all had to do it) is getting the source to compile under use strict;.

As for the deadline (arbitrariness aside) getting code running under use strict; will take less time than you think. Really it will, no matter how bad the code is. Most importantly, it almost assuredly save you time (short term and long term).

1. The obvious reason: You will have better code to read and debug.
2. The not so obvious reason which will save you the most time: You will find the little tiny bugs that no one ever thinks to look for right away - instead of days, weeks, ... later when it takes you most of a day to find that one last irritating bug that everyone is getting bent out of shape about.

Seriously, it sounds like waste of time, but it isn't.
You may think, 'This code is worse than anyone has seen, so adding use strict will take longer than anyone can understand.' but trust me I have seen worse code and using strict is more important and saves more time, the worse the code is.



grep
One dead unjugged rabbit fish later

In reply to Re^3: deleteing array elements I get mad!! by grep
in thread deleteing array elements I get mad!! by kurreburre

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.