First of all, you should use strict; and use warnings;.

On your first attempt, you do something like this:

$timestamp = POSIX::strftime("%m/%d/%Y %I:%M %p", localtime(( stat $fi
+les)[9])); # or change localtime to gmtime
$size = (stat $files)[7];

[download]

You run stat twice, forcing the operating system to grab the same data twice. Why?

Something like this should do the trick in less time:

# Get both pieces of information we need
my ($size, $timestamp) =  ((stat $files)[7, 9]);
# Convert timestamp
$timestamp = POSIX::strftime("%m/%d/%Y %I:%M %p", localtime($timestamp
+);

[download]

Don't use '#ff0000':
use Acme::AutoColor; my $redcolor = RED();
All colors subject to change without notice.

In reply to Re: sizeDateValidator.pl is horribly slow by cavac
in thread sizeDateValidator.pl is horribly slow by msensay

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.