You should use warnings; use strict; at the top of all your scripts, and you should check the return values of functions for errors (in this case opendir). Here's a version incorporating that and a bit of cleanup:

#!/usr/bin/env perl
use warnings;
use strict;
use IPC::System::Simple qw/system/; # recommended but optional

opendir my $dh, "." or die "opendir failed: $!";
my @files = grep {/\.dbf$/} readdir $dh;
closedir $dh;

foreach my $file (@files) {
    system(qq{dbf_dump --fs "," "$file" > $_.csv})==0
        or die "system() failed (\$?=$?)";
}

[download]

Note the error handling code on system isn't really needed if you use IPC::System::Simple.

In reply to Re: dbf_dump to apply to multiple files in a directory by Anonymous Monk
in thread dbf_dump to apply to multiple files in a directory by solanum

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.