Why not just use a hash as a simple lookup table?
This refactored version of your script prints a tab-separated list of all the files specified as arguments on the command line. The report includes a Boolean column indicating if each file's MD5 digest matches one of the digests in the lookup table: Yes or No.
#!perl
use strict;
use warnings;
use autodie qw( open close );
use Digest::MD5;
use English qw( -no_match_vars );
use File::Glob qw( bsd_glob );
@ARGV or die "Usage: perl $PROGRAM_NAME file ...\n";
@ARGV = map { bsd_glob($ARG) } @ARGV;
local $OUTPUT_FIELD_SEPARATOR = "\t";
local $OUTPUT_RECORD_SEPARATOR = "\n";
my %md5_digests_table = map { $ARG => 1 } qw(
d41d8cd98f00b204e9800998ecf8427e
d6721344ed0cdc2e8a054a68b7ebc365
cee8eb94fd83f8d534bc44bf136ebaa0
);
for my $file (@ARGV) {
open my $fh, '<', $file;
binmode($fh);
my $md5 = Digest::MD5->new()->addfile($fh)->hexdigest();
close $fh;
my $match = exists $md5_digests_table{$md5} ? 'Yes' : 'No';
print $file, $md5, $match;
}
exit 0;
-
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.
|