#!/usr/bin/perl
use warnings;
use strict;
my $filename=shift || &help; # command line argument is perl script to
+ evaluate
my @modules; # array of 'use' statements from code we are checking
open (IN,$filename) or die "couldn't open $filename for processing: $!
+\n";
while (<IN>)
{
chomp;
if ((/^use/) and not (/strict/ || /warnings/))
{
push @modules,$_;
}
}
close IN;
for my $code (@modules)
{
my (undef,$library)=split(/ /,$code); # get the module name
$library=~s/;//; # clean up the name
eval $code;
if ($@)
{
warn "couldn't load $library: $@","\n";
}
else
{
print "$library looks ok\n";
};
}
sub help
{
print <<"END";
check_perl_modules.pl
This script finds all the "use" statements loading modules in the targ
+et perl
file (specified as a command line argument) and attempts to load them.
If there are problems loading the module, the error mesage returned is
+ printed.
END
exit;
}
-
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.
|