Just adding
use strict;
use warnings;
isn't really going to help all that much until you can look into the code and see what is going on. THe book you have been recomended will help. But in the long run, it is going to be a long hard slog.
Depending on how much is hard coded by way of file names and so on, you may want to consider adding a configuration file using something like Config::Simple. In fact I would try that before I even try to move off the BSD machine.
As for the future? Well maybe tests wouldbe a good idea. But also a move to a more robust module or OO based coding paradigm with better documentation and re-usability would be nice! But in the end? Well I am sure you can read all the sage advice on the monsatery without asking too much!
jdtoronto
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.