How about just having a separate perl script for each company? It seems like the modularized approach isn't really doing all that much except managing a namespace and it adds a lot of complexity for little value that I can see. You could keep all the scripts in a single directory and just execute them all whenever you need to, via cron or via some control routine that just executes all the scripts in a given directory. Each script can contain the location to store raw and processed files.
That's not that different from your approach using 100 modules, but why use require and eval when do or system would work just as well? Ideally, there would be some reuseable bits that you could put into modules to share between these scripts so that each script is just a small wrapper to drive some common way of gathering data and some shared output functions.
-xdg
Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.
In reply to Re: Thorny design problem
by xdg
in thread Thorny design problem
by tlm
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |