Kyle R. Burton on 8 Dec 2003 11:37:16 -0500 |
I'm using a script that runs 'perl -wc' over my modules before they're checked in to CVS. This has helped me catch quite a few errors in my code before I commit to CVS (including stray keystrokes and typos). The codebase has grown (it's about 1030 [Perl] source files at this point) and the process of running the perl -wc now takes quite a while. Is there any way to perform the same operation from within a script/program without resorting to the fork/exec? I'd like a utility that could crawl the source tree testing each module to see if it compiles cleanly - I just want it to be fast. I've read about Safe module for compartmentalized compilation or execution, but I've been unable to find a set of opcodes that allows me to eval/compile code successfully (I think I'm missing allowed op codes for use or require). I think that a temporary Safe compartment would be good because it could be flushed between compiles (though that might end up re-compiling lost of modules over and over, but it would be no worse than the external fork/exec). Any advice would be appreciated. Kyle -- ------------------------------------------------------------------------------ Wisdom and Compassion are inseparable. -- Christmas Humphreys mortis@voicenet.com http://www.voicenet.com/~mortis ------------------------------------------------------------------------------ - **Majordomo list services provided by PANIX <URL:http://www.panix.com>** **To Unsubscribe, send "unsubscribe phl" to majordomo@lists.pm.org**
|
|