in reply to Packaging multiple use statements into a module

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.

  • Comment on Re: Packaging multiple use statements into a module

Replies are listed 'Best First'.
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]
      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]
[reply]

In Section Seekers of Perl Wisdom