I would have written that like this, keeping (and clarifying in the "Usage" message) the intention to allow multiple files to be done in one run. (Note -- on unix/linux/macosx for sure, don't know about "cmd.exe" -- when your command line is
prog_name *.txt or whatever, the shell does file name expansion, replacing "*.txt" with the list of all matching file names, before invoking the script, so @ARGV has that many elements in it.)
#!/usr/bin/perl
use strict;
use String::CRC32;
my $Usage = "Usage: $0 file.name ...\n";
@ARGV or die $Usage;
for my $file ( @ARGV ) {
open( my $fh, "<", $file ) or die "Unable to open $file: $!\n";
my $crc = crc32( $fh );
close $fh;
printf( "%08x ( %08x ) %s\n", $crc, 0xffffffff - $crc, $file );
}
I don't understand the relevance of 0xffffffff - $crc, but if it's useful at all, it helps to have fixed-width fields to the left of variable-width fields.
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.