Well, the other day I was just thinking about how I keep getting bitten on code like this:
# Find all sub-dirs of $dir opendir DIR, $dir or die "yaddah:$!"; @subdirs = grep { -d } readdir(DIR);
This simple, obvious code doesn't do what I expect. The reason is that I keep forgetting to explictly do a chdir($dir): the "-d" is looking in the wrong place. So myself, I've been wondering why an "opendir" doesn't do a "chdir" for you... You can do the recursive equivalent of that task using File::Find like so:
use File::Find; find( sub { -d && print $File::Find::name, "\n"; }, $dir );
Without the implicit "chdir" behavior, you'd need to change the "-d" line to:
-d $File::Find::name && print $File::Find::name, "\n";

In reply to Re: Why does File::Find chdir? by doom
in thread Why does File::Find chdir? by jplindstrom

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.