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

use Perl Log In

Log In

[ Create a new account ]

richardc (1662)

richardc
  (email not shown publicly)
http://unixbeard.net/~richardc/

Journal of richardc (1662)

Tuesday September 04, 2001
10:34 AM

a shower of sparks

[ #754 ]
So I'm bullying old versions of perl onto my laptop to test out Pod::Coverage (as well as some things for $day_job), I hope to push it back to at least 5.004_04, as yet I've only been hacking against 5.6.1.

Anyhow, sitting at the CPAN shell I tell it to install Pod::Coverage, which it starts to happily, asking about the prerequisites and installing them nicely. Then it's my turn.

All the tests explode.

From a quick poke it seems that Devel::Peek has moved into the core, and grown the CvGV subroutine. Unluckily this is the exact same subroutine that is used to identify if a subroutine was defined by the package P::C is examining, or just imported into it. This is a handy trick, since we don't really want to come down on people for using external modules and not documenting the things that got supplied by them.

My first thoughts are to factor this out into a derived class, but that's not so great as this routine is fairly useful as a default, and it's an interface/behaviour change that would be best avoided. Will give this more thought when I go home. Watch this space, or perl-qa