I was thinking that in 2.0 we could have two different <> configuration
containers, where <PerlConf> will replace the <Perl> from 1.x, and
introducing <Perl> to do something else.
I want <Perl> sections to execute Perl code, whichever it is, in the
main:: package unless specified differently via package().
<PerlConf> is to operate only in the Apache::ModuleConfig namespace (at
least endorsed to).
Why doing this separation? Because it's too convenient to fire up a <Perl>
block to do some Perl, which has nothing to do with Apache configuration,
but mainly used for Perl modules configuration and similar. Now if you use
the existing <Perl> sections to perform the latter, you may pollute the
Apache::ModuleConfig namespace, inadvertedly declare package() and then
try to configure Apache, which won't work since you aren't in the
Apache::ModuleConfig namespace anymore.
So to avoid this confusion and make <Perl> sections mainly an addition for
PerlRequire, I think this separation is a good idea.
What do you think?
_____________________________________________________________________
Stas Bekman JAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide http://perl.apache.org/guide
mailto:[EMAIL PROTECTED] http://apachetoday.com http://eXtropia.com/
http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
