You may find File::Find helps clean up the logic:
use strict;
use warnings;
use File::Find;
my @matches = (qr(.*\.pl$), qr(.*\.pm$));
find(sub{wanted ($_, @matches)}, '.');
sub wanted {
my ($name, @m) = @_;
print "$File::Find::name\n" if grep {$name =~ /$_/} @m;
}
Prints (on my system - your results will be different):
./noname1.pl
./noname1.pm
./noname2.pl
./noname2.pm
./SortaIniParser.pm
./StarTrek.pl
./Win32/FileVersionInfo.pm
./Win32/PEFile.pm
You can replace the grep {$name =~ /$_/} @m test with whatever suits your purpose.
Optimising for fewest key strokes only makes sense transmitting to Pluto or beyond
-
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.
|