Re: Best approach for loading several modules

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

Re: Best approach for loading several modules

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 regardless of

Best approach for loading several modules

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

Re: Best approach for loading several modules

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 100

Re: Best approach for loading several modules

"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 "use"

Re: Best approach for loading several modules

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

RE: Best approach for loading several modules

-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 becoming clearer. If you add

Re: Best approach for loading several modules

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

Re: Best approach for loading several modules

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

Re: Best approach for loading several modules

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 not

Re: Best approach for loading several modules

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" directives

Re: Best approach for loading several modules

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