Is this correct?: You want a module that can be configured to do stuff differently depending on how it's configured. And you may want to have two or more of these configurations at the same time in the same program. (Otherwise you probably wouldn't worry about clashing variables.)
To me it seems like you want an object/class. 'instance1' of the object does it this way, 'instance2' of the object does it that way. The customization can then be done during class initialization and then you pass the class instance around and do stuff.
The following code is only for illustrative purposes. It is incomplete and will not compile. Assume 'Find::Files' is an actual module and does whatever you want it to do.
# first instance sub magic1 { ... } my $obj1 = Find::Files( 'function' => \&magic1 ); # let's do some magic! $obj1->find_and_call_function('/tmp'); # ------------------------------------------------ # second instance # can be in the same file or in another module sub magic2 { ... } my $obj2 = Find::Files( 'function' => \&magic2 ); # let's do some other magic! $obj2->find_and_call_function('/tmp');
In reply to Re: Design question: storing package 'flags'.
by Monk::Thomas
in thread Design question: storing package 'flags'.
by perl-diddler
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |