Re^2: migrate perl program

thanks for your responses, but my scripts are simple, long but simple, a lot a scripts for transfer FTP. The modules which frighten me, are perl-Net-SSLeay-1.30-4.EL3, perl-Crypt-SSLeay-0.51-4, perl-DBI-1.32-9. I don't use strict/warnings in my scripts. I've been reassured by your analyses, I am going to launch the first tests. i've got a feetback.

Comment on Re^2: migrate perl program

Replies are listed 'Best First'.
Re^3: migrate perl program by GrandFather (Saint) on Dec 02, 2014 at 20:26 UTC
So a really good first step would be to add strictures to your code before you port it and clean up any issues raised on the old system. If possible it would also be smart to add some regression tests so you can have some confidence behavior hasn't changed in important places during the migration. Also run through checking that system calls are checked for errors and handled correctly - if you are moving to a new system filed and directories may have moved around in surprising ways and file operations may begin failing as a result. Perl is the programming world's equivalent of English	[reply]

Replies are listed 'Best First'.

Re^3: migrate perl program
by GrandFather (Saint) on Dec 02, 2014 at 20:26 UTC

So a really good first step would be to add strictures to your code before you port it and clean up any issues raised on the old system. If possible it would also be smart to add some regression tests so you can have some confidence behavior hasn't changed in important places during the migration. Also run through checking that system calls are checked for errors and handled correctly - if you are moving to a new system filed and directories may have moved around in surprising ways and file operations may begin failing as a result.

Perl is the programming world's equivalent of English

[reply]