in reply to migrate perl program
Try to put together a list of Perl modules in use, this would help greatly in understanding what kind of problems you might run into.
You could try to collect some data on this automatically, for example by using grep. My grep-fu isn't very strong but it should atleast help you get started:
grep -r "^use [0-9a-zA-Z\:]*;" /home/*Also, I've found that well-written perl code usually survives longer. No "use strict/use warnings"? Lots of global variables? No SQL placeholders? Manual extraction of form parameters as opposed to using the CGI module? These are usually signs that the migration is going to take a while. Not necessarily because more things break, but because poorly written code can be notoriously hard to troubleshoot and you end up having to rewrite a lot of code that deserved to die.
I know this all too well, because I've just spent two days migrating my own private web server with scripts dating back to last century. It was even worse than I feared :-P
Time flies when you don't know what you're doing
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^2: migrate perl program
by gehu (Initiate) on Dec 02, 2014 at 17:08 UTC | |
by GrandFather (Saint) on Dec 02, 2014 at 20:26 UTC |