It's surprisingly mellow thrash-wise, actually. I just do
#SETUP DELETED, CODE WON'T RUN
my @file1 = <FILE1>;
my @file2 = <FILE2>;
my $lc = List::Compare->new(\@file1, \@file2);
my @file1only = $lc->get_Lonly;
my @file2only = $lc->get_Ronly;
print OUT "Files that exist only in FILE1:\n";
print OUT "IGNORING FILES WITH Tmp OR Temp IN PATHNAME!!!\n\n";
foreach my $file1(@file1only) {
unless (($file1 =~ "Tmp") or ($file1=~"Temp")) {
print OUT $file1;
}
}
print OUT "\n\n";
print OUT "Files that exist only in FILE2:\n";
print OUT "IGNORING FILES WITH Tmp OR Temp IN PATHNAME!!!\n\n";
foreach my $file2(@file2only) {
unless (($file2 =~ "Tmp") or ($file2=~"Temp")) {
print OUT $file2;
}
}
and it takes less than a minute to run on my box here at work.
Unfortunately, we're an all-Windows shop. I've managed to infiltrate a couple of FreeBSD boxes into the test department (cool network tools and a neato disk imaging system called Frisbee), but it's hardly worth moving all of the files over there and back just to save a few seconds using "sort" instead of List::Compare.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|