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

use Perl Log In

Log In

[ Create a new account ]

rjbs (4671)

  (email not shown publicly)
AOL IM: RicardoJBSignes (Add Buddy, Send Message)
Yahoo! ID: RicardoSignes (Add User, Send Message)

I'm a Perl coder living in Bethlehem, PA and working Philadelphia. I'm a philosopher and theologan by training, but I was shocked to learn upon my graduation that these skills don't have many associated careers. Now I write code.

Journal of rjbs (4671)

Wednesday September 03, 2008
08:08 AM

rx and module::pluggable; thanks, cpan testers!

[ #37336 ]

There's been a fresh outburst of acrimony about how CPAN testers just send unpleasant and useless email to people who don't care and can't benefit. Coincidentally, I got one of the most useful bug reports I've gotten in a long time from an automated tester.

I got a test report that seemed completely bizarre. I got another one from the same tester with the same message, too. It was complaining: Can't locate Data/Rx/CoreType/int/

What? I never tried to load that module. The closet I came was, in Data::Rx::Coretype::int, having this code:


Clearly this tester was on drugs, right, and had done something insane in his rig that no "real user" would ever do?

I contacted SREZIC, the smoker and he said he didn't know just what happened, but that the versions of Module::Pluggable differed between those two machines (which had 3.1) and another machine that passed (3.9).

Aha! It turns out that prior to Module::Pluggable 3.7, its inner-package finder (intended to find multiple packages inside of files) would find that SUPER call and try to load Oops!

Now I can update the prerequisite version for my dist to avoid this bug, and I've learned about a generally important to know about bug in a common module.

Thanks, CPAN Testers!

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.