It would seem best to put all your 'data_gathering' processes in one module. There has to be a lot of commonality in the code for each company.
In the module you might have the following subs.
Now you need to tell the module which process combination to use. For this you could use a hash, outside the module, that defines the process for each company. That way you don't need to mess with the module when you add a new company provided, of course, that the required sub exists in the module.
use Crunch; %process = ( 'WalMart' => 'A:A:A', 'ExxonMobil' => 'B:D:A', ... 'CiscoSystemsInc' => 'C:D:A', ); sub do_em { my $path_to_companies = shift; opendir $dh, $path_to_companies or die "Can't opendir $path_to_compa +nies: $!\n"; while ( my $company = readdir( $dh ) ) { next if $company ~= /^\./; my $dir = catdir( $path_to_companies, $company ); next unless -d $dir; Crunch::do_it( dir => $dir company => $company process => $process{$company); ); } }
In reply to Re: Thorny design problem
by nedals
in thread Thorny design problem
by tlm
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |