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.
  • Those who don't take reality into account make up laws instead and then kick people in the head for not following them
    • I'll put you on the "pro" side of literal tabs in Makefiles then, and five years of completely broken Scalar::Util in ActivePerl.

      • How is Scalar::Util broken in ActivePerl it is (at least supposed to be) the same as in core Perl.
        • As I understand it, it doesn't include (all of?) the XS components of the module, making reftype() unavailable for the ActivePerl 5.8.x releases.

          The explanation I heard (and I don't remember where, though I'm pretty sure it wasn't from you) is that one goal of the ActivePerl releases for 5.8.x was to maintain binary compatibility back to 5.8.0, and thus there would be no reftype() available for Scalar::Util.

          When I last looked at which of my distributions failed in the AS build and test farm, most of the

          • The explanation I heard [...] is that one goal of the ActivePerl releases for 5.8.x was to maintain binary compatibility back to 5.8.0, and thus there would be no reftype() available for Scalar::Util.

            I think it's reasonable to try to maintain binary backwards compatibility, but the problem seems to come from them breaking compatibility with Perl!

            Is the problem instead that we pretend that ActivePerl is Perl?

            P.S. Why is `make` considered broken, anyway, instead of the editors that can't highlight/insert tabs? Maybe they just aren't appropriate for editing Makfiles.