Slash Boxes
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.
More | Login | Reply
Loading... please wait.
  • Wow! Definitely post the URL when it is available.
  • Hi,

    I was at YAPC::Europe last July, and I decided to try OODoc.

    OODoc requires a lot of documentation to be written out of the box, but beeing a lazy bastard, I subclassed it to generate documentation for me (basic stuff).

    I also do perl code parsing. If you like to compare code, or look at my code for it, email/jabber me at melo(at)

    Looking forward to seeing this in action!
    life is too short
  • CPAN!

    Adam Kennedy has written PPI [] which takes a good stab and parsing Perl with perl.


    broquaint out

  • 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.


    • 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.


  • Hi!

    For some part of Module::CPANTS::Generator, I wrote a parser (using Parse::RecDescent) that can parse (sort of good, I hope) a small aspect of Perl, namely "use" statements.

    The module is called Module-ExtractUse, it's on CPAN [] and you can view the results in Module::CPANTS' "uses" field.

    You might find it interesting. I'm definitly interested in your results (and I assume they will flow into Module::CPANTS?)

    While we're at it, take a look at this: CPANTS Web Interface []