Re^2: Fastest way to minimally check that file contains perl code?

[LanX]

> there's a whole category for Obfuscated code on PerlMonks

On a side note: It's possible to run Perl::Tidy in a server mode, which is far faster than starting it up for each file.

Though I doubt it's faster than perl -c , unless using/requiring a large tree of dependencies (like Moose) is causing the lag here.

[hippo]

The Moose argument is why I like vr's idea. If perl -c doesn't bomb out early on you can be pretty confident it is actually compiling Perl (with Moose or something equally heavy).

[LanX]

> it is actually compiling Perl (with Moose or something equally heavy)

Well, after the timeout you'd only have proven (again and again) that Moose contains Perl, the file in question could still be just garbage starting with use Moose

But yeah, this should be sufficient for the 80% threshold. :)