You can parse the files in the directory with a structure like this, instead of using opendir/readdir/closedir:
my @files = ();
foreach (<*$count*>) {
    s/\.[^.]*$//;
    push @files, $_;
}

[download]

Not sure what you needed to do with the files, but you might do that inside the loop as well. I'm not sure exactly how <*> works internally, but it's definitly better than doing a system() call that relies on ls, awk, and grep (even if those are fine tools). I find it cool, yet strangely disturbing, that you can interpolate the variable $count into the <...> directory listing.

-Ted

In reply to Don't use opendir by tedv
in thread thanks, i'm new. rtfm right? :) by derrickm

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.