Hello fellow monks,
I am working on a little module to scan a whole tree of sourcefiles for use with Vim. One of the methods is:
sub parseDir {
my $self = shift;
my $path = shift; # the path to the directroy we are
# currently scanning.
my $out = shift; # the file we write the results to
my $target = shift; # the thing we are searching for
my $dir = IO::Dir->new($path) or die "can't open $path : $!";
my @files = $dir->read();
$dir->close();
# Scan all interesting files
grep( ( -f "$path/$_" ) and
( $_ =~ m/\.(java|xml|cpp|c|h|inc|pas)$/i ) and
( $self->Scan_File( "$path/$_", $out, $target ) ) , @file
+s );
# Also scan any subdirectories.
grep( ( ( -d "$path/$_" ) and
( $_ !~ /^\.+$/ ) and # but avoid . and ..
( $self->parseDir( "$path/$_", $out, $target ) ) ), @files
+ );
}
The odd thing is that the second grep works fine while the first grep results in a:
'Not enough arguments for grep at scan.pl line 63, near "@files )"'.
The only difference between the two is that the first has a '(' ')' pair less. I am quite puzzled why this makes a difference, since
both
( expression ) and ( expression ) and ( expression)
and
( ( expression ) and ( expression ) and ( expression) )
seem to me to be syntactically correct expression.
Can anybody shed some light on this?
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.