Stas Bekman wrote:
Geoffrey Young wrote:
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.
ok, I'll get a patch together for it.
cool, thanks.
IIRC, there is one other place that selects it but doesn't replace it, but I can't remember where it is.
probably could grep each file for SELECT/UNSELECT and see if there is uneven number?
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?
no. the code is called from mod_include, not mod_perl, so I have no way to get the context except via dTHX.
In that case you certainly have to do that, but only once and then pass it around if you have other functions that rely on it.
__________________________________________________________________ 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]
