Packaging multiple use statements into a module

djerius has asked for the wisdom of the Perl Monks concerning the following question:

I have several modules which perform the same long set of use statements. For example:

 use A;
 use B;
 use C;
[download]

I'd like to create a module (say ABC) which essentially performs the above use statements but runs the modules' import() routines in the module from which ABC is use'd. The latter part is the grotty part I'd like to avoid having to write (without it there's not much point in the whole exercise).

I'm pretty sure that there's a module on CPAN which handles this sort of thing and makes it effortless. I think I saw something closely related to this in the daily CPAN modules list a few months ago, but I can't find it.

Any help is appreciated.

Thanks, Diab

Comment on Packaging multiple use statements into a module Select or Download Code

Replies are listed 'Best First'.
Re: Packaging multiple use statements into a module by Fletch (Bishop) on Feb 08, 2010 at 21:28 UTC
Perhaps you're thinking of Toolkit? (No experience with it or opinion one way or the other, just actually remembered the name of it :) The cake is a lie. The cake is a lie. The cake is a lie.	[reply]
Re^2: Packaging multiple use statements into a module by Haarg (Priest) on Feb 08, 2010 at 23:01 UTC
There are two problems with Toolkit that I see. First is that it uses a source filter to do its work, and that is almost guaranteed to become a problem eventually. Second is that it is meant to load one set of modules that are defined per-machine. I think ToolSet is generally a better choice. In addition to not using source filters, it is meant to build your own modules for including groups of prerequisites. Being based on modules like this instead of a single per-machine list makes it redistributable as well.	[reply]
Re^3: Packaging multiple use statements into a module by djerius (Beadle) on Feb 09, 2010 at 17:26 UTC
After looking at ToolKit I've come to the same conclusions that you have. Thanks for pointing out ToolSet — it's much more along the lines of what I want. And it has the added benefit that I think I understand what it's doing!	[reply]
Re^2: Packaging multiple use statements into a module by djerius (Beadle) on Feb 08, 2010 at 21:36 UTC
Yes! That's exactly the one. Thanks a lot.	[reply]
Re^3: Packaging multiple use statements into a module by toolic (Bishop) on Feb 08, 2010 at 21:38 UTC
See Categorized Damian Modules to further guide your decision.	[reply]
Re: Packaging multiple use statements into a module by ikegami (Patriarch) on Feb 08, 2010 at 21:37 UTC
If you're using Exporter, you can use its `export_to_level`	[reply] [d/l]
Re^2: Packaging multiple use statements into a module by djerius (Beadle) on Feb 09, 2010 at 16:37 UTC
From my reading of Exporter's documentation, this would require modifications to the modules' import() routines. If a module didn't have its own import(), one could inject one into its namespace, but if it has its own one would have to tread more carefully. And, as you point out, this works only for modules which use Exporter.	[reply]