hey there amri, list, i would argue that static analysis has a limited application (near 0) in production. your t/perl_critic.t should be run before calling the release code complete. after the code has shipped, it should not change, and so the results of static analysis should also not change.
I'm blocking on [EMAIL PROTECTED] either approving or denying my request to s/CJCOLLIER/CJAC/ before uploading the first pass of HTML::Mason::Critic... if I don't hear back soon, I will bite the bullet and upload as CJCOLLIER. Cheers, C.J. (and Zelda in the left hand) On Thu, 2008-03-27 at 05:24 -0700, amiribarksdale wrote: > Hi folks: > > I am trying to tighten up the code in a web application I have made--I run > HTML::Mason and mod_perl--and I was trying to figure out how to run > Perl::Critic or some other diagnostic tool on the whole thing, so that it > would be active for every request and I could see problems throughout the > whole thing. I tried putting it in my main handler, but it only works on the > handler. I could put a use Perl::Critic on every Mason component, but that's > tedious. Is there a way to run such a module across a whole application? > > Amiri
signature.asc
Description: This is a digitally signed message part
------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________ Mason-users mailing list Mason-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mason-users
