perldelta - what is new for perl v5.17.1
This document describes differences between the 5.17.0 release and the 5.17.1 release.
If you are upgrading from an earlier release such as 5.16.0, first read perl5170delta, which describes differences between 5.16.0 and 5.17.0.
Several more built-in functions have been added as subroutines to the CORE:: namespace,
namely,
those non-overridable keywords that can be implemented without custom parsers: defined,
delete,
exists,
glob,
pos,
protoytpe,
scalar,
split,
study,
and undef.
As some of these have prototypes,
prototype('CORE::...') has been changed to not make a distinction between overridable and non-overridable keywords.
This is to make prototype('CORE::pos') consistent with prototype(&CORE::pos).
/(?{})/ and /(??{})/ have been heavily reworkedThe implementation of this feature has been almost completely rewritten. Although its main intent is to fix bugs, some behaviors, especially related to the scope of lexical variables, will have changed. This is described more fully in the "Selected Bug Fixes" section.
\N{BELL} now refers to U+1F514 instead of U+0007Unicode 6.0 reused the name "BELL" for a different code point than it traditionally had meant. Since Perl v5.14, use of this name still referred to U+0007, but would raise a deprecation warning. Now, "BELL" refers to U+1F514, and the name for U+0007 is "ALERT". All the functions in charnames have been correspondingly updated.
You may no longer write something like:
m/a/and 1
Instead you must write
m/a/ and 1
with whitespace separating the operator from the closing delimiter of the regular expression. Not having whitespace has resulted in a deprecation warning since Perl v5.14.0.
require dies for unreadable filesWhen require encounters an unreadable file, it now dies. It used to ignore the file and continue searching the directories in @INC [perl #113422].
Unicode 6.2 is proposing some changes that may very well break some CPAN modules. The timing of this nicely coincides with Perl's being early in the release cycle. This commit takes the current beta 6.2, adds the proposed changes that aren't yet in it, and subtracts the changes that would affect \X processing, as those turn out to have errors, and may have to be rethought. Unicode has been notified of these problems.
This will allow us to gather data as to whether or not the proposed changes cause us problems. These will be presented to Unicode to aid in their final decision as to whether or not to go forward with the changes.
These changes will be replaced by the final version of Unicode 6.2 before 5.18.0 is released.
x repetition operator is now folded to a single constant at compile time if called in scalar context with constant operands and no parentheses around the left operand.Work around an edge case on Linux with Busybox's unzip.
ptar now supports the -T option as well as dashless options [rt.cpan.org #75473], [rt.cpan.org #75475].
Auto-encode filenames marked as UTF-8 [rt.cpan.org #75474].
Don't use tell on IO::Zlib handles [rt.cpan.org #64339].
Don't try to chown on symlinks.
B::COP::stashlen has been replaced with B::COP::stashoff.
B::COP::stashpv now supports UTF-8 package names and embedded NULs.
Avoid warning when run under perl -w.
The constructor now respects overridden accessor methods [perl #29230].
Upgrade bundled zlib to version 1.2.7.
Fix build failures on Irix, Solaris, and Win32, and also when building as C++ [rt.cpan.org #69985], [rt.cpan.org #77030], [rt.cpan.org #75222].
Treat undef requirements to from_string_hash as 0 (with a warning).
Added requirements_for_module method.
Allow adding blib/script to PATH.
Save the history between invocations of the shell.
Handle multiple makemakerargs and makeflags arguments better.
Use File::HomeDir when available, and provide PERL5_CPANPLUS_HOME to override the autodetection.
Always re-fetch CHECKSUMS if fetchdir is set.
Fix Digest::Perl::MD5 OO fallback [rt.cpan.org #66634].
This is due to a minor code change in the XS for the VMS implementation.
Manifest files are now correctly embedded for those versions of VC++ which make use of them. [perl #111782, #111798].
abs2rel could produce incorrect results when given two relative paths or the root directory twice [perl #111510].
Add SSL verification features [github #6], [github #9].
Include the final URL in the response hashref.
Add local_address option.
sync() can now be called on read-only file handles [perl #64772].
Use POSIX::_exit instead of exit in run_forked [rt.cpan.org #76901].
Fix the MERGE cache option.
Fixed bug where modules without $VERSION might have a version of '0' listed in 'provides' metadata, which will be rejected by PAUSE.
Fixed bug in PodParser to allow numerals in module names.
Fixed bug where giving arguments twice led to them becoming arrays, resulting in install paths like ARRAY(0xdeadbeef)/lib/Foo.pm.
Fix use of requires on perls installed to a path with spaces.
The option --libpods has been reinstated. It is deprecated, and its use does nothing other than issue a warning that it is no longer supported.
Since the HTML files generated by pod2html claim to have a UTF-8 charset, actually write the files out using UTF-8 [perl #111446].
See note about op_comp in the "Internal Changes" section below.
Fix interactions with Devel::Cover.
Don't eval code under no strict.
Fix an overloading issue with sum.
first and reduce now check the callback first (so &first(1) is disallowed).
Fix tainted on magical values [rt.cpan.org #55763].
Fix sum on previously magical values [rt.cpan.org #61118].
Fix reading past the end of a fixed buffer [rt.cpan.org #72700].
No longer require stat on filehandles.
Use fc for casefolding.
Add support for italics.
Improve error handling.
Fix glob semantics on Win32 [rt.cpan.org #49732].
Don't use Win32::GetShortPathName when calling perl [rt.cpan.org #47890].
Ignore -T when reading shebang [rt.cpan.org #64404].
Handle the case where we don't know the wait status of the test more gracefully.
Make the test summary 'ok' line overridable so that it can be changed to a plugin to make the output of prove idempotent.
Don't run world-writable files.
This adds a function all_casefolds() that returns all the casefolds.
link on Win32 now attempts to set $! to more appropriate values based on the Win32 API error code. [perl #112272]
Perl no longer mangles the environment block, e.g. when launching a new sub-process, when the environment contains non-ASCII characters. Known problems still remain, however, when the environment contains characters outside of the current ANSI codepage (e.g. see the item about Unicode in %ENV in http://perl5.git.perl.org/perl.git/blob/HEAD:/Porting/todo.pod). [perl #113536]
All C header files from the top-level directory of the distribution are now installed on VMS, providing consistency with a long-standing practice on other platforms. Previously only a subset were installed, which broke non-core extension builds for extensions that depended on the missing include files.
study function was made a no-op in 5.16. It was simply disabled via a return statement; the code was left in place. Now the code supporting what study used to do has been removed.cop->stashpv). Instead, there is an offset (cop->stashoff) into the new PL_stashpad array, which holds stash pointers.regexp_engine struct has acquired a new field op_comp, which is currently just for perl's internal use, and should be initialised to NULL by other regex plugin modules.alloccoptash has been added to the API, but is considered experimental. See perlapi.(?{}) and (??{}), has been heavily reworked to eliminate a whole slew of bugs. The main user-visible changes are:
/(?{ $x='{' })/
This means that this error message is longer generated:
Sequence (?{...}) not terminated or not {}-balanced in regex
but a new error may be seen:
Sequence (?{...}) not terminated with ')'
In addition, literal code blocks within run-time patterns are only compiled once, at perl compile-time:
for my $p (...) {
# this 'FOO' block of code is compiled once,
# at the same time as the surrounding 'for' loop
/$p{(?{FOO;})/;
}
/A(?{B})C/ behaves (from a closure viewpoint) exactly like /A/ && do { B } && /C/, while qr/A(?{B})C/ is like sub {/A/ && do { B } && /C/}. So this code now works how you might expect, creating three regexes that match 0, 1, and 2:
for my $i (0..2) {
push @r, qr/^(??{$i})$/;
}
"1" =~ $r[1]; # matches
use re 'eval' pragma is now only required for code blocks defined at runtime; in particular in the following, the text of the $r pattern is still interpolated into the new pattern and recompiled, but the individual compiled code-blocks within $r are reused rather than being recompiled, and use re 'eval' isn't needed any more:
my $r = qr/abc(?{....})def/;
/xyz$r/;
next etc. will not see any enclosing loops and caller will not see any calling subroutines. return returns a value from the code block, not from any enclosing subroutine. my $code = '(??{$x})';
for my $x (1..3) {
# recompile to see fresh value of $x each time
$x =~ /$code/;
}
/msix and (?msix) etc. flags are now propagated into the return value from (??{}); this now works:
"AB" =~ /a(??{'b'})/i;
re_eval:
use re 'eval'; $c = '(?{ warn "foo" })'; /$c/;
/(?{ warn "foo" })/;
formerly gave:
foo at (re_eval 1) line 1.
foo at (re_eval 2) line 1.
and now gives:
foo at (eval 1) line 1.
foo at /some/prog line 2.
vec no longer produces "uninitialized" warnings in lvalue context [perl #9423].(?:) or (?:|)) could disable some optimizations. This has been fixed.prototype produces when passed a string like "CORE::nonexistent_keyword" now passes UTF-8 and embedded NULs through unchanged [perl #97478].prototype now treats magical variables like $1 the same way as non-magical variables when checking for the CORE:: prefix, instead of treating them as subroutine names.caller, and possibly crashes [perl #113060].\&{$_[1]} in an attribute handler for a closure) no longer results in a copy of the subroutine (or assertion failures on debugging builds).eval '__PACKAGE__' now returns the right answer on threaded builds if the current package has been assigned over (as in *ThisPackage:: = *ThatPackage::) [perl #78742].caller to see a stack frame belonging to that deleted package. caller could crash if the stash's memory address was reused for a scalar and a substitution was performed on the same scalar [perl #113486].UNIVERSAL::can no longer treats its first argument differently depending on whether it is a string or number internally.open with <& for the mode checks to see whether the third argument is a number, in determining whether to treat it as a file descriptor or a handle name. Magical variables like $1 were always failing the numeric check and being treated as handle names.warn's handling of magical variables ($1, ties) has undergone several fixes. FETCH is only called once now on a tied argument or a tied $@ [perl #97480]. Tied variables returning objects that stringify as "" are no longer ignored. A tied $@ that happened to return a reference the previous time is was used is no longer ignored.warn "" now treats $@ with a number in it the same way, regardless of whether it happened via $@=3 or $@="3". It used to ignore the former. Now it appends "\t...caught", as it has always done with $@="3".$1 + 1) used to use floating point operations even where integer operations were more appropriate, resulting in loss of accuracy on 64-bit platforms [perl #109542].$x contains the string "dogs", -$x returns "-dogs" even if $y=0+$x has happened at some point.-'-10' was fixed to return "10", not "+10". But magical variables ($1, ties) were not fixed till now [perl #57706].UTF8 flag.tr/SEARCHLIST/REPLACEMENTLIST/ has been fixed. Only the first instance is supposed to be meaningful if a character appears more than once in SEARCHLIST. Under some circumstances, the final instance was overriding all earlier ones. [perl #113584]qr/\87/ previously silently inserted a NUL character, thus matching as if it had been written qr/\00087/. Now it matches as if it had been written as qr/87/, with a message that the sequence "\8" is unrecognized.__SUB__ now works in special blocks (BEGIN, END, etc.).BEGIN block. It still does not work properly, but it no longer crashes [perl #111610].\&{''} (with the empty string) now autovivifies a stub like any other sub name, and no longer produces the "Unable to create sub" error [perl #94476].Perl 5.17.1 represents approximately 4 weeks of development since Perl 5.17.0 and contains approximately 37,000 lines of changes across 710 files from 35 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.1:
?, Andy Dougherty, Aristotle Pagaltzis, Breno G. de Oliveira, Brian Fraser, Chris 'BinGOs' Williams, Craig A. Berry, David Mitchell, Dominic Hargreaves, Evan Miller, Father Chrysostomos, Florian Ragwitz, H.Merijn Brand, Herbert Breunung, Hugo van der Sanden, Jesse Luehrs, Karl Williamson, Karthik Rajagopalan, Lukas Mai, Martin Hasch, Michael Schroeder, Nicholas Clark, Paul Johnson, Reini Urban, Renee Baecker, Rhesa Rozendaal, Ricardo Signes, Shlomi Fish, Steve Hay, Steve Peters, Sullivan Beck, Tony Cook, Volker Schatz, Yves Orton, Zefram.
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.
