> -----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 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 modules needed for the site, but still
> selectively "use" the
> ones needed in each script and pray the list of common
> modules used doesn't
> change often!
http://perl.apache.org/guide/config.html#The_Confusion_with_use_at_the_
> Good job we have a Vim macro guru on-site :)
>
> There just seems something inherently bad to me about having a lot of
> duplicate sections of code across 100+ scripts -
but code isn't duplicated if you pre-load your modules:
http://perl.apache.org/guide/performance.html#Preload_Perl_Modules_at_Server
_S
as Vivek said earlier, in general, the guide makes for wonderful reading :)
--Geoff
> wouldn't it
> be easier if
> there was some way all these use module directives could be
> filtered out
> into one "load common boring stuff" line and not having to worry about
> namespace problems?
>
> Martin
>