Thanks for touching the subject of using
strict.pm and especially it's superb ability to fix majority of the bugs in a legacy code (that which wasn't running on strict before) without having to resort to rather involved practices such as
Refactoring, for example.
Of course, there are many other issues involved in 'revisiting old code'. Aside from having to refactor bits and pieces of an old code in order to resurrect it from near-extinction, one also has to tackle conflicting coding styles. It's half the trouble if the styles are just that 'conflicting'. Unfortunately, there's a lot of coding styles that are precursors to greater problems in the code. I believe some of these issues were touched in
On maintaining old code and the battle of styles... post I mead a couple weeks ago.
Romping around the monastery, you should also notice a great many posts where similar subjects are discussed:
UPDATE fixed a few spelling errors ;)
_____________________
$"=q;grep;;$,=q"grep";for(`find . -name ".saves*~"`){s;$/;;;/(.*-(\d+)
+-.*)$/;$_=["ps -e -o pid | "," $2 | "," -v "," "]`@$_`?{print"
++ $1"}:{print"- $1"}&&`rm $1`;print"\n";}