Everyone has already pointed out the advantages of dbms and databases. But if you just need to process the files once, it is probably most efficient to hash your search strings instead. Like this (untested):
# Build a hash lookup for things I want, defaulting to not there
my %found;
my @search;
foreach my $item (@timearray) {
my $id = "$NETID\|$month\/$date\/$year\|$item\|";
push @search, $id;
$found{$id} = "||$item||";
}
# Scan the file for them
my $file = "/PHL/data1/PHL/tmp/ECL_STAT";
open(ECL_STAT, "< $file") or die "Cannot read $file: $!";
while (<ECL_STAT>) {
chomp;
if (/(([^\|]+\|){3})/ and exists $found{$1}) {
$found{$1} = $_;
}
}
# Build output array
push @ECL, map $found{$_}, @search;
Now you only need to scan once, and only build in memory data structures for the actual data you are looking for.
(Which is coming in the order you are looking for it in. This code would be easier if I could assume that order didn't matter.)
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.