perl5175delta - what is new for perl v5.17.5
This document describes differences between the 5.17.4 release and the 5.17.5 release.
If you are upgrading from an earlier release such as 5.17.3, first read perl5174delta, which describes differences between 5.17.3 and 5.17.4.
Perl now supports the final version of Unicode 6.2. Earlier releases in the 5.17 series supported Unicode 6.2 beta versions. There were no substantive changes in the final Unicode 6.2 version from the most recent beta, included in Perl 5.17.4. A list of changes from Unicode 6.1 is at http://www.unicode.org/versions/Unicode6.2.0.
Poorly written perl code that allows an attacker to specify the count to perl's x string repeat operator can already cause a memory exhaustion denial-of-service attack.
A flaw in versions of perl before 5.15.5 can escalate that into a heap buffer overrun; coupled with versions of glibc before 2.16,
it possibly allows the execution of arbitrary code.
The flaw addressed to this commit has been assigned identifier CVE-2012-5195.
Unicode has now withdrawn their previous recommendation for regular expressions to automatically handle cases where a single character can match multiple characters case-insensitively; for example,
the letter LATIN SMALL LETTER SHARP S and the sequence ss.
This is because it turns out to be impracticable to do this correctly in all circumstances.
Because Perl has tried to do this as best it can,
it will continue to do so.
(We are considering an option to turn it off.) However,
a new restriction is being added on such matches when they occur in [bracketed] character classes.
People were specifying things such as /[\0-\xff]/i,
and being surprised that it matches the two character sequence ss (since LATIN SMALL LETTER SHARP S occurs in this range).
This behavior is also inconsistent with the using a property instead of a range: \p{Block=Latin1} also includes LATIN SMALL LETTER SHARP S,
but /[\p{Block=Latin1}]/i does not match ss.
The new rule is that for there to be a multi-character case-insensitive match within a bracketed character class,
the character must be explicitly listed,
and not as an end point of a range.
This more closely obeys the Principle of Least Astonishment.
See "Bracketed Character Classes" in perlrecharclass.
Note that a bug [perl #89774],
now fixed as part of this change,
prevented the previous behavior from working fully.
The warnings category for lexical subroutines is now "experimental::lexical_subs", with two colons, not "experimental:lexical_subs";
sort without arguments.
It now correctly omits the comma for system $prog @args and exec $prog @args.hex and oct have been rewritten,
eliminating several problems,
and making one incompatible change:
use bigint or use bigrat was compiled later would take precedence over the other,
causing hex and oct not to respect the other pragma when in scope.hex and oct anywhere else in the program to evalute their arguments in list context and prevent them from inferring $_ when called without arguments.oct("1234") return 1234 (for any number not beginning with 0) anywhere in the program.
Now "1234" is translated from octal to decimal,
whether within the pragma's scope or not.hex and oct now respect any existing overrides that were in place before the new overrides were installed,
falling back to them outside of the scope of use bignum.use bignum "hex",
use bignum "oct" and similar invocations for bigint and bigrat now export a hex or oct function,
instead of providing a global override.longmess() and shortmess() functions are now documented.link() when on Windows,
as on other OSes [perl #115100].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.
Support for MPE/IX has been removed.
The option to build without USE_SOCKETS_AS_HANDLES has been removed.
PL_formfeed has been removed.PL_compcv now points to the currently-compiling subroutine,
rather than the BEGIN block itself.mg_length has been deprecated.sv_len now always returns a byte count and sv_len_utf8 a character count.
Previously,
sv_len and sv_len_utf8 were both buggy and would sometimes returns bytes and sometimes characters.
sv_len_utf8 no longer assumes that its argument is in UTF8.
Neither of these creates UTF8 caches for tied or overloaded values or for non-PVs any more.sv_mortalcopy now copies string buffers of shared hash key scalars when called from XS modules [perl #79824].RXf_SPLIT and RXf_SKIPWHITE are no longer used.
They are now #defined as 0.RXf_MODIFIES_VARS flag can be set by custom regular expression engines to indicate that the execution of the regular expression may cause variables to be modified.
This lets s/// know to skip certain optimisations.
Perl's own regular expression engine sets this flag for the special backtracking verbs that set $REGMARK and $REGERROR.dump,
goto,
last,
next,
redo or require followed by a bareword (or version) and then an infix operator is no longer a syntax error.
It used to be for those infix operators (like +) that have a different meaning where a term is expected.
[perl #105924]require a::b .
1 and require a::b + 1 no longer produce erroneous ambiguity warnings.
[perl #107002]qr// used in m/// no longer triggers the "empty pattern reuses last pattern" behaviour.
[perl #96230]%^H) is tied,
compile-time scope entry (which copies the hint hash) no longer leaks memory if FETCH dies.
[perl #107000]split " " behaviour.
[perl #94490]defined scalar(@array),
defined do { &foo },
and similar constructs now treat the argument to defined as a simple scalar.
[perl #97466]*DB::DB glob or provides a subroutine stub for &DB::DB no longer results in a crash,
but an error instead.
[perl #114990]reset "" now matches its documentation.
reset only resets m?...? patterns when called with no argument.
An empty string for an argument now does nothing.
(It used to be treated as no argument.) [perl #97958]printf with an argument returning an empty list no longer reads past the end of the stack,
resulting in erratic behaviour.
[perl #77094]--subname no longer produces erroneous ambiguity warnings.
[perl #77240]v10 is now allowed as a label or package name.
This was inadvertently broken when v-strings were added in Perl 5.6.
[perl #56880]/[\@\\]||/ result in a "panic" error.
[perl #115050]length,
pos,
substr and sprintf could be confused by ties,
overloading,
references and typeglobs if the stringification of such changed the internal representation to or from UTF8.
[perl #114410]$tied =~ s/$non_utf8/$utf8/ no longer loops infinitely if the tied variable returns a Latin-1 string,
shared hash key scalar,
or reference or typeglob that stringifies as ASCII or Latin-1.
This is a regression from 5.12.x.s/// without /e is now better at detecting when it needs to forego certain optimisations,
fixing some buggy cases:
&&,
||,
.. and others) in the replacement part; e.g.,
s/(.)/$l{$a||$1}/g.
[perl #26986]s//$foo/) that causes the last-successful pattern to be used,
when that pattern contains code blocks that modify the variables in the replacement.s///e.$| autoflush variable is created on-the-fly when needed.
If this happened (e.g.,
if it was mentioned in a module or eval) when the currently-selected filehandle was a typeglob with an empty IO slot,
it used to crash.
[perl #115206]length($object) no longer returns the undefined value if the object has string overloading that returns undef.
[perl #115260]PL_stashcache,
the stash name lookup cache for method calls,
has been restored,
Commit da6b625f78f5f133 in August 2011 inadvertently broke the code that looks up values in PL_stashcache.
As it's a only cache,
quite correctly everything carried on working without it.
Perl 5.17.5 represents approximately 4 weeks of development since Perl 5.17.4 and contains approximately 17,000 lines of changes across 310 files from 32 authors.
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.17.5:
Aaron Crane, Adrian M. Enache, Andy Dougherty, Brad Gilbert, Chris 'BinGOs' Williams, Colin Kuskie, Craig A. Berry, Daniel Dragan, David Golden, David Mitchell, Dominic Hargreaves, Eric Brine, Father Chrysostomos, Florian Ragwitz, H.Merijn Brand, James E Keenan, Jerry D. Hedden, Jesse Luehrs, Karl Williamson, Nicholas Clark, Niko Tyni, Paul Johnson, Peter Martini, Reini Urban, Ricardo Signes, Ruslan Zakirov, Sawyer X, Smylers, Steffen Müller, Steve Hay, Tony Cook, Yves Orton.
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 http://rt.perl.org/perlbug/ . 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 perl -V,
will be sent off to perlbug@perl.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 perl5-security-report@perl.org. 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.
