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.
  • However, the longer answer is that it depends. A discussion that keeps cropping up is whether older perls are applicable anymore. My suggestion would be that if you're testing on an environment that had a version of perl packaged with it, then test that and later versions only on that envirnoment. However, with some environments (e.g. Windows) that don't come pre-installed with Perl, then take your starting point from 5.6.1.

    The reason being that some environments have different configurations than earlier

    • I'd like to support 5.6 and 5.8 even though I'm developing on and only now use 5.10. It's not as if I'm taking advantage of many 5.8 features let alone 5.10. Debian Sarge and Etch both came with 5.8.x and Lenny will come with 5.10, so to find a 5.6 system you need to go back to Woody - which is well past it.

      At work I keep three Red Hat 7.x system alive (though I shouldn't really) and they use Perl 5.6, hence my plan to try and look at Perl on a system of that vintage.

      Windows is a different story. I suppose people tend to install ActiveState Perl and don't upgrade until they do their periodic Windows reinstallation. At the same time it's a pain to install quite a lot on Windows because most people don't have a compiler so they either don't install the package or install a binary PPM.

      --
      -- "It's not magic, it's work..."