> -----Original Message----- > From: p sena > Well, might be possible with those hacks. However there would be some > more simpler solutions to this if we just need to compile check a list > of perl files. > For example a file 'a' consisting a statement of requiring file 'b' at > runtime, compile checking file a with conditions which makes file b > execute does serve the purpose.
Thanks, P Sena. Guess you're right. I want to make sure the files I'm dealing with do each compile individually without relying on others to have declared their global variables. If I have only one process to check a list of Perl files, crappy stuff might still compile because of other stuff having initialized it from afar. > some kind of custom test scenarios scripted down can also come as a > rescue... Getting each file to compile individually is my first step in a series of measures to raise code quality. Then, we can think about more advanced things like testing or perlcritic. You might have better ideas - if so, please let me know. Thanks! -- Michael Ludwig _______________________________________________ ActivePerl mailing list [email protected] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
