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?
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 :)
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?
--Geoff
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
