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.
  • 5.004? Are you serious? If you're doing it as an exercise in personal torture, ok, but hell, both 5.004_05 and 5.005_03 are past their 10 year "use by" date. I'd be interested to know if you've seen a 5.004 or even 5.005 in the wild that's actually being used for development, as opposed to just running some old code nobody touches anymore, and where an upgrade, or parallel Perl install, is not feasible.

    • I last used a 5.004 system for production purposes 3 years ago, but it was serious crufty and if it wasn't a charity stuck in a bad situation I would have insisted on an upgrade.

      I do know there's still a few 5.005 machines floating around, usually IRIX systems running old stuff.

      5.004 support is a nice to have, but can be sacrificed if needed. I'm more interested in the 5.005 support (although ONLY in the Tiny modules, everything else I'm happy to move to 5.6.1).

    • If you're doing it as an exercise in personal torture....

      I thought Template::Tiny was for Padre [perl.org], which I'd love to see running on IRIX with Perl 5.004.

      • The needs of Padre have created the specific demand, but all ::Tiny module gets used in a similar way. Just because it's needed for one thing, doesn't mean you make solutions only for that thing.

    • 5.004? Are you serious?

      He also said that loading the module should consume no more than 100kb. I would think 5.004 is a lesser constraint than that one; clearly he is serious. (Although combining both constraints… well, real Turing tar pits are even more compelling, so…)