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
thr
Jonathan Vanasco wrote:
On Mar 26, 2008, at 9:47 AM, Colin Wetherbee wrote:
We seem to have solved the problem, but for the sake of conversation...
When I've tried that in the past, mod_perl would always look for
handler() within JetSet::Handler::AccessHandler.pm.
Wow.
I've got 5 sites in p
On Mar 26, 2008, at 9:47 AM, Colin Wetherbee wrote:
We seem to have solved the problem, but for the sake of
conversation...
When I've tried that in the past, mod_perl would always look for
handler() within JetSet::Handler::AccessHandler.pm.
Wow.
I've got 5 sites in production right now..
Am Donnerstag, den 27.03.2008, 06:30 -0700 schrieb amiribarksdale:
> 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
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
