I'd rewrite it using Test-Driven Development methods. Write the test, have it fail, then write the code that makes that test pass. Lather, rinse, repeat. There are a number of nodes regarding TDD on Perlmonks and other venues. It makes things very simple for a newer developer because you're focusing on results, not methods. Also, if you ever want to change something, you have a test-suite that describes what this thing is supposed to do. :-)
------
We are the carpenters and bricklayers of the Information Age.
The idea is a little like C++ templates, except not quite so brain-meltingly complicated. -- TheDamian, Exegesis 6
Please remember that I'm crufty and crochety. All opinions are purely mine and all code is untested, unless otherwise specified.
In reply to Re: Re: Opinions on migrating Perl scripts from 5.005 to 5.8.1?
by dragonchild
in thread Opinions on migrating Perl scripts from 5.005 to 5.8.1?
by Lori713
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |