perldelta - what is new for perl v5.19.11
This document describes differences between the 5.19.10 release and the 5.19.11 release.
If you are upgrading from an earlier release such as 5.19.9, first read perl51910delta, which describes differences between 5.19.9 and 5.19.10.
This pragma provides an easy and convenient way to enable or disable experimental features.
No changes have been made to the installed code other than the version bump to keep in sync with the latest CPAN release.
This fixes local::lib shell variable string output and prevents an endless loop when running "notest test Module" for some Module having dependencies.
The debugger now correctly restores its input and output filehandles after using the pager command. [perl #121456]
The MM_TEST_ROOT feature has been removed from the tests.
A regression in MM_Unix.pm has been resolved. [Issue #96]
The list of Perl versions covered has been updated.
The warning about the use of the
:utf8 layer has been made more prominent.
Recognition of tied SVs has been tightened up.
The following additions or changes have been made to diagnostic output, including warnings and fatal error messages. For the complete list of diagnostic messages, see perldiag.
Character following "\c" must be ASCIIhas been reworded as
Character following "\c" must be printable ASCIIto emphasize that in
\cX, X must be a printable (non-control) ASCII character.
On VMS only,
a check for glob metacharacters in a path returned by the
glob() operator has been replaced with a check for VMS wildcard characters.
This saves a significant number of unnecessary
lstat() calls such that some simple glob operations become 60-80% faster.
The time taken to build perl on Windows has been reduced quite significantly (time savings in the region of 30-40% are typically seen) by reducing the number of,
I/O calls for each
require() (for miniperl.exe only).
About 15 minutes of idle sleeping was removed from running
make test due to a bug in which the timeout monitor used for tests could not be cancelled once the test completes,
and the full timeout period elapsed before running the next test file.
On a perl built without pseudo-fork (pseudo-fork builds were not affected by this bug),
killing a process tree with
kill() and a negative signal resulted in
kill() inverting the returned value.
kill() killed 1 process tree PID then it returned 0 instead of 1,
kill() was passed 2 invalid PIDs then it returned 2 instead of 0.
This has probably been the case since the process tree kill feature was implemented on Win32.
It has now been corrected to follow the documented behaviour.
When building a 64-bit perl, an uninitialized memory read in miniperl.exe, used during the build process, could lead to a 4GB wperl.exe being created. This has now been fixed. (Note that perl.exe itself was unaffected, but obviously wperl.exe would have been completely broken.) [perl #121471]
Perl can now be built with gcc version 4.8.1 from http://www.mingw.org. This was previously broken due to an incorrect definition of DllMain() in one of perl's source files. Earlier gcc versions were also affected when using version 4 of the w32api package. Versions of gcc available from http://mingw-w64.sourceforge.net/ were not affected. [perl #121643]
The test harness now has no failures when perl is built on a FAT drive with the Windows OS on an NTFS drive. [perl #21442]
LC_NUMERICis now initialized to the C locale. This affects only XS modules, as the Perl core usages always make sure this locale category is correctly set for their purposes. XS code remains vulnerable to other code changing this category's locale. Further fixes are planned in Perl 5.22 to reduce these long-standing vulnerabilities. [perl #121317]
$!introduced in Perl 5.19.2 has been reverted for Perl 5.20. [perl #119499]
This re-breaks the bugs it fixed, perl #112208, so an alternative fix is planned for Perl 5.22
//mmatches to falsely fail. Now fixed. [perl #121484]
perl -I /somedir/(with a trailing slash) from finding .pmc files. This has been fixed. [perl #121512].
caller()introduced in Perl 5.18.0. In some circumstances when
caller()was called on an
eval STRINGstack frame it would attempt to allocate the limit of the address space minus one, which would croak with an out of memory error, which would be caught by the eval. A change in Perl 5.19.1 which increased allocation sizes to allow COW to operate more often rounded that allocation size up and wrapped to a zero allocation size, resulting in a crash when the source string was copied over. [perl #120998].
Perl 5.19.11 represents approximately 4 weeks of development since Perl 5.19.10 and contains approximately 3,600 lines of changes across 140 files from 18 authors.
Excluding auto-generated files, documentation and release tools, there were approximately 850 lines of changes to 72 .pm, .t, .c and .h files.
Perl continues to flourish into its third decade thanks to a vibrant community of users and developers. The following people are known to have contributed the improvements that became Perl 5.19.11:
Aaron Crane, Chris 'BinGOs' Williams, Craig A. Berry, Daniel Dragan, David Golden, David Mitchell, H.Merijn Brand, Hiroo Hayashi, Karl Williamson, Matthew Horsfall, Ricardo Signes, Shirakata Kentaro, Smylers, Steve Hay, Thomas Sibley, Tony Cook, Zefram, Ævar Arnfjörð Bjarmason.
The list above is almost certainly incomplete as it is automatically generated from version control history. In particular, it does not include the names of the (very much appreciated) contributors who reported issues to the Perl bug tracker.
Many of the changes included in this version originated in the CPAN modules included in Perl's core. We're grateful to the entire CPAN community for helping Perl to flourish.
For a more complete list of all of Perl's historical contributors, please see the AUTHORS file in the Perl source distribution.
If you find what you think is a bug, you might check the articles recently posted to the comp.lang.perl.misc newsgroup and the perl bug database at https://rt.perl.org/ . There may also be information at http://www.perl.org/ , the Perl Home Page.
If you believe you have an unreported bug,
please run the perlbug program included with your release.
Be sure to trim your bug down to a tiny but sufficient test case.
Your bug report,
along with the output of
will be sent off to firstname.lastname@example.org to be analysed by the Perl porting team.
If the bug you are reporting has security implications, which make it inappropriate to send to a publicly archived mailing list, then please send it to email@example.com. This points to a closed subscription unarchived mailing list, which includes all the core committers, who will be able to help assess the impact of issues, figure out a resolution, and help co-ordinate the release of patches to mitigate or fix the problem across all platforms on which Perl is supported. Please only use this address for security issues in the Perl core, not for modules independently distributed on CPAN.
The Changes file for an explanation of how to view exhaustive details on what changed.
The INSTALL file for how to build Perl.
The README file for general stuff.
The Artistic and Copying files for copyright information.