well, the problem with changing the source is that modperl_hooks.c is autogenerated - they'd need to know to alter ModPerl::Code, which is kinda less intuitive unless you're one of us :)
right, I haven't thought of that, but only looked at modperl_register_hooks in mod_perl.c
what bothers me about -D is that, the more I think about it, we're using -D in a way neither intended by core nor used by other modules. -D is specifically for <IfDefine> containers, while using -D in this way has little do to with that.
Not really, -D is used for many other things in Apache. So defining the hooks order via -D sounds as reasonable to me, as passing -DONE_PROCESS.
OK, what about env vars then? Sounds like the simplest solution then.
__________________________________________________________________ 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]
