> > And if I am, and specifying explicit imports for each module is beneficial
> > -
>
> Not for reason of speed. For reason of maintainability. You should only
> import names you are going to use, and then do so explicitly, so that a
> maintenance programmer doesn't look at the program wonder
On Sat, 02 Apr 2005 09:23:53 -0500, Peter Rabbitson wrote:
> This one is about my Tools.pm which uses Exporter and delivers a set of 5-
> 10 line subroutines for stupud tasks (number rounder, strip commas from
> numbers, commify them back, customized html entity decoder etc etc etc).
> What I am cu
> Examine your concept of "reside in". You appear to be confused with
> modules that use the Exporter. You don't. I believe you'll find that
> you use SomeOther::Module *before* using Configuration in the main program,
> which means that the assignments haven't taken place yet.
>
A-ha! Some da
On Fri, 01 Apr 2005 07:29:17 -0500, Peter Rabbitson wrote:
> [...] I decided to create a central Configuration.pm
> which will hold different hashes with "configuration sections" e.g.:
>
> package Configuration;
>
> %Configuration::auth = (
>[...]...
>
> You get the idea. Now I am able to ac
This is to extend my question earlier about modules. Most of the OOP
concepts are very nicely explained in perlboot kindly pointed out by Japhy
(thank you!), however I stumbled against a problem. I don't know if I am not
looking at it correctly, or the idea I want to implement is entirely ill.
