Thank you. However, if you're looking for great code, be warned that the above code used a lot of globals (well, lexicals whose scope covers the entire file). If later on I wanted to reword this into a proper module, those might cause me problems. Fortunately, they're always "read only" in the code and that minimizes things but global variables are still a good thing to avoid, if feasible.
Also, my read_config was actually put in there so a project manager could easily use this code. In reality, there are better ways of getting the "old" and "new" data into the program. I really should turn this into an OO module and make those values that you can set in methods.
Cheers,
Ovid
New address of my CGI Course.
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.