If I felt as you do, I'd probably add a perlcritic check to my makes. But you could just use themes something like this:
#!/usr/bin/perl
use warnings;
use strict;
use File::Basename;
my ( $DEFAULT, $PM_THEME, $PL_THEME, $T_THEME )
= qw( rir rir_large rir rir );
my %themes = (
'.t' => $T_THEME,
'.pm' => $PM_THEME,
'.pl' => $PL_THEME,
);
my $file = pop @ARGV;
my ( $name, $path, $suffix ) = fileparse( $file, qr{\.\w+} );
local $, = ' ';
# forking could scale up better
if ($suffix) {
print `perlcritic @ARGV -theme $themes{$suffix} $file`;
}
else {
# STDIN or unknown extension ( or anything else YYY? )
print `perlcritic @ARGV -theme $DEFAULT $file`;
}
Be well, rir
-
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.
|