hi
I'm playing around with interpreter selection for #perl/mod_include support. anyway, I was wondering why modperl_run_filter_init() uses MP_dINTERP_SELECT to select the interpreter, but never puts the interpreter back into the pool. what happens to the remaining phases if PerlInterpScope is handler?
must be a bug then.
on that same note, I wasn't able to use MP_dINTERP_SELECT in my XS code due to a recurring 'invalid lvalue in assignment' (the aTHX=perl->interp part, it turns out). I ended up using MP_dTHX, which worked and was the last piece I needed to be able to port to threaded mpms :)
were you passing pTHX around? I can't tell without seeing the code.
so, I guess the question is, then, after selecting the interpreter, do I need to put it back into the pool if the scope is handler?
If you have picked one by yourself, yes, you need to put it back.
__________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
