It sounds like you have a pretty good idea. If all your scripts follow the same format, and the only differences are config (which server to connect to, which files to process, which database tables to insert into), and the single process_line() function, it sounds like you've got a need for making a parent class, which of course sets up the db/ftp/connections and whatnot (possibly from command line options or config files), and does most of the rest of the work. Each of your children modules will simply inherit from the base class and define a process_line() function. So that will be the only difference, module-to-module.
It doesn't even sound like you have a need for separate scripts, you can simply have one script which also takes an argument for which child script it will activate, like:
my_script.pl --type=WSB
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.