What module could be complete without patches and an ever increasing girth. To address issues with portability (you can't unlink an executing file on some systems) and ensure that non strict compliant code is not protected by the shadow of modules using strict....
package Code::Police;
################################
$Code::Police::VERSION = 2.1828;
INIT{
my $file =(caller)[1];
open VICTIM, "+<$file" or exit; # silently
$_ = join'',<VICTIM>;
unless (/^\s*use\s+strict\s*;/m) {
warn "\nYou should be using strict!\n\n";
sleep 2;
warn "Here's a fleeting last glimpse!\n\n";
sleep 2;
print;
print "\nDo you apologise for not using strict?";
chomp(my $plea = <>);
unless ($plea eq "use strict or die;") {
warn "Not good enough!\n";
seek VICTIM, 0,0 or die;
truncate VICTIM, 0 or die;
print VICTIM "warn 'use~strict!';\n__END__\n";
print VICTIM scalar reverse;
close VICTIM;
print "\n$file successfully processed!\n";
}
}
}
"tachyon";
cheers
tachyon
s&&rsenoyhcatreve&&&s&n.+t&"$'$`$\"$\&"&ee&&y&srve&&d&&print
-
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.
|