perldelta - what is new for perl v5.26.0
This document describes the differences between the 5.24.0 release and the 5.26.0 release.
/xxSpecifying two x characters to modify a regular expression pattern does everything that a single one does, but additionally TAB and SPACE characters within a bracketed character class are generally ignored and can be added to improve readability, like /[ ^ A-Z d-f p-x ]/xx. Details are at "/x and /xx" in perlre.
We have switched to a hybrid hash function to better balance performance for short and long keys.
For short keys, 16 bytes and under, we use an optimised variant of One At A Time Hard, and for longer keys we use Siphash 1-3. For very long keys this is a big improvement in performance. For shorter keys there is a modest improvement.
This adds a new modifier '~' to here-docs that tells the parser that it should look for /^\s*$DELIM\n/ as the closing delimiter.
These syntaxes are all supported:
<<~EOF;
<<~\EOF;
<<~'EOF';
<<~"EOF";
<<~`EOF`;
<<~ 'EOF';
<<~ "EOF";
<<~ `EOF`;The '~' modifier will strip, from each line in the here-doc, the same whitespace that appears before the delimiter.
Newlines will be copied as is, and lines that don't include the proper beginning whitespace will cause perl to croak.
For example:
if (1) {
print <<~EOF;
Hello there
EOF
}prints "Hello there\n" with no leading whitespace.
Perl now provides a way to build perl without . in @INC by default. If you want this feature, you can build with -Ddefault_inc_excludes_dot
Because the testing / make process for perl modules do not function well with . missing from @INC, Perl now supports the environment variable PERL_USE_UNSAFE_INC=1 which makes Perl behave as it previously did, returning . to @INC in all child processes.
WARNING: PERL_USE_UNSAFE_INC has been provided during the perl 5.25 development cycle and is not guaranteed to function in perl 5.26.
Unlike utf8_hop(), utf8_hop_safe() won't navigate before the beginning or after the end of the supplied buffer.
@{^CAPTURE} exposes the capture buffers of the last match as an array. So $1 is ${^CAPTURE}[0].
%{^CAPTURE} is the equivalent to %+ (ie named captures)
%{^CAPTURE_ALL} is the equivalent to %- (ie all named captures).
A list of changes is at http://www.unicode.org/versions/Unicode9.0.0/. Modules that are shipped with core Perl but not maintained by p5p do not necessarily support Unicode 9.0. Unicode::Normalize does work on 9.0.
\p{script} uses the improved Script_Extensions propertyUnicode 6.0 introduced an improved form of the Script (sc) property, and called it Script_Extensions (scx). As of now, Perl uses this improved version when a property is specified as just \p{script}. The meaning of compound forms, like \p{sc=script} are unchanged. This should make programs be more accurate when determining if a character is used in a given script, but there is a slight chance of breakage for programs that very specifically needed the old behavior. See "Scripts" in perlunicode.
As an experimental feature, Perl now allows the referencing operator to come after my(), state(), our(), or local(). This syntax must be enabled with use feature 'declared_refs'. It is experimental, and will warn by default unless no warnings 'experimental::refaliasing' is in effect. It is intended mainly for use in assignments to references. For example:
use experimental 'refaliasing', 'declared_refs';
my \$a = \$b;See "Assigning to References" in perlref for slightly more detail.
Some platforms natively do a reasonable job of collating and sorting in UTF-8 locales. Perl now works with those. For portability and full control, Unicode::Collate is still recommended, but now you may not need to do anything special to get good-enough results, depending on your application. See "Category LC_COLLATE: Collation: Text Comparisons and Sorting" in perllocale.
NUL charactersIn locales that have multi-level character weights, these are now ignored at the higher priority ones. There are still some gotchas in some strings, though. See "Collation of strings containing embedded NUL characters" in perllocale.
Using the lexical_subs feature no longer emits a warning. Existing code that disables the experimental::lexical_subs warning category that the feature previously used will continue to work. The lexical_subs feature has no effect; all Perl code can use lexical subroutines, regardless of what feature declarations are in scope.
CORE subroutines for hash and array functions callable via referenceThe hash and array functions in the CORE namespace--keys, each, values, push, pop, shift, unshift and splice--, can now be called with ampersand syntax (&CORE::keys(\%hash) and via reference (my $k = \&CORE::keys; $k->(\%hash)). Previously they could only be used when inlined.
The fundamentally unsafe tmpnam() interface was deprecated in Perl 5.22.0 and has now been removed. In its place you can use for example the File::Temp interfaces.
Formerly, require ::Foo::Bar would try to read /Foo/Bar.pm. Now any bareword require which starts with a double colon dies instead.
"{" characters in regular expression patterns are no longer permissibleYou have to now say something like "\{" or "[{]" to specify to match a LEFT CURLY BRACKET. This will allow future extensions to the language. This restriction is not enforced, nor are there current plans to enforce it, if the "{" is the first character in the pattern.
These have been deprecated since v5.16, with a deprecation message displayed starting in v5.22.
A variable name may no longer contain a literal control character under any circumstances. These previously were allowed in single-character names on ASCII platforms, but have been deprecated there since Perl v5.20. This affects things like $\cT, where \cT is a literal control (such as a NAK or NEGATIVE ACKNOWLEDGE character) in the source code.
NBSP is no longer permissible in \N{...}The name of a character may no longer contain non-breaking spaces. It has been deprecated to do so since Perl v5.22.
.) from @INCFor security reasons, @INC no longer contains the default directory (.).
On Unix systems, Perl treats any relative paths in the PATH environment variable as tainted when starting a new process. Previously, it was allowing a backslash to escape a colon (unlike the OS), consequently allowing relative paths to be considered safe if the PATH was set to something like /\:.. The check has been fixed to treat . as tainted in that example.
-Di switch is now required for PerlIO debugging outputPreviously PerlIO debugging output would be sent to the file specified by the PERLIO_DEBUG environment variable if perl wasn't running setuid and the -T or -t switches hadn't been parsed yet.
If perl performed output at a point where it hadn't yet parsed its switches this could result in perl creating or overwriting the file named by PERLIO_DEBUG even when the -T switch had been supplied.
Perl now requires the -Di switch to produce PerlIO debugging output. By default this is written to stderr, but can optionally be redirected to a file by setting the PERLIO_DEBUG environment variable.
If perl is running setuid or the -T switch has supplied PERLIO_DEBUG is ignored and the debugging output is sent to stderr as for any other -D switch.
${^ENCODING} has been removedConsequently, the encoding pragma's default mode is no longer supported. If you still need to write your source code in encodings other than UTF-8, use a source filter such as Filter::Encoding on CPAN or encoding's Filter option.
scalar(%hash) return signature changedThe value returned for scalar(%hash) will no longer show information about the buckets allocated in the hash. It will simply return the count of used keys. It is thus equivalent to 0+keys(%hash).
A form of backwards compatibility is provided via Hash::Util::bucket_ratio() which provides the same behavior as scalar(%hash) provided prior to Perl 5.25.
keys returned from an lvalue subroutinekeys returned from an lvalue subroutine can no longer be assigned to in list context.
sub foo : lvalue { keys(%INC) }
(foo) = 3; # death
sub bar : lvalue { keys(@_) }
(bar) = 3; # also an errorThis makes the lvalue sub case consistent with (keys %hash) = ... and (keys @_) = ..., which are also errors. [perl #128187]
In order for Perl to eventually allow string delimiters to be Unicode grapheme clusters (which look like a single character, but may be a sequence of several ones), we have to stop allowing a single char delimiter that isn't a grapheme by itself. These are unlikely to exist in actual code, as they would typically display as attached to the character in front of them.
A hash in boolean context is now sometimes faster, e.g.
if (!%h) { ... }This was already special-cased, but some cases were missed, and even the ones which weren't have been improved.
Several other ops may now also be faster in boolean context.
New Faster Hash Function on 64 bit builds
We use a different hash function for short and long keys. This should improve performance and security, especially for long keys.
readline is faster
Reading from a file line-by-line with readline() or <> should now typically be faster due to a better implementation of the code that searches for the next newline character.
Reduce cost of SvVALID().
$ref1 = $ref2 has been optimized.
Array and hash assignment are now faster, e.g.
(..., @a) = (...);
(..., %h) = (...);especially when the RHS is empty.
Reduce the number of odd special cases for the SvSCREAM flag.
Avoid sv_catpvn() in do_vop() when unneeded.
Enhancements in Regex concat COW implementation.
Speed up AV and HV clearing/undeffing.
Better optimise array and hash assignment
Converting a single-digit string to a number is now substantially faster.
The internal op implementing the split builtin has been simplified and sped up. Firstly, it no longer requires a subsidiary internal pushre op to do its work. Secondly, code of the form my @x = split(...) is now optimised in the same way as @x = split(...), and is therefore a few percent faster.
The rather slow implementation for the experimental subroutine signatures feature has been made much faster; it is now comparable in speed with the old-style my ($a, $b, @c) = @_.
Bareword constant strings are now permitted to take part in constant folding. They were originally exempted from constant folding in August 1999, during the development of Perl 5.6, to ensure that use strict "subs" would still apply to bareword constants. That has now been accomplished a different way, so barewords, like other constants, now gain the performance benefits of constant folding.
This also means that void-context warnings on constant expressions of barewords now report the folded constant operand, rather than the operation; this matches the behaviour for non-bareword constants.
Archive::Tar has been upgraded from version 2.04 to 2.24.
arybase has been upgraded from version 0.11 to 0.12.
attributes has been upgraded from version 0.27 to 0.29.
The deprecation message for the :unique and :locked attributes now mention they will disappear in Perl 5.28.
B has been upgraded from version 1.62 to 1.68.
B::Concise has been upgraded from version 0.996 to 0.999.
Its output is now more descriptive for op_private flags.
B::Debug has been upgraded from version 1.23 to 1.24.
B::Deparse has been upgraded from version 1.37 to 1.40.
B::Xref has been upgraded from version 1.05 to 1.06.
It now uses 3-arg open() instead of 2-arg open(). [perl #130122]
base has been upgraded from version 2.23 to 2.25.
bignum has been upgraded from version 0.42 to 0.47.
Carp has been upgraded from version 1.40 to 1.42.
charnames has been upgraded from version 1.43 to 1.44.
Compress::Raw::Bzip2 has been upgraded from version 2.069 to 2.074.
Compress::Raw::Zlib has been upgraded from version 2.069 to 2.074.
Config::Perl::V has been upgraded from version 0.25 to 0.28.
CPAN has been upgraded from version 2.11 to 2.18.
CPAN::Meta has been upgraded from version 2.150005 to 2.150010.
Data::Dumper has been upgraded from version 2.160 to 2.167.
The XS implementation now supports Deparse.
This fixes a stack management bug. [perl #130487].
DB_File has been upgraded from version 1.835 to 1.840.
Devel::Peek has been upgraded from version 1.23 to 1.26.
Devel::PPPort has been upgraded from version 3.32 to 3.35.
Devel::SelfStubber has been upgraded from version 1.05 to 1.06.
It now uses 3-arg open() instead of 2-arg open(). [perl #130122]
diagnostics has been upgraded from version 1.34 to 1.36.
It now uses 3-arg open() instead of 2-arg open(). [perl #130122]
Digest has been upgraded from version 1.17 to 1.17_01.
Digest::MD5 has been upgraded from version 2.54 to 2.55.
Digest::SHA has been upgraded from version 5.95 to 5.96.
DynaLoader has been upgraded from version 1.38 to 1.42.
Encode has been upgraded from version 2.80 to 2.88.
encoding has been upgraded from version 2.17 to 2.19.
This module's default mode is no longer supported as of Perl 5.25.3. It now dies when imported, unless the Filter option is being used.
encoding::warnings has been upgraded from version 0.12 to 0.13.
This module is no longer supported as of Perl 5.25.3. It emits a warning to that effect and then does nothing.
Errno has been upgraded from version 1.25 to 1.28.
Document that using %! loads Errno for you.
It now uses 3-arg open() instead of 2-arg open(). [perl #130122]
ExtUtils::Embed has been upgraded from version 1.33 to 1.34.
It now uses 3-arg open() instead of 2-arg open(). [perl #130122]
ExtUtils::MakeMaker has been upgraded from version 7.10_01 to 7.24.
ExtUtils::Miniperl has been upgraded from version 1.05 to 1.06.
ExtUtils::ParseXS has been upgraded from version 3.31 to 3.34.
ExtUtils::Typemaps has been upgraded from version 3.31 to 3.34.
feature has been upgraded from version 1.42 to 1.47.
Fixes the Unicode Bug in the range operator.
File::Copy has been upgraded from version 2.31 to 2.32.
File::Fetch has been upgraded from version 0.48 to 0.52.
File::Glob has been upgraded from version 1.26 to 1.28.
Issue a deprecation message for File::Glob::glob().
File::Spec has been upgraded from version 3.63 to 3.67.
FileHandle has been upgraded from version 2.02 to 2.03.
Filter::Simple has been upgraded from version 0.92 to 0.93.
It no longer treats no MyFilter immediately following use MyFilter as end-of-file. [perl #107726]
Getopt::Long has been upgraded from version 2.48 to 2.49.
Getopt::Std has been upgraded from version 1.11 to 1.12.
Hash::Util has been upgraded from version 0.19 to 0.22.
HTTP::Tiny has been upgraded from version 0.056 to 0.070.
Internal 599-series errors now include the redirect history.
I18N::LangTags has been upgraded from version 0.40 to 0.42.
It now uses 3-arg open() instead of 2-arg open(). [perl #130122]
IO has been upgraded from version 1.36 to 1.38.
IO-Compress has been upgraded from version 2.069 to 2.074.
IO::Socket::IP has been upgraded from version 0.37 to 0.38.
IPC::Cmd has been upgraded from version 0.92 to 0.96.
IPC::SysV has been upgraded from version 2.06_01 to 2.07.
JSON::PP has been upgraded from version 2.27300 to 2.27400_02.
lib has been upgraded from version 0.63 to 0.64.
It now uses 3-arg open() instead of 2-arg open(). [perl #130122]
List::Util has been upgraded from version 1.42_02 to 1.46_02.
Locale::Codes has been upgraded from version 3.37 to 3.42.
Locale::Maketext has been upgraded from version 1.26 to 1.28.
Locale::Maketext::Simple has been upgraded from version 0.21 to 0.21_01.
Math::BigInt has been upgraded from version 1.999715 to 1.999806.
There have also been some core customizations.
Math::BigInt::FastCalc has been upgraded from version 0.40 to 0.5005.
Math::BigRat has been upgraded from version 0.260802 to 0.2611.
Math::Complex has been upgraded from version 1.59 to 1.5901.
Memoize has been upgraded from version 1.03 to 1.03_01.
Module::CoreList has been upgraded from version 5.20170420 to 5.20170520.
Module::Load::Conditional has been upgraded from version 0.64 to 0.68.
Module::Metadata has been upgraded from version 1.000031 to 1.000033.
mro has been upgraded from version 1.18 to 1.20.
Net::Ping has been upgraded from version 2.43 to 2.55.
IPv6 addresses and AF_INET6 sockets are now supported, along with several other enhancements.
Remove sudo from 500_ping_icmp.t.
Avoid stderr noise in tests
Check for echo in new Net::Ping tests.
NEXT has been upgraded from version 0.65 to 0.67.
Opcode has been upgraded from version 1.34 to 1.39.
open has been upgraded from version 1.10 to 1.11.
OS2::Process has been upgraded from version 1.11 to 1.12.
It now uses 3-arg open() instead of 2-arg open(). [perl #130122]
overload has been upgraded from version 1.26 to 1.28.
Its compilation speed has been improved slightly.
parent has been upgraded from version 0.234 to 0.236.
perl5db.pl has been upgraded from version 1.50 to 1.51.
Ignore /dev/tty on non-Unix systems. [perl #113960]
Perl::OSType has been upgraded from version 1.009 to 1.010.
perlfaq has been upgraded from version 5.021010 to 5.021011.
PerlIO has been upgraded from version 1.09 to 1.10.
PerlIO::encoding has been upgraded from version 0.24 to 0.25.
PerlIO::scalar has been upgraded from version 0.24 to 0.26.
Pod::Checker has been upgraded from version 1.60 to 1.73.
Pod::Functions has been upgraded from version 1.10 to 1.11.
Pod::Html has been upgraded from version 1.22 to 1.2202.
Pod::Perldoc has been upgraded from version 3.25_02 to 3.28.
Pod::Simple has been upgraded from version 3.32 to 3.35.
Pod::Usage has been upgraded from version 1.68 to 1.69.
POSIX has been upgraded from version 1.65 to 1.76. This remedies several defects in making its symbols exportable. [perl #127821] The POSIX::tmpnam() interface has been removed, see "POSIX::tmpnam() has been removed". Trying to import POSIX subs that have no real implementations (like POSIX::atend()) now fails at import time, instead of waiting until runtime.
re has been upgraded from version 0.32 to 0.34
This adds support for the new /xx regular expression pattern modifier, and a change to the use re 'strict' experimental feature. When re 'strict' is enabled, a warning now will be generated for all unescaped uses of the two characters } and ] in regular expression patterns (outside bracketed character classes) that are taken literally. This brings them more in line with the ) character which is always a metacharacter unless escaped. Being a metacharacter only sometimes, depending on action at a distance, can lead to silently having the pattern mean something quite different than was intended, which the re 'strict' mode is intended to minimize.
Safe has been upgraded from version 2.39 to 2.40.
Scalar::Util has been upgraded from version 1.42_02 to 1.46_02.
Storable has been upgraded from version 2.56 to 2.62.
Fixes [perl #130098].
Symbol has been upgraded from version 1.07 to 1.08.
Sys::Syslog has been upgraded from version 0.33 to 0.35.
Term::ANSIColor has been upgraded from version 4.04 to 4.06.
Term::ReadLine has been upgraded from version 1.15 to 1.16.
It now uses 3-arg open() instead of 2-arg open(). [perl #130122]
Test has been upgraded from version 1.28 to 1.30.
It now uses 3-arg open() instead of 2-arg open(). [perl #130122]
Test::Harness has been upgraded from version 3.36 to 3.38.
Test::Simple has been upgraded from version 1.001014 to 1.302073.
Thread::Queue has been upgraded from version 3.09 to 3.12.
Thread::Semaphore has been upgraded from 2.12 to 2.13.
Added the down_timed method.
threads has been upgraded from version 2.07 to 2.15.
Compatibility with 5.8 has been restored.
Fixes [perl #130469].
threads::shared has been upgraded from version 1.51 to 1.56.
This fixes [cpan #119529], [perl #130457]
Tie::Hash::NamedCapture has been upgraded from version 0.09 to 0.10.
Time::HiRes has been upgraded from version 1.9733 to 1.9741.
It now builds on systems with C++11 compilers (such as G++ 6 and Clang++ 3.9).
Now uses clockid_t.
Time::Local has been upgraded from version 1.2300 to 1.25.
Unicode::Collate has been upgraded from version 1.14 to 1.19.
Unicode::UCD has been upgraded from version 0.64 to 0.68.
It now uses 3-arg open() instead of 2-arg open(). [perl #130122]
version has been upgraded from version 0.9916 to 0.9917.
VMS::DCLsym has been upgraded from version 1.06 to 1.08.
It now uses 3-arg open() instead of 2-arg open(). [perl #130122]
warnings has been upgraded from version 1.36 to 1.37.
XS::Typemap has been upgraded from version 0.14 to 0.15.
XSLoader has been upgraded from version 0.21 to 0.27.
Fixed a security hole in which binary files could be loaded from a path outside of @INC.
It now uses 3-arg open() instead of 2-arg open(). [perl #130122]
This file documents all upcoming deprecations, and some of the deprecations which already have been removed. The purpose of this documentation is two-fold: document what will disappear, and by which version, and serve as a guide for people dealing with code which has features that no longer work after an upgrade of their perl.
Use of unassigned code point or non-standalone grapheme for a delimiter will be a fatal error starting in Perl 5.30
This was changed to drop a leading v in v5.30, so it uses the same style as other deprecation messages.
"\c%c" is more clearly written simply as "%s".
It was decided to undeprecate the use of \c%c, see http://www.nntp.perl.org/group/perl.perl5.porters/2017/02/msg242944.html
Removed redundant dSP from an example.
All references to Usenet have been removed.
Updated documentation of scalar(%hash). See "scalar(%hash) return signature changed" above.
Use of single character variables, with the variable name a non printable character in the range \x80-\xFF is no longer allowed. Update the docs to reflect this.
All references to Usenet have been removed.
Deprecations are to be marked with a D. "%s() is deprecated on :utf8 handles" use a deprecation message, and as such, such be marked "(D deprecated)" and not "(W deprecated)".
Documented new feature: See "Declaring a reference to a variable" above.
Defined on aggregates is no longer allowed. Perlfunc was still reporting it as deprecated, and that it will be deleted in the future.
Clarified documentation of seek(), tell() and sysseek(). [perl #128607]
Removed obsolete documentation of study().
Add pTHX_ to magic method examples.
Document Tab VS Space.
perlinterp has been expanded to give a more detailed example of how to hunt around in the parser for how a given operator is handled.
Document NUL collation handling.
Some locales aren't compatible with Perl. Note the potential bad consequences of using them.
All references to Usenet have been removed.
Updated the mirror list.
All references to Usenet have been removed.
All references to Usenet have been removed.
Added a section on calling methods using their fully qualified names.
Do not discourage manual @ISA.
Tidy the document.
Mention Moo more.
Clarify behavior single quote regexps.
Several minor enhancements to the documentation.
Fixed link to Crosby paper on hash complexity attack.
Documented new feature: See "Declaring a reference to a variable" above.
Updated documentation of scalar(%hash). See "scalar(%hash) return signature changed" above.
Documented change to \p{script} to now use the improved Script_Extensions property. See "Use of \p{script} uses the improved Script_Extensions property" above.
Updated the text to correspond with changes in Unicode UTS#18, concerning regular expressions, and Perl compatibility with what it says.
Removed obsolete documentation of ${^ENCODING}. See "${^ENCODING} has been removed" above.
Document @ISA. Was documented other places, not not in perlvar.
Since . is now removed from @INC by default, do will now trigger a warning recommending to fix the do statement:
Using the empty pattern (which re-executes the last successfully-matched pattern) inside a code block in another regex, as in /(?{ s!!new! })/, has always previously yielded a segfault. It now produces an error: Infinite recursion in regex.
The experimental declared_refs feature is not enabled
(F) To declare references to variables, as in my \%x, you must first enable the feature:
no warnings "experimental::declared_refs";
use feature "declared_refs";Version control conflict marker
(F) The parser found a line starting with <<<<<<<, >>>>>>>, or =======. These may be left by a version control system to mark conflicts after a failed merge operation.
(A) You've accidentally run your script through bash or another shell instead of Perl. Check the #! line, or manually feed your script into Perl yourself. The #! line at the top of your file could look like:
#!/usr/bin/perl(A) You've accidentally run your script through zsh or another shell instead of Perl. Check the #! line, or manually feed your script into Perl yourself. The #! line at the top of your file could look like:
#!/usr/bin/perlUnescaped left braces are already illegal in some contexts in regular expression patterns, but, due to an oversight, no deprecation warning was raised in other contexts where they are intended to become illegal. This warning is now raised in these contexts.
Bareword in require must not start with a double-colon: "%s"
See "Deprecations"
Declaring references is experimental
(S experimental::declared_refs) This warning is emitted if you use a reference constructor on the right-hand side of my(), state(), our(), or local(). Simply suppress the warning if you want to use the feature, but know that in doing so you are taking the risk of using an experimental feature which may change or be removed in a future Perl version:
no warnings "experimental::declared_refs";
use feature "declared_refs";
$fooref = my \$foo;${^ENCODING} is no longer supported. Its use will be fatal in Perl 5.28
(D deprecated) The special variable ${^ENCODING}, formerly used to implement the encoding pragma, is no longer supported as of Perl 5.26.0.
When a require fails, we now do not provide @INC when the require is for a file instead of a module.
When @INC is not scanned for a require call, we no longer display @INC to avoid confusion.
Attribute "locked" is deprecated, and will disappear in Perl 5.28
Attribute "unique" is deprecated, and will disappear in Perl 5.28
Constants from lexical variables potentially modified elsewhere are deprecated. This will not be allowed in Perl 5.32
Deprecated use of my() in false conditional. This will be a fatal error in Perl 5.30
dump() better written as CORE::dump(). dump() will no longer be available in Perl 5.30
${^ENCODING} is no longer supported. Its use will be fatal in Perl 5.28
File::Glob::glob() will disappear in perl 5.30. Use File::Glob::bsd_glob() instead.
%s() is deprecated on :utf8 handles. This will be a fatal error in Perl 5.30
$* is no longer supported. Its use will be fatal in Perl 5.30
$* is no longer supported. Its use will be fatal in Perl 5.30
Opening dirhandle %s also as a file. This will be a fatal error in Perl 5.28
Opening filehandle %s also as a directory. This will be a fatal error in Perl 5.28
Setting $/ to a reference to %s as a form of slurp is deprecated, treating as undef. This will be fatal in Perl 5.28
Unescaped left brace in regex is deprecated here (and will be fatal in Perl 5.30), passed through in regex; marked by <-- HERE in m/%s/
Unknown charname '' is deprecated. Its use will be fatal in Perl 5.28
Use of bare << to mean <<"" is deprecated. Its use will be fatal in Perl 5.28
Use of code point 0x%s is deprecated; the permissible max is 0x%s. This will be fatal in Perl 5.28
Use of comma-less variable list is deprecated. Its use will be fatal in Perl 5.28
Use of inherited AUTOLOAD for non-method %s() is deprecated. This will be fatal in Perl 5.28
Use of strings with code points over 0xFF as arguments to %s operator is deprecated. This will be a fatal error in Perl 5.28
Improve error for missing tie() package/method. This brings the error messages in line with the ones used for normal method calls, despite not using call_method().
Make the sysread()/syswrite/() etc :utf8 handle warnings default. These warnings were under 'deprecated' previously.
'do' errors now refer to 'do' (not 'require').
Details as to the exact problem have been added to the diagnostics that occur when malformed UTF-8 is encountered when trying to convert to a code point.
Executing undef $x where $x is tied or magical no longer incorrectly blames the variable for an uninitialized-value warning encountered by the tied/magical code.
Unescaped left brace in regex is illegal here in regex; marked by <-- HERE in m/%s/
The word "here" has been added to the message that was raised in v5.25.1. This is to indicate that there are contexts in which unescaped left braces are not (yet) illegal.
Code like $x = $x . "a" was incorrectly failing to yield a use of uninitialized value warning when $x was a lexical variable with an undefined value. That has now been fixed. [perl #127877]
When the error "Experimental push on scalar is now forbidden" is raised for the hash functions keys, each, and values, it is now followed by the more helpful message, "Type of arg 1 to whatever must be hash or array". [perl #127976]
undef *_; shift or undef *_; pop inside a subroutine, with no argument to shift or pop, began crashing in Perl 5.14.0, but has now been fixed.
"string$scalar->$*" now correctly prefers concat overloading to string overloading if $scalar->$* returns an overloaded object, bringing it into consistency with $$scalar.
/@0{0*->@*/*0 and similar contortions used to crash, but no longer do, but merely produce a syntax error. [perl #128171]
do or require with a reference or typeglob which, when stringified, contains a null character started crashing in Perl 5.20.0, but has now been fixed. [perl #128182]
These old utilities have long since superceded by h2xs, and are now gone from the distribution.
Removed spurious executable bit.
Account for possibility of DOS file endings.
Many improvements
Tidy file, rename some symbols.
Replace obscure character range with \w.
try to be more helpful when tests fail.
Avoid infinite loop for enums.
Long lines in the message body are now wrapped at 900 characters, to stay well within the 1000-character limit imposed by SMTP mail transfer agents. This is particularly likely to be important for the list of arguments to Configure, which can readily exceed the limit if, for example, it names several non-default installation paths. This change also adds the first unit tests for perlbug. [perl #128020]
DEFAULT_INC_EXCLUDES_DOT has been turned on as default.
The dtrace build process has further changes:
If the -xnolibs is available, use that so a dtrace perl can be built within a FreeBSD jail.
On systems that build a dtrace object file (FreeBSD, Solaris and SystemTap's dtrace emulation), copy the input objects to a separate directory and process them there, and use those objects in the link, since dtrace -G also modifies these objects.
Add libelf to the build on FreeBSD 10.x, since dtrace adds references to libelf symbols.
Generate a dummy dtrace_main.o if dtrace -G fails to build it. A default build on Solaris generates probes from the unused inline functions, while they don't on FreeBSD, which causes dtrace -G to fail.
[perl #130108]
You can now disable perl's use of the PERL_HASH_SEED and PERL_PERTURB_KEYS environment variables by configuring perl with -Accflags=NO_PERL_HASH_ENV.
You can now disable perl's use of the PERL_HASH_SEED_DEBUG environment variable by configuring perl with -Accflags=-DNO_PERL_HASH_SEED_DEBUG.
Zero out the alignment bytes when calculating the bytes for 80-bit NaN and Inf to make builds more reproducible. [perl #130133]
Since 5.18 for testing purposes we have included support for building perl with a variety of non-standard, and non-recommended hash functions. Since we do not recommend the use of these functions we have removed them and their corresponding build options. Specifically this includes the following build options:
PERL_HASH_FUNC_SDBM
PERL_HASH_FUNC_DJB2
PERL_HASH_FUNC_SUPERFAST
PERL_HASH_FUNC_MURMUR3
PERL_HASH_FUNC_ONE_AT_A_TIME
PERL_HASH_FUNC_ONE_AT_A_TIME_OLD
PERL_HASH_FUNC_MURMUR_HASH_64A
PERL_HASH_FUNC_MURMUR_HASH_64BRemove "Warning: perl appears in your path"
This install warning is more or less obsolete, since most platforms already *will* have a /usr/bin/perl or similar provided by the OS.
Reduce verbosity of "make install.man"
Previously, two progress messages were emitted for each manpage: one by installman itself, and one by the function in install_lib.pl that it calls to actually install the file. Disabling the second of those in each case saves over 750 lines of unhelpful output.
Cleanup for clang -Weverything support. [perl 129961]
Configure: signbit scan was assuming too much, stop assuming negative 0.
Various compiler warnings have been silenced.
Several smaller changes have been made to remove impediments to compiling under C++11.
Builds using USE_PAD_RESET now work again; this configuration had bit-rotted.
A probe for gai_strerror was added to Configure that checks if the the gai_strerror() routine is available and can be used to translate error codes returned by getaddrinfo() into human readable strings.
Configure now aborts if both "-Duselongdouble" and "-Dusequadmath" are requested. [perl #126203]
Fixed a bug in which Configure could append "-quadmath" to the archname even if it was already present. [perl #128538]
Clang builds with "-DPERL_GLOBAL_STRUCT" or "-DPERL_GLOBAL_STRUCT_PRIVATE" have been fixed (by disabling Thread Safety Analysis for these configurations).
make_ext.pl no longer updates a module's pm_to_blib file when no files require updates. This could cause dependencies, perlmain.c in particular, to be rebuilt unnecessarily. [perl #126710]
The output of perl -V has been reformatted so that each configuration and compile-time option is now listed one per line, to improve readability.
Configure now builds miniperl and generate_uudmap if you invoke it with -Dusecrosscompiler but not -Dtargethost=somehost. This means you can supply your target platform config.sh, generate the headers and proceed to build your cross-target perl. [perl #127234]
Builds with -Accflags=-DPERL_TRACE_OPS now only dump the operator counts when the environment variable PERL_TRACE_OPS to be set to a non-zero integer. This allows make test to pass on such a build.
When building with GCC 6 and link-time optimization (the -flto option to gcc), Configure was treating all probed symbols as present on the system, regardless of whether they actually exist. This has been fixed. [perl #128131]
The t/test.pl library is used for internal testing of Perl itself, and also copied by several CPAN modules. Some of those modules must work on older versions of Perl, so t/test.pl must in turn avoid newer Perl features. Compatibility with Perl 5.8 was inadvertently removed some time ago; it has now been restored. [perl #128052]
The build process no longer emits an extra blank line before building each "simple" extension (those with only *.pm and *.pod files).
XS-APItest/t/utf8.t: Several small fixes and enhancements.
Tests for locales were erroneously using locales incompatible with Perl.
Some parts of the test suite that try to exhaustively test edge cases in the regex implementation have been restricted to running for a maximum of five minutes. On slow systems they could otherwise take several hours, without significantly improving our understanding of the correctness of the code under test.
In addition, some of those test cases have been split into more files, to allow them to be run in parallel on suitable systems.
A new internal facility allows analysing the time taken by the individual tests in Perl's own test suite; see Porting/harness-timer-report.pl.
t/re/regexp_nonull.t has been added to test that the regular expression engine can handle scalars that do not have a null byte just past the end of the string.
A new test script, t/op/decl-refs.t, has been added to test the new feature, "Declaring a reference to a variable".
A new test script, t/re/anyof.t, has been added to test that the ANYOF nodes generated by bracketed character classes are as expected.
t/harness now tries really hard not to run tests outside of the Perl source tree. [perl #124050]
Perl now compiles under NetBSD on VAX machines. However, it's not possible for that platform to implement floating-point infinities and NaNs compatibly with most modern systems, which implement the IEEE-754 floating point standard. The hexadecimal floating point (0x...p[+-]n literals, printf %a) is not implemented, either. The make test passes 98% of tests.
Test fixes and minor updates.
Account for lack of inf, nan, and -0.0 support.
don't treat -Dprefix=/usr as special, instead require an extra option -Ddarwin_distribution to produce the same results.
Finish removing POSIX deprecated functions.
OS X El Capitan doesn't implement the clock_gettime() or clock_getres() APIs, emulate them as necessary.
Deprecated syscall(2) on macOS 10.12.
Several tests have been updated to work (or be skipped) on EBCDIC platforms.
Net::Ping UDP test is skipped on HP-UX.
The hints for Hurd have been improved enabling malloc wrap and reporting the GNU libc used (previously it was an empty string when reported).
VAX floating point formats are now supported.
The path separator for the PERL5LIB and PERLLIB environment entries is now a colon (:) when running under a Unix shell. There is no change when running under DCL (it's still |).
Remove some VMS-specific hacks from showlex.t. These were added 15 years ago, and are no longer necessary for any VMS version now supported.
Move _pDEPTH and _aDEPTH after config.h otherwise DEBUGGING may not be defined yet.
VAXC has not been a possibility for a good long while, and the versions of the DEC/Compaq/HP/VSI C compiler that report themselves as "DEC" in a listing file are 15 years or more out-of-date and can be safely desupported.
Support for compiling perl on Windows using Microsoft Visual Studio 2015 (containing Visual C++ 14.0) has been added.
This version of VC++ includes a completely rewritten C run-time library, some of the changes in which mean that work done to resolve a socket close() bug in perl #120091 and perl #118059 is not workable in its current state with this version of VC++. Therefore, we have effectively reverted that bug fix for VS2015 onwards on the basis that being able to build with VS2015 onwards is more important than keeping the bug fix. We may revisit this in the future to attempt to fix the bug again in a way that is compatible with VS2015.
These changes do not affect compilation with GCC or with Visual Studio versions up to and including VS2013, i.e. the bug fix is retained (unchanged) for those compilers.
Note that you may experience compatibility problems if you mix a perl built with GCC or VS <= VS2013 with XS modules built with VS2015, or if you mix a perl built with VS2015 with XS modules built with GCC or VS <= VS2013. Some incompatibility may arise because of the bug fix that has been reverted for VS2015 builds of perl, but there may well be incompatibility anyway because of the rewritten CRT in VS2015 (e.g. see discussion at http://stackoverflow.com/questions/30412951).
Tweaks for Win32 VC vs GCC detection makefile code. This fixes issue that CCHOME depends on CCTYPE, which in auto detect mode is set after CCHOME, so CCHOME uses the uninit CCTYPE var. Also fix else vs .ELSE in makefile.mk
fp definitions have been updated.
Fix some breakage, add 'undef' value for default_inc_excludes_dot in build scripts.
Drop support for Linux a.out Linux has used ELF for over twenty years.
OpenBSD 6 still does not support returning pid, gid or uid with SA_SIGINFO. Make sure this is accounted for.
t/uni/overload.t: Skip hanging test on FreeBSD.
The op_class() API function has been added. This is like the existing OP_CLASS() macro, but can more accurately determine what struct an op has been allocated as. For example OP_CLASS() might return OA_BASEOP_OR_UNOP indicating that ops of this type are usually allocated as an OP or UNOP; while op_class() will return OPclass_BASEOP or OPclass_UNOP as appropriate.
The output format of the op_dump() function (as used by perl -Dx) has changed: it now displays an "ASCII-art" tree structure, and shows more low-level details about each op, such as its address and class.
New versions of macros like isALPHA_utf8 and toLOWER_utf8 have been added, each with the suffix _safe, like isSPACE_utf8_safe. These take an extra parameter, giving an upper limit of how far into the string it is safe to read. Using the old versions could cause attempts to read beyond the end of the input buffer if the UTF-8 is not well-formed, and their use now raises a deprecation warning. Details are at "Character classification" in perlapi.
Calling macros like isALPHA_utf8 on malformed UTF-8 have issued a deprecation warning since Perl v5.18. They now die. Similarly, macros like toLOWER_utf8 on malformed UTF-8 now die.
Calling the functions utf8n_to_uvchr and its derivatives, while passing a string length of 0 is now asserted against in DEBUGGING builds, and otherwise returns the Unicode REPLACEMENT CHARACTER. If you have nothing to decode, you shouldn't call the decode function.
The functions utf8n_to_uvchr and its derivatives now return the Unicode REPLACEMENT CHARACTER if called with UTF-8 that has the overlong malformation, and that malformation is allowed by the input parameters. This malformation is where the UTF-8 looks valid syntactically, but there is a shorter sequence that yields the same code point. This has been forbidden since Unicode version 3.1.
The functions utf8n_to_uvchr and its derivatives now accept an input flag to allow the overflow malformation. This malformation is when the UTF-8 may be syntactically valid, but the code point it represents is not capable of being represented in the word length on the platform. What "allowed" means in this case is that the function doesn't return an error, and advances the parse pointer to beyond the UTF-8 in question, but it returns the Unicode REPLACEMENT CHARACTER as the value of the code point (since the real value is not representable).
The PADOFFSET type has changed from being unsigned to signed, and several pad-related variables such as PL_padix have changed from being of type I32 to type PADOFFSET.
The function "utf8n_to_uvchr" in perlapi has been changed to not abandon searching for other malformations when the first one is encountered. A call to it thus can generate multiple diagnostics, instead of just one.
A new function, "utf8n_to_uvchr_error" in perlapi, has been added for use by modules that need to know the details of UTF-8 malformations beyond pass/fail. Previously, the only ways to know why a sequence was ill-formed was to capture and parse the generated diagnostics, or to do your own analysis.
Several new functions for handling Unicode have been added to the API: "is_strict_utf8_string" in perlapi, "is_c9strict_utf8_string" in perlapi, "is_utf8_string_flags" in perlapi, "is_strict_utf8_string_loc" in perlapi, "is_strict_utf8_string_loclen" in perlapi, "is_c9strict_utf8_string_loc" in perlapi, "is_c9strict_utf8_string_loclen" in perlapi, "is_utf8_string_loc_flags" in perlapi, "is_utf8_string_loclen_flags" in perlapi, "is_utf8_fixed_width_buf_flags" in perlapi, "is_utf8_fixed_width_buf_loc_flags" in perlapi, "is_utf8_fixed_width_buf_loclen_flags" in perlapi.
These functions are all extensions of the is_utf8_string_*() functions, that apply various restrictions to the UTF-8 recognized as valid.
A new API function sv_setvpv_bufsize() allows simultaneously setting the length and allocated size of the buffer in an SV, growing the buffer if necessary.
A new API macro SvPVCLEAR() sets its SV argument to an empty string, like Perl-space $x = '', but with several optimisations.
All parts of the internals now agree that the sassign op is a BINOP; previously it was listed as a BASEOP in regen/opcodes, which meant that several parts of the internals had to be special-cased to accommodate it. This oddity's original motivation was to handle code like $x ||= 1; that is now handled in a simpler way.
Several new internal C macros have been added that take a string literal as arguments, alongside existing routines that take the equivalent value as two arguments, a character pointer and a length. The advantage of this is that the length of the string is calculated automatically, rather than having to be done manually. These routines are now used where appropriate across the entire codebase.
The code in gv.c that determines whether a variable has a special meaning to Perl has been simplified.
The DEBUGGING-mode output for regex compilation and execution has been enhanced.
Several macros and functions have been added to the public API for dealing with Unicode and UTF-8-encoded strings. See "Unicode Support" in perlapi.
Use my_strlcat() in locale.c. While strcat() is safe in this context, some compilers were optimizing this to strcpy() causing a porting test to fail that looks for unsafe code. Rather than fighting this, we just use my_strlcat() instead.
Three new ops, OP_ARGELEM, OP_ARGDEFELEM and OP_ARGCHECK have been added. These are intended principally to implement the individual elements of a subroutine signature, plus any overall checking required.
Perl no longer panics when switching into some locales on machines with buggy strxfrm() implementations in their libc. [perl #121734]
Perl is now built with the PERL_OP_PARENT compiler define enabled by default. To disable it, use the PERL_NO_OP_PARENT compiler define. This flag alters how the op_sibling field is used in OP structures, and has been available optionally since perl 5.22.0.
See "Internal Changes" in perl5220delta for more details of what this build option does.
The meanings of some internal SV flags have been changed
OPpRUNTIME, SVpbm_VALID, SVpbm_TAIL, SvTAIL_on, SvTAIL_off, SVrepl_EVAL, SvEVALED
Change hv_fetch(…, "…", …, …) to hv_fetchs(…, "…", …)
The dual-life dists all use Devel::PPPort, so they can use this function even though it was only added in 5.10.
$-{$name} would leak an AV on each access if the regular expression had no named captures. The same applies to access to any hash tied with Tie::Hash::NamedCapture and all => 1. [perl #130822]
Attempting to use the deprecated variable $# as the object in an indirect object method call could cause a heap use after free or buffer overflow. [perl #129274]
When checking for an indirect object method call in some rare cases the parser could reallocate the line buffer but then continue to use pointers to the old buffer. [perl #129190]
Supplying a glob as the format argument to "formline" in perlfunc would cause an assertion failure. [perl #130722]
Code like $value1 =~ qr/.../ ~~ $value2 would have the match converted into a qr// operator, leaving extra elements on the stack to confuse any surrounding expression. [perl #130705]
Since 5.24.0 in some obscure cases, a regex which included code blocks from multiple sources (e.g. via embedded via qr// objects) could end up with the wrong current pad and crash or give weird results. [perl #129881]
Occasionally local()s in a code block within a patterns weren't being undone when the pattern matching backtracked over the code block. [perl #126697]
Using substr() to modify a magic variable could access freed memory in some cases. [perl #129340]
Perl 5.25.9 was fixed so that under use utf8, the entire Perl program is checked that the UTF-8 is wellformed. It turns out that several edge cases were missed, and are now fixed. [perl #126310] was the original ticket.
Under use utf8, the entire Perl program is now checked that the UTF-8 is wellformed. This resolves [perl #126310].
The range operator .. on strings now handles its arguments correctly when in the scope of the unicode_strings feature. The previous behaviour was sufficiently unexpected that we believe no correct program could have made use of it.
The split operator did not ensure enough space was allocated for its return value in scalar context. It could then write a single pointer immediately beyond the end of the memory block allocated for the stack. [perl #130262]
Using a large code point with the W pack template character with the current output position aligned at just the right point could cause a write a single zero byte immediately beyond the end of an allocated buffer. [perl #129149]
Supplying the form picture argument as part of the form argument list where the picture specifies modifying the argument could cause an access to the new freed compiled form. [perl #129125]
Fix a problem with sort's build-in compare, where it would not sort correctly with 64-bit integers, and non-long doubles. [perl #130335]
Fix issues with /(?{ ... <<EOF })/ that broke Method-Signatures. [perl #130398]
Fix a macro which caused syntax error on an EBCDIC build.
Prevent tests from getting hung up on 'NonStop' option. [perl #130445]
Fixed an assertion failure with chop and chomp, which could be triggered by chop(@x =~ tr/1/1/). [perl #130198].
Fixed a comment skipping error under /x; it could stop skipping a byte early, which could be in the middle of a UTF-8 character. [perl #130495].
perldb now ignores /dev/tty on non-Unix systems. [perl #113960];
Fix assertion failure for {}->$x when $x isn't defined. [perl #130496].
DragonFly BSD now has support for setproctitle(). [perl #130068].
Fix an assertion error which could be triggered when lookahead string in patterns exceeded a minimum length. [perl #130522].
Only warn once per literal about a misplaced _. [perl #70878].
Ensure range-start is set after error in tr///. [perl #129342].
Don't read past start of string for unmatched backref; otherwise, we may have heap buffer overflow. [perl #129377].
Properly recognize mathematical digit ranges starting at U+1D7E. use re 'strict' is supposed to warn if you use a range whose start and end digit aren't from the same group of 10. It didn't do that for five groups of mathematical digits starting at U+1D7E.
A sub containing a "forward" declaration with the same name (e.g., sub c { sub c; }) could sometimes crash or loop infinitely. [perl #129090]
A crash in executing a regex with a floating UTF-8 substring against a target string that also used UTF-8 has been fixed. [perl #129350]
Previously, a shebang line like #!perl -i u could be erroneously interpreted as requesting the -u option. This has been fixed. [perl #129336]
The regex engine was previously producing incorrect results in some rare situations when backtracking past a trie that matches only one thing; this showed up as capture buffers ($1, $2, etc) erroneously containing data from regex execution paths that weren't actually executed for the final match. [perl #129897]
Certain regexes making use of the experimental regex_sets feature could trigger an assertion failure. This has been fixed. [perl #129322]
Invalid assignments to a reference constructor (e.g., \eval=time) could sometimes crash in addition to giving a syntax error. [perl #125679]
The parser could sometimes crash if a bareword came after evalbytes. [perl #129196]
Autoloading via a method call would warn erroneously ("Use of inherited AUTOLOAD for non-method") if there was a stub present in the package into which the invocant had been blessed. The warning is no longer emitted in such circumstances. [perl #47047]
A sub containing with a "forward" declaration with the same name (e.g., sub c { sub c; }) could sometimes crash or loop infinitely. [perl #129090]
The use of splice on arrays with nonexistent elements could cause other operators to crash. [perl #129164]
Fixed case where re_untuit_start will overshoot the length of a utf8 string. [perl #129012]
Handle CXt_SUBST better in Perl_deb_stack_all, previously it wasn't checking that the current cx is the right type, and instead was always checking the base cx (effectively a noop). [perl #129029]
Fixed two possible use-after-free bugs in Perl_yylex. Perl_yylex maintains up to two pointers into the parser buffer, one of which can become stale under the right conditions. [perl #129069]
Fixed a crash with s///l where it thought it was dealing with UTF-8 when it wasn't. [perl #129038]
Fixed place where regex was not setting the syntax error correctly. [perl #129122]
The &. operator (and the & operator, when it treats its arguments as strings) were failing to append a trailing null byte if at least one string was marked as utf8 internally. Many code paths (system calls, regexp compilation) still expect there to be a null byte in the string buffer just past the end of the logical string. An assertion failure was the result. [perl #129287]
Check pack_sockaddr_un()'s return value because pack_sockaddr_un() silently truncates the supplied path if it won't fit into the sun_path member of sockaddr_un. This may change in the future, but for now check the path in thesockaddr matches the desired path, and skip if it doesn't. [perl #128095]
Make sure PL_oldoldbufptr is preserved in scan_heredoc(). In some cases this is used in building error messages. [perl #128988]
Check for null PL_curcop in IN_LC() [perl #129106]
Fixed the parser error handling for an ':attr(foo' that does not have an ending ')'.
Fix Perl_delimcpy() to handle a backslash as last char, this actually fixed two bugs, [perl #129064] and [perl #129176].
[perl #129267] rework gv_fetchmethod_pvn_flags separator parsing to prevent possible string overrun with invalid len in gv.c
Problems with in-place array sorts: code like @a = sort { ... } @a, where the source and destination of the sort are the same plain array, are optimised to do less copying around. Two side-effects of this optimisation were that the contents of @a as visible to to sort routine were partially sorted, and under some circumstances accessing @a during the sort could crash the interpreter. Both these issues have been fixed, and Sort functions see the original value of @a.
Non-ASCII string delimiters are now reported correctly in error messages for unterminated strings. [perl #128701]
pack("p", ...) used to emit its warning ("Attempt to pack pointer to temporary value") erroneously in some cases, but has been fixed.
@DB::args is now exempt from "used once" warnings. The warnings only occurred under -w, because warnings.pm itself uses @DB::args multiple times.
The use of built-in arrays or hash slices in a double-quoted string no longer issues a warning ("Possible unintended interpolation...") if the variable has not been mentioned before. This affected code like qq|@DB::args| and qq|@SIG{'CHLD', 'HUP'}|. (The special variables @- and @+ were already exempt from the warning.)
gethostent and similar functions now perform a null check internally, to avoid crashing with torsocks. This was a regression from 5.22. [perl #128740]
defined *{'!'}, defined *{'['}, and defined *{'-'} no longer leak memory if the typeglob in question has never been accessed before.
In 5.25.4 fchown() was changed not to accept negative one as an argument because in some platforms that is an error. However, in some other platforms that is an acceptable argument. This change has been reverted [perl #128967].
Mentioning the same constant twice in a row (which is a syntax error) no longer fails an assertion under debugging builds. This was a regression from 5.20. [perl #126482]
Many issues relating to printf "%a" of hexadecimal floating point were fixed. In addition, the "subnormals" (formerly known as "denormals") floating point anumbers are now supported both with the plain IEEE 754 floating point numbers (64-bit or 128-bit) and the x86 80-bit "extended precision". Note that subnormal hexadecimal floating point literals will give a warning about "exponent underflow". [perl #128843, #128889, #128890, #128893, #128909, #128919]
A regression in 5.24 with tr/\N{U+...}/foo/ when the code point was between 128 and 255 has been fixed. [perl #128734].
A regression from the previous development release, 5.23.3, where compiling a regular expression could crash the interpreter has been fixed. [perl #128686].
Use of a string delimiter whose code point is above 2**31 now works correctly on platforms that allow this. Previously, certain characters, due to truncation, would be confused with other delimiter characters with special meaning (such as ? in m?...?), resulting in inconsistent behaviour. Note that this is non-portable, and is based on Perl's extension to UTF-8, and is probably not displayable nor enterable by any editor. [perl #128738]
@{x followed by a newline where x represents a control or non-ASCII character no longer produces a garbled syntax error message or a crash. [perl #128951]
An assertion failure with %: = 0 has been fixed. [perl #128238]
In Perl 5.18, the parsing of "$foo::$bar" was accidentally changed, such that it would be treated as $foo."::".$bar. The previous behavior, which was to parse it as $foo:: . $bar, has been restored. [perl #128478]
Since Perl 5.20, line numbers have been off by one when perl is invoked with the -x switch. This has been fixed. [perl #128508]
Vivifying a subroutine stub in a deleted stash (e.g., delete $My::{"Foo::"}; \&My::Foo::foo) no longer crashes. It had begun crashing in Perl 5.18. [perl #128532]
Some obscure cases of subroutines and file handles being freed at the same time could result in crashes, but have been fixed. The crash was introduced in Perl 5.22. [perl #128597]
Code that looks for a variable name associated with an uninitialized value could cause an assertion in cases where magic is involved, such as $ISA[0][0]. This has now been fixed. [perl #128253]
A crash caused by code generating the warning "Subroutine STASH::NAME redefined" in cases such as sub P::f{} undef *P::; *P::f =sub{}; has been fixed. In these cases, where the STASH is missing, the warning will now appear as "Subroutine NAME redefined". [perl #128257]
Fixed an assertion triggered by some code that handles deprecated behavior in formats, e.g. in cases like this:
format STDOUT =
@
0"$x"A possible divide by zero in string transformation code on Windows has been avoided, fixing a crash when collating an empty string. [perl #128618]
Some regular expression parsing glitches could lead to assertion failures with regular expressions such as /(?<=/ and /(?<!/. This has now been fixed. [perl #128170]
until ($x = 1) { ... } and ... until $x = 1 now properly warn when syntax warnings are enabled. [perl #127333]
socket() now leaves the error code returned by the system in $! on failure. [perl #128316]
Assignment variants of any bitwise ops under the bitwise feature would crash if the left-hand side was an array or hash. [perl #128204]
require followed by a single colon (as in foo() ? require : ... is now parsed correctly as require with implicit $_, rather than require "". [perl #128307]
Scalar keys %hash can now be assigned to consistently in all scalar lvalue contexts. Previously it worked for some contexts but not others.
List assignment to vec or substr with an array or hash for its first argument used to result in crashes or "Can't coerce" error messages at run time, unlike scalar assignment, which would give an error at compile time. List assignment now gives a compile-time error, too. [perl #128260]
Expressions containing an && or || operator (or their synonyms and and or) were being compiled incorrectly in some cases. If the left-hand side consisted of either a negated bareword constant or a negated do {} block containing a constant expression, and the right-hand side consisted of a negated non-foldable expression, one of the negations was effectively ignored. The same was true of if and unless statement modifiers, though with the left-hand and right-hand sides swapped. This long-standing bug has now been fixed. [perl #127952]
reset with an argument no longer crashes when encountering stash entries other than globs. [perl #128106]
Assignment of hashes to, and deletion of, typeglobs named *:::::: no longer causes crashes. [perl #128086]
Handle SvIMMORTALs in LHS of list assign. [perl #129991]
[perl #130010] a5540cf breaks texinfo
This involved user-defined Unicode properties.
Fix error message for unclosed \N{ in regcomp.
An unclosed \N{ could give the wrong error message "\N{NAME} must be resolved by the lexer".
List assignment in list context where the LHS contained aggregates and where there were not enough RHS elements, used to skip scalar lvalues. Previously, (($a,$b,@c,$d) = (1)) in list context returned ($a); now it returns ($a,$b,$d). (($a,$b,$c) = (1)) is unchanged: it still returns ($a,$b,$c). This can be seen in the following:
sub inc { $_++ for @_ }
inc(($a,$b,@c,$d) = (10))Formerly, the values of ($a,$b,$d) would be left as (11,undef,undef); now they are (11,1,1).
[perl 129903]
The basic problem is that code like this: /(?{ s!!! })/ can trigger infinite recursion on the C stack (not the normal perl stack) when the last successful pattern in scope is itself. Since the C stack overflows this manifests as an untrappable error/segfault, which then kills perl.
We avoid the segfault by simply forbidding the use of the empty pattern when it would resolve to the currently executing pattern.
[perl 128997] Avoid reading beyond the end of the line buffer when there's a short UTF-8 character at the end.
[perl 129950] fix firstchar bitmap under utf8 with prefix optimisation.
[perl 129954] Carp/t/arg_string.t: be liberal in f/p formats.
[perl 129928] make do "a\0b" fail silently instead of throwing.
[perl 129130] make chdir allocate the stack it needs.
Some modules have been broken by the context stack rework. These modules were relying on non-guaranteed implementation details in perl. Their maintainers have been informed, and should contact perl5-porters for advice if needed. Below is a subset of these modules:
Coro and perl v5.22.0 were already incompatible due to a change in the perl, and the reworking on the perl context stack creates a further incompatibility. perl5-porters has discussed the issue on the mailing list.
The module lexical::underscore no longer works on perl v5.24.0, because perl no longer has a lexical $_!
mod_perl has been patched for compatibility for v5.22.0 and later but no release has been made. The relevant patch (and other changes) can be found in their source code repository, mirrored at GitHub.
Parsing bad POSIX charclasses no longer leaks memory. This was fixed in Perl 5.25.2 [perl #128313]
Fixed issues with recursive regexes. The behavior was fixed in Perl 5.24.0. [perl #126182]
Jon Portnoy (AVENJ), a prolific Perl author and admired Gentoo community member, has passed away on August 10, 2016. He will be remembered and missed by all those with which he came in contact and enriched with his intellect, wit, and spirit.
It is with great sadness we also note Kip Hampton's passing.. Probably best known as the author of the Perl & XML column on XML.com, he was a core contributor to AxKit, an XML server platform that became an Apache Foundation project. He was a frequent speaker in the early days at OSCON, and most recently at YAPC::NA in Madison. He was frequently on irc.perl.org as `ubu`, generally in the #axkit-dahut community, the group responsible for YAPC::NA Asheville in 2011.
Kip and his constant contributions to the community will be greatly missed.
Perl 5.26.0 represents approximately 12 months of development since Perl 5.24.0 and contains approximately 370,000 lines of changes across 2,600 files from 86 authors.
Excluding auto-generated files, documentation and release tools, there were approximately 230,000 lines of changes to 1,800 .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.24.1:
Aaron Crane, Abigail, Ævar Arnfjörð Bjarmason, Alex Vandiver, Andreas König, Andreas Voegele, Andrew Fresh, Andy Lester, Aristotle Pagaltzis, Chad Granum, Chase Whitener, Chris 'BinGOs' Williams, Chris Lamb, Christian Hansen, Christian Millour, Colin Newell, Craig A. Berry, Dagfinn Ilmari Mannsåker, Dan Collins, Daniel Dragan, Dave Cross, Dave Rolsky, David Golden, David H. Gutteridge, David Mitchell, Dominic Hargreaves, Doug Bell, E. Choroba, Ed Avis, Father Chrysostomos, François Perrad, Hauke D, H.Merijn Brand, Hugo van der Sanden, Ivan Pozdeev, James E Keenan, James Raspass, Jarkko Hietaniemi, Jerry D. Hedden, Jim Cromie, J. Nick Koston, John Lightsey, Karen Etheridge, Karl Williamson, Leon Timmermans, Lukas Mai, Matthew Horsfall, Maxwell Carey, Misty De Meo, Neil Bowers, Nicholas Clark, Nicolas R., Niko Tyni, Pali, Paul Marquess, Peter Avalos, Petr Písař, Pino Toscano, Rafael Garcia-Suarez, Reini Urban, Renee Baecker, Ricardo Signes, Richard Levitte, Rick Delaney, Salvador Fandiño, Samuel Thibault, Sawyer X, Sébastien Aperghis-Tramoni, Sergey Aleynikov, Shlomi Fish, Smylers, Stefan Seifert, Steffen Müller, Stevan Little, Steve Hay, Steven Humphrey, Sullivan Beck, Theo Buehler, Thomas Sibley, Todd Rinaldo, Tomasz Konojacki, Tony Cook, Unicode Consortium, Yaroslav Kuzmin, 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 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 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 see "SECURITY VULNERABILITY CONTACT INFORMATION" in perlsec for details of how to report the issue.
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.