r.biswas:
I'd suggest writing a subroutine to read all your configurations into an array, and then when processing the input file you can simply load the current configuration. Something like:
my @configurations;
load_configurations("config_file");
open my $FH, '<', $input_fname or die "Can't open $input_fname: $!";
while (<$FH>) {
my @config_vars;
... parse out an input entry ...
@config_vars = @$configurations[$configuration_ID];
... code to process input using configuration variables...
}
sub load_configurations {
my $fname = shift;
open my $FH, '<', $fname or die "Can't open $fname: $!";
while (<$FH>) {
my @config_vars;
... parse out a configuration...
$configurations[$configuration_ID] = [ @config_vars ];
}
}
This way, you have all the configurations at your fingertips, and you can process each input entry with a different configuration, if desired.
...roboticus
When your only tool is a hammer, all problems look like your thumb.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Outside of code tags, you may need to use entities for some characters:
| |
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.
|
|