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.

At Least the FAIL Part was Accurate 2 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.

  • Call it not a bug, a tiny missing check, a minor lazyness of the parrot build gears, whatever. In any case it's pretty inappropriate to call perldoc without precautions and simply letting the first one in $PATH win. Something like

            "${^X}doc ..."

    is quite a bit better, or using Pod::Simple directly with $^X. Such minor bugs in the build process can easily be spotted if you're so inclined to actually read reports from cpantesters.

    Chromatic, no bonus points for this posting.

    • In any case it's pretty inappropriate to call perldoc without precautions and simply letting the first one in $PATH win.

      I agree, and that's a bug in our configuration process which I've just now fixed. (The configuration system already detected perldoc, but it didn't actually set the value appropriately.)

      However, I can configure Parrot with Perl 5.10 and build it just fine without getting the Devel::Autoflush error from Perl 5.8.8. I don't even have that module installed on my system (and it's defin

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.