For the sake of defensive programming, and to be cross platform compatible, you could also use File::Spec::Functions to be safe.

File::Spec::Functions has two routines that will return the characters used to represent the current and upper directory for your specific operating system. While it may be true that most OS's use "." and ".." to represent the current directory and upper directory, it may not necessarily be garaunteed. If it was, I doubt these functions would have been put into the module in the first place. =)

Here's your example using File::Spec::Functions:

use File::Spec::Functions qw(curdir updir); #.. next if $file eq curdir or $file eq updir;

In reply to (dkubb) Re: (4) recurse directories and sub-directories (bad code warning) by dkubb
in thread recurse directories and sub-directories by Anonymous Monk

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.