Hi Grygonos,

While it "gets the job done", a couple things jumped out at me that I felt were important enought to comment on.

First of all, the big one: foreach (2..$#entries) Try running this on the root of your C drive, which doesn't have the "." and ".." entries. You'll miss the first two directories. 

opendir DIR, 'c:/';
print join "\n", (readdir(DIR))[0,1];
__END__
output on my system:
2dvtllhn.sys
ADOBEAPP

[download]
Also, it seems that . and .. are always listed first in the directory, but I've never seen it documented. I certainly wouldn't depend on it.

Second, using the -d test instead of if(opendir(TEST,$item)) to test for a directory would be more efficient as well as more readable.

In reply to Re^2: Reading directory structure? by bmann
in thread Reading directory structure? by Seventh

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.