On Fri, May 21, 2004 at 06:25:17PM -0700, Philippe M. Chiasson wrote:
> Paul Johnson wrote:
>
> >On Tue, May 18, 2004 at 11:23:59AM -0700, Philippe M. Chiasson wrote:
> >
> >>The other issue is that CHECK/INIT blocks are not being called proprely
> >>under
> >>mod_perl 1.x, so moving the CHECK/INIT code in a sub of its own, allows
> >>the
> >>mod_perl user to do this in his/her startup script:
> >>
> >>use Devel::Cover;
> >>Devel::Cover::check;
> >>Devel::Cover::set_first_init_and_end;
> >
> >I'm probably showing my lack of knowledge, but is there any reason why I
> >couldn't check $ENV{MOD_PERL} and call those two subs in
> >Devel::Cover::import() ?
> >
> That would probably work, yes. My plan, after you introduced my patch
> was to write a simple Devel::Cover::Apache module for mod_perl users
> to use in place of Devel::Cover that would call those 2 subs. But it
> would be certainly simpler if Devel::Cover detected a mod_perl
> environment and took care of things by itself.
OK, I've just released Devel::Cover 0.45 which includes this change. It
seems to work OK for me on simple examples, but I'd be grateful for any
feedback.
> >I need to set up an environment to check all this, too.
> >
> Grab geoff's mp1 test skeleton here:
>
> http://www.apache.org/~geoff/bug-reporting-skeleton-mp1.tar.gz
>
> And just add :
>
> use Devel::Cover to t/conf/modperl_extra.pl
Ooh, that's nice! And suspiciously similar to a tarball Geoff sent me
for a bug in Devel:Cover ;-)
--
Paul Johnson - [EMAIL PROTECTED]
http://www.pjcj.net
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
