The problem that
aaron_baugher pointed out is the main thing, but once you get past that, the script will take somewhat longer to run than it needs to, because you're calling the "stat" function multiple times on each file. I'd do it like this (not tested):
use strict;
use warnings;
use POSIX;
use File::Spec;
my $inputFile = "inputFileInfo.txt";
my $outputFile = strftime( "resultsFile_%Y-%m-%d_%H-%M-%S.txt", localt
+ime(time()));
my $pathToCheck = File::Spec->catfile( 'c:', 'temp' );
open( IN, '<', $inputFile ) or die "$inputFile: $!\n";
open( OUT, '>', $outputFile ) or die "$outputFile: $!\n";
while ( <IN> ) {
chomp;
my $checkFile = File::Spec->catfile( $pathToCheck, $_ );
my @stats = stat $checkFile;
if ( @stats ) {
printf OUT ( "%s: %d, %s\n", $checkFile, $stats[7],
scalar( localtime( $stats[9] )));
}
else {
print OUT "$checkFile: stat failed (file not readable or not f
+ound)\n";
}
}
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.