I'd like to suggest that you also need a
Step 0: Write a test suite that the current code passes for all normal modes of operation and for all failure modes.With this test suite, you can be reasonably certain that refactored code isn't just going to be spreading the devastation.
Given that you seem to be describing a spaghetti-coded application with communication from function to function via all kinds of secret tunnels and spooky-action-at-a-distance global variables, I'd say you have a job on your hands just with Step 0. But you've already taken a test suite into consideration... Right?
Give a man a fish: <%-{-{-{-<
In reply to Re: Perl archeology: Need help in refactoring of old Perl code that does not use strict
by AnomalousMonk
in thread Perl archeology: Need help in refactoring of old Perl code that does not use strict
by likbez
For: | Use: | ||
& | & | ||
< | < | ||
> | > | ||
[ | [ | ||
] | ] |