Re: Code::Police

[tachyon]

in reply to Code::Police

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

[premchai21]

Now suppose I do this:

#!/usr/bin/perl -w
use SomeModule;use strict;
use Code::Police;

foo(); chomp, bar; something_else;

What happens here? The use strict is invisible to the Code::Police, and so tpircs ym yfisdrawkcab yeht.

Now, what if I do this?

#!/usr/bin/perl -w
use Code::Police;
BEGIN
{
    eval '#' . <<'';
use strict;

}

The Code::Police then see a strict where there isn't one, and let the script pass through unharmed. The original way of detecting strict I think is probably better.