Thanks for the tip - its something I will definitely explore. My entire
gripe with this problem has not been with performance or efficiency but with
readability and easy maintainability of the many scripts in our main
application - but we are getting there - and the great thing is there are so
man
Martin Wood wrote:
>
> > but code isn't duplicated if you pre-load your modules:
> >
> http://perl.apache.org/guide/performance.html#Preload_Perl_Modules_at_Server
> > _S
>
> I realise the actual code isn't duplicated - but the script itself still
> needs the list of "use" directives regardles
On Thu, 11 May 2000, Martin Wood wrote:
> >Please read the sections posted by Geoff and others. The *already* posted
> >link:
> >http://perl.apache.org/guide/config.html#The_Confusion_with_use_at_the_
> >answers your question.
>
> Damn mod_perl guide, much too comprehensive for its own good! :)
>Please read the sections posted by Geoff and others. The *already* posted
>link:
>http://perl.apache.org/guide/config.html#The_Confusion_with_use_at_the_
>answers your question.
Damn mod_perl guide, much too comprehensive for its own good! :)
> Please invest some time into reading before crying
On Thu, 11 May 2000, Martin Wood wrote:
> > but code isn't duplicated if you pre-load your modules:
> >
> http://perl.apache.org/guide/performance.html#Preload_Perl_Modules_at_Server
> > _S
>
> I realise the actual code isn't duplicated - but the script itself still
> needs the list of "use" d
Martin Wood wrote:
>
> Thanks for the replies so far all - things are already becoming clearer.
>
> > If you add a "standard" module to your set, how will it affect
> > existing apps if they don't directly need it or call it? Why have the
> > "use" statement at all if that particular module is
On Thu, 11 May 2000, Martin Wood wrote:
> Our Apache::Registry CGIs need access to a dozen or so core modules - is
> there an elegant solution to loading these without seeing a dozen or so use
> statements at the head of the script?
Yes. As Vivek pointed out, you can move them all into a startup
> but code isn't duplicated if you pre-load your modules:
>
http://perl.apache.org/guide/performance.html#Preload_Perl_Modules_at_Server
> _S
I realise the actual code isn't duplicated - but the script itself still
needs the list of "use" directives regardless of whether you pre-load them
and t
> -Original Message-
> From: Martin Wood [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, May 11, 2000 10:38 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Best approach for loading several modules
>
>
> Thanks for the replies so far all - things are already
> beco
Thanks for the replies so far all - things are already becoming clearer.
> If you add a "standard" module to your set, how will it affect
> existing apps if they don't directly need it or call it? Why have the
> "use" statement at all if that particular module is not being used?
So pre-load all
> "MW" == Martin Wood <[EMAIL PROTECTED]> writes:
MW> Our Apache::Registry CGIs need access to a dozen or so core modules - is
MW> there an elegant solution to loading these without seeing a dozen or so use
MW> statements at the head of the script? (We have over 100 different CGIs that
The "
Checkout Apache::RegistryLoader.
--Jeff
At 02:23 PM 5/11/00, Martin Wood wrote:
>Hi there,
>
>Our Apache::Registry CGIs need access to a dozen or so core modules - is
>there an elegant solution to loading these without seeing a dozen or so use
>statements at the head of the script? (We have over
Hi there,
Our Apache::Registry CGIs need access to a dozen or so core modules - is
there an elegant solution to loading these without seeing a dozen or so use
statements at the head of the script? (We have over 100 different CGIs that
share a common structure - it would be a nightmare maintaining
13 matches
Mail list logo
