On Sun, 9 Sep 2001, Stas Bekman wrote:
> but as you said we have this already, and it doesn't take the problem
> away. You have to remember to declare the package when you just want to
> run some code and switch back to Apache::ReadConfig when you want to do
> the configuration. To me it makes sense to let <Perl> run in the package
> main, unless specified differently and have <PerlConf> or whatever which
> explicitly declares the Apache::ReadConfig package for you. I'm just
> trying to make things less error-prone for users.
you think it will be less error-prone to change the behavior of
how <Perl> worked from 1.x? if you want something to run in package main,
say so with 'package main' or use PerlRequire. changing the behavior of
what <Perl> currently does and adding a new directive just to be in a
different package does not make any sense to me.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
