On Thu, 26 Apr 2001, Stas Bekman wrote:
> sure, but that's a different matter. I say that PerlModule and PerlRequire
> have a bug, which should be fixed. It's just that your problem made me
> reiterate the problem.
patch below fixes. problem was the reference to
@Apache::ReadConfig::PerlConfig created an entry in %Apache::ReadConfig::,
which triggered perl_section_self_boot() to delete $INC{$startup_pl}
i think that using *Apache::ReadConfig elsewhere will still trigger the
double loading of all Perl{Require,Module}s, but i doubt the people
suffering from the double load problem are using that feature. so i'll
deal with that later.
> True, one of the reasons why I don't use DSO. I guess Doug dedicates all
> his time on 2.0, and rather not do anything else than the critical bug
> fixing for 1.x. But if anybody sends a patch in, the thing will be
> probably added. Doug, please correct me if I'm wrong.
i am still committed to supporting 1.xx, its just a matter of time. of
course it is much more fun working on the new stuff :)
--- Apache/Apache.pm 2001/01/29 16:07:08 1.62
+++ Apache/Apache.pm 2001/04/26 05:16:08
@@ -30,7 +30,10 @@
sub httpd_conf {
shift;
- push @Apache::ReadConfig::PerlConfig,
+ no strict 'refs';
+ #use a symbolic reference so %Apache::ReadConfig::
+ #is empty at compile time
+ push @{"Apache::ReadConfig::PerlConfig"},
map "$_\n", @_;
}
