"perl -c file" seems very slow, for big amount of perl sources it is excessive, when all is needed is to check whether some file contains perl code or not. I dont need to check stricts or some complex conditions like possibility to load packages via "use" directives. For me it is absolutely enough to know that, say, file XXX is a perl source file with a probability of 80%. I dont need to execute anything in BEGIN {} blocks or check whether file syntactically correct for 100%. My goal is to separate perl source files from some garbage, when perl files and garbage files can have any "extensions" (because a lot of perl files i'm dealing with has names like foo.bar.abc.do-me.good). When i using perl -c it takes too much time to check, though i use AnyEvent and Proc::FastSpawn in my checker script.
I tried file and ohlohcount utilities as well, but its assumptions is VERY inaccurate.
So my Q is: are there any performance-oriented perl package or so to check whether some text is a perl code with some estimate of probability?
Thanks!
-
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.
|