It is also an example where consistent indentation would have helped to spot the problem, as well as wider indentation of 4 spaces instead of 2 and comments:
sub getdir
{
    my $dir = shift;

    # Open the directory handle, reporting the reason ($!)
    opendir (my $dh, $dir) || die qq(Cannot opendir: $dir: $!);
    
    while( my $file = readdir($dh)) { 
        next if ($file =~ m[^\.{1,2}$]);   # Ignore . and ..
        my $path = $dir .'/'. $file;
        if (-e $path) {
            # do some stuff
        }
        elsif (-d $path) {
            getdir($path);
        }

        closedir ($dh);    # Close the directory handle - OOPS
    }
}

[download]

In reply to Re^2: Bad file descriptor error by cdarke
in thread Bad file descriptor error by Lamont85

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.