On Tue, 12 Dec 2000, Salvador Ortiz Garcia wrote:
> Do you think it is worth try to debug it?
i would be happy to see ApacheReadConfig gone and use Apache::ReadConfig
in both places, if you're up for it.
-
To unsubscribe, e-m
On Tue, 12 Dec 2000, Doug MacEachern wrote:
> guys, ApacheReadConfig is the original name, and still the name used
> internally.
> Apache::ReadConfig is an alias for ApacheReadConfig (see Apache.pm) and is
> documented as the public namespace.
I see.
> for some reason using Apache::ReadConfig i
On Wed, 13 Dec 2000, Stas Bekman wrote:
> > On Tue, 12 Dec 2000, Stas Bekman wrote:
>
> > > 1. It's Apache::ReadConfig, not ApacheReadConfig
> >
> > Sorry, no.
>
> sorry, yes :)
You are right, it's also Apache::ReadConfig ;-)
I'm thinking its time to change the C code. (and my own perl
guys, ApacheReadConfig is the original name, and still the name used
internally.
Apache::ReadConfig is an alias for ApacheReadConfig (see Apache.pm) and is
documented as the public namespace.
for some reason using Apache::ReadConfig internally caused problems, i
can't recall the details (the swit
> On Tue, 12 Dec 2000, Stas Bekman wrote:
>
> > On Tue, 12 Dec 2000, Salvador Ortiz Garcia wrote:
> >
> > > Anyway %ApacheReadConfig:: isn't documented in the main docs, and that is
> > > the main reason that many people are using long ... sections
> > > that can be sustituted by a simple and cl
On Tue, 12 Dec 2000, Stas Bekman wrote:
> On Tue, 12 Dec 2000, Salvador Ortiz Garcia wrote:
>
> > Anyway %ApacheReadConfig:: isn't documented in the main docs, and that is
> > the main reason that many people are using long ... sections
> > that can be sustituted by a simple and cleaner "PerlReq
On Tue, 12 Dec 2000, Salvador Ortiz Garcia wrote:
> Anyway %ApacheReadConfig:: isn't documented in the main docs, and that is
> the main reason that many people are using long ... sections
> that can be sustituted by a simple and cleaner "PerlRequire foobar".
Just to correct a few points :)
1
On Tue, 12 Dec 2000, Gerald Richter wrote:
> >
> > Where is declared that $PerlRequire?
> >
>
> Inside a Perl section..., so PerlRequire inside the Perl Section triggers
> perl_section_self_boot, which calls perl_section, which executes the
> PerlRequire inside the Perl section
>
> I think
>
> Where is declared that $PerlRequire?
>
Inside a Perl section..., so PerlRequire inside the Perl Section triggers
perl_section_self_boot, which calls perl_section, which executes the
PerlRequire inside the Perl section
I think you see what I mean...
>
> Can you please try this in both pe
On Tue, 12 Dec 2000, Gerald Richter wrote:
> > Before this change, the walking of the %ApacheReadConfig:: namespace
> > populated by a PerlRequire directive was ignored (or delayed).
> >
> > Because the
> >
> > SVt_PV: $PerlRequire = /opt/symphony/etc/httpd/startup.pl'
> >
> > from your trace I
10 matches
Mail list logo
