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.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Module::Info (Score:2, Informative)

    by educated_foo (3106) on 2003.08.18 13:27 (#23266) Journal
    You might also look at using Module::Info, which (AFAIK) grovels around a bit in the op-tree to gather information. On the downside, you probably have to install the modules to make full use of M::I. However, you might be able to attach this as a "trojan" on CPANTS.

    /s

    • Module::Info can extract some information without loading the module, but to get what I need it has to load it so it's unfortunetly not an option.

      /me imagines a machine with all CPAN modules installed !

      • Hence the suggestion to piggyback this on top of CPANTS. To test a module, you have to have enough of an installation to make it run and function. So after running the tests (if they pass), CPANTS could automatically run a function to gather Module::Info data to send back with the results. I'm not sure how bad the politics of such a move would be, but it seems like a natural way to distribute an otherwise expensive computation.

        /s