> -----Original Message-----
> From: Doug MacEachern [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, May 17, 2001 11:47 AM
> To: Geoffrey Young
> Cc: '[EMAIL PROTECTED]'
> Subject: RE: more Apache::Test stuff...
>
>
> On Thu, 17 May 2001, Geoffrey Young wrote:
>
> > these patches seem to solve the problem by moving PerlRequire (and
> > PerlSwitches?) to the preamble, thus insuring that @INC is
> modified before
> > seeing any extra configuration stuff...
>
> only problem is the patch causes pretty much all of 2.0's
> test to fail :-(
arg...
> i guess 2.0 doesn't have the ordering problem that 1.3 does,
> since with
> 2.0 there's no Perl code run until after all the
> configuration is read.
you mean that when 2.0 sees PerlModule it just checks to see if it's valid
then (later) perl checks for the module in @INC,
whereas 1.3 does all this as it happens? Same for (yet to be implemented?)
custom directives?
I guess that would get 2.0 around "features" such as
<Perl>
...
<Perl>
PerlTaintCheck On
# tainting is off for this PerlRequire but not for child processes
PerlRequire startup.pl
--Geoff
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
