The point about the -M, -A and -C args being "in days" is that these are float values, not integers. You might want your printf format to use something like "%7.2f" rather than "%5d" for these values.

If you read "perldoc -f -X", you'll notice that you can save a few ops by using underscore "_" when doing a second (third, ...) look-up of a stat value on the same file: 

  printf ("%12s %7.2f %7.2f %7.2f\n", $loglfile, -M $logfile, -A _, -C
+ _);

[download]

Also, the idea of using glob is very good (avoids the need to worry about newlines at the ends of the file names); the idea about using File::Find is probably not worth the trouble.

(updated code snippet to use "%7.2f", as per my own suggestion)

In reply to Re: Perl File-Test Operators by graff
in thread Perl File-Test Operators by gyasuda

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.