dorian wrote:
The two are not the same, as explained here:
http://perl.apache.org/docs/2.0/user/config/custom.html#Enabling_the_New_Configuration_Directives
"This [PerlLoadModule] directive is similar to PerlModule, but it
require()'s the Perl module immediately, causing an early mod_perl startup.
> The two are not the same, as explained here:
> http://perl.apache.org/docs/2.0/user/config/custom.html#Enabling_the_New_Configuration_Directives
>
> "This [PerlLoadModule] directive is similar to PerlModule, but it
> require()'s the Perl module immediately, causing an early mod_perl startup."
dorian taylor wrote:
if PerlLoadModule supplants the command table, i surmise it does
the job of PerlModule as well (which i understand to be roughly the
equivalent of 'use'). i'm wondering, would there ever be a reason
to load a module without wanting to supplant the command table with
any existin
if PerlLoadModule supplants the command table, i surmise it does
the job of PerlModule as well (which i understand to be roughly the
equivalent of 'use'). i'm wondering, would there ever be a reason
to load a module without wanting to supplant the command table with
any existing values that may be
