Perl has been updated! Head over here to get the new version, or go here to read up on the upcoming Perl 6, which remains in development. I have to say, however, I love a language that still supports VMS, HPUX and AIX in its most recent release. Below is an abreviated list of the changes in 5.12.3.
- We upgraded CGI.pm to version 3.49 to incorporate fixes for regressions introduced in the release we shipped with Perl 5.12.0.
- We upgraded Pod::Simple to version 3.14 to get an improvement to \C\<\< \>\> parsing.
- We made a small fix to the CPANPLUS test suite to fix an occasional spurious test failure.
- We upgraded Safe to version 2.27 to wrap coderefs retured by reval() and rdo().
- We fixed exporting of is_strict and is_lax from version. These were being exported with a wrapper that treated them as method calls, which caused them to fail. They are just functions, are documented as such, and should never be subclassed, so this patch just exports them directly as functions without the wrapper.
- t/op/sselect.t is now less prone to clock jitter during timing checks on Windows.
- sleep() time on Win32 may be rounded down to multiple of the clock tick interval.
- lib/blib.t and lib/locale.t: Fixes for test failures on Darwin/PPC
- perl5db.t: Fix for test failures when Term::ReadLine::Gnu is installed.
- Perl now allows -Duse64bitint without promoting to use64bitall on HP-UX
- Perl now builds on AIX 4.2
- The changes required work around AIX 4.2s' lack of support for IPv6, and limited support for POSIX sigaction().
- FreeBSD 7 no longer contains /usr/bin/objformat. At build time, Perl now skips the objformat check for versions 7 and higher and assumes ELF.
- It's now possible to build extensions on older (pre 7.3-2) VMS systems.
- DCL symbol length was limited to 1K up until about seven years or so ago, but there was no particularly deep reason to prevent those older systems from configuring and building Perl.
- We fixed the previously-broken -Uuseperlio build on VMS.
- We were checking a variable that doesn't exist in the non-default case of disabling perlio. Now we only look at it when it exists.
- We fixed the -Uuseperlio command-line option in configure.com.
- Formerly it only worked if you went through all the questions interactively and explicitly answered no.