On Thu, 19 Dec 2002, Stas Bekman wrote: > We need to start the interpreter early only to be able to feed the > configuration directives (PerlLoadModule and <Perl>). If there was a way > to start one interpreter to do the config processing and then somehow > start mod_perl normally after the config is over. I need to think some > more about it.
first problem: requires ithreads (not acceptable). also, it is likely PerlLoadModule and/or <Perl> will require some of the other config (e.g. PerlSwitches). trickiest part, merging data that was fed from one interpreter to another. > There is at least one problem with the current mod_perl cvs: If you have > PerlLoadModule followed by PerlSwitches, the latter will be lost, since > the interpreter will be already running by the time PerlSwitches is reached. its not lost, a config syntax error is thrown. the one i'm getting right now "too late for PerlSwitches". there's nothing wrong with requiring that PerlSwitches comes before PerlLoadModule. but order can indeed be painful with a generated httpd.conf. > My notebook has died and I can't reproduce it :( If that prevents from > making the release can you please backout this commit and then will get > back to it after the release. If there is no hurry, I'll look into when > I revive the notebook :( Sorry about that. out of time now, i'm leaving for the airport in a bit. might be able to get to it next week, tho painfully behind a slow dialup. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
