Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

What's loaded? 3 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • > Using this in our code base shows 315 modules as loaded. Yikes!

    Think of all that functionality you didn't have to write, and how much useful functionality you can focus on because you're using these 315 modules. It's a plus, not a minus!

    If you're looking for a more useful way to present this information, you might want to whip up some CPAN cross-indexing magic to roll up the different class versions into distributions -- for instance, both File::Spec and File::Spec::Unix may be from the File::Spec distribution version 1.03.

    • The 315 modules is a plus if you can control the environment. If you have a large package that you want to distribute, the more dependencies you have, the more problems you have in making something easy to install. Witness the Bricolage package. Many folks have had a heck of a time trying to install it because of all of those dependencies. Plus, when some dependencies aren't even from the CPAN, the problem becomes even worse.

      • It's a typical trade-off. Since installation is the only place this is a problem I think we should focus on that instead of trying to get rid of dependencies, similar to how the Krang folks did. (Not that you say we should get rid of dependencies, other folks do.) Creating friendly installations is pretty low on most developers' todo lists though (me included).
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.