PERL5400DELTA(1)
π PERL5400DELTA β what's new for perl v5.40.0 π
okay bestie, gather round, because this is perl5400delta, part of the Perl Programmers Reference Guide, and it's literally the glow-up diary of Perl. β¨
πΈ NAME πΈ
perl5400delta β what is new for perl v5.40.0. yes that's the whole name, she's simple like that π
π¦ DESCRIPTION π¦
This doc spills all the tea on the differences between the 5.38.0 release and the 5.40.0 release. that's it. that's the description. periodt.
π Core Enhancements π
β¨ New __CLASS__ Keyword β¨
so when you're using the new class feature, code inside a method, an ADJUST block, or a field initializer expression can now use the brand-new __CLASS__ keyword. π
it hands you a class name, kinda like __PACKAGE__, BUT β and this is the iconic part β while __PACKAGE__ gives you the compile-time package the code appears in, __CLASS__ is aware of the actual run-time class that the object instance is a member of. main character energy, fr fr. this makes it super useful for method dispatch on that class, especially during constructors, where you're not allowed to touch $self. π€
for more info, go peek at "__CLASS__" in perlfunc.
π :reader attribute for field variables π
when you're in your class feature era, field variables can now take a :reader attribute. what does it do? it politely requests that an accessor method be automatically created that just returns the value of the field variable from the given instance. slay.
field $name :reader;
is equivalent to
field $name;
method name () { return $name; }
you can also give it an alternative name, because customization is self-care:
field $name :reader(get_name);
for more detail, see ":reader" in perlclass. π
π
Permit a space in -M command-line option π
when perl is processing command-line options, it now allows a space between the -M switch and the name of the module after it. no cap.
$ perl -M Data::Dumper=Dumper -E 'say Dumper [1,2,3]'
this matches the existing behaviour of the -I option. consistency queen. π
π¨ Restrictions to use VERSION declarations π¨
back in Perl 5.36, a deprecation warning got added for when you downgrade a use VERSION declaration from one above version 5.11 down to below. welp, that's now a fatal error. π
also: it's now a fatal error to issue a subsequent use VERSION declaration when another one is in scope, when either version is 5.39 or above. this is to avoid complications surrounding imported lexical functions from builtin. and a deprecation warning has also been added for any other subsequent use VERSION declaration below version 5.39, warning you that it will no longer be permitted in Perl version 5.44. consider this your warning bestie π«Ά
π New builtin::inf and builtin::nan functions (experimental) π
two new functions, inf and nan, have joined the builtin namespace. they act like constants that yield the floating-point infinity and Not-a-Number value respectively. infinity and void, iconic duo. β¨
π₯ New ^^ logical xor operator π₯
Perl has always had three low-precedence logical operators β and, or and xor β plus three high-precedence bitwise versions &, ^ and |. but until this release, even though the medium-precedence logical operators && and || were also hanging around, there was NO exclusive-or equivalent. the set was incomplete. the tragedy. π
this release of Perl adds the final ^^ operator, completing the set. she's the missing piece. the final girlboss.
$x ^^ $y and say "One of x or y is true, but not both";
π try/catch feature is no longer experimental π
before this release, the try/catch feature for handling errors was considered experimental. it was introduced way back in Perl version 5.34.0, and now it's officially a stable language feature and using it no longer prints a warning. glow-up complete. π it still must be enabled with the 'try' feature though, don't forget.
see "Try Catch Exception Handling" in perlsyn.
π¦ for iterating over multiple values at a time is no longer experimental π¦
previously, iterating over multiple values at a time with for was experimental. introduced in Perl version 5.36.0, it's now a stable language feature and using it no longer prints a warning. she graduated. π
see "Compound Statements" in perlsyn.
πΈ builtin module is no longer experimental πΈ
before this release, the builtin module and all of its functions were considered experimental. introduced in Perl version 5.36.0, this module is now considered stable and its use no longer prints a warning. HOWEVER β plot twist β several of its functions are still considered experimental. π so like, the module ate, but some of the functions are still in their testing era.
β The :5.40 feature bundle adds try β
the latest version feature bundle now contains the recently-stablized feature try. and since this feature bundle is used by the -E commandline switch, these are immediately available in -E scripts. instant access, no assembly required. π₯
π use v5.40; imports builtin functions π
in addition to importing a feature bundle, use v5.40; (or later versions) imports the corresponding builtin version bundle. two for one, we love a bundle deal. π
π Security π
π CVE-2023-47038 - Write past buffer end via illegal user-defined Unicode property π
this vulnerability was reported directly to the Perl security team by Nathan Mills the.true.nathan.mills@gmail.com. thank you Nathan, king behaviour. π«‘
a crafted regular expression, when compiled by perl 5.30.0 through 5.38.0, can cause a one-byte attacker controlled buffer overflow in a heap allocated buffer. that's a whole yikes, no cap.
π CVE-2023-47039 - Perl for Windows binary hijacking vulnerability π
this vulnerability was reported to the Intel Product Security Incident Response Team (PSIRT) by GitHub user ycdxsb <https://github.com/ycdxsb/WindowsPrivilegeEscalation>. PSIRT then reported it to the Perl security team. chain of custody, we love to see it.
Perl for Windows relies on the system path environment variable to find the shell (cmd.exe). when running an executable which uses the Windows Perl interpreter, Perl attempts to find and execute cmd.exe within the operating system. HOWEVER β due to path search order issues β Perl initially looks for cmd.exe in the current working directory. π
an attacker with limited privileges can exploit this behavior by placing cmd.exe in locations with weak permissions, such as C:\ProgramData. by doing so, when an administrator attempts to use this executable from these compromised locations, arbitrary code can be executed. genuinely terrifying, stay safe out there bestie π¨
π Incompatible Changes π
π reset EXPR now calls set-magic on scalars π
previously, reset EXPR did not call set magic when clearing scalar variables. this meant changes didn't propagate to the underlying internal state where needed β like for $^W β and didn't result in an exception where the underlying magic would normally throw one, like for $1.
so basically: code that had no effect before may now actually have an effect, including possibly throwing an exception. surprises incoming. π
reset EXPR already called set magic when modifying arrays and hashes, for the record.
this has no effect on plain reset used to reset one-match searches as with m?pattern?. that one's fine. breathe.
[GH #20763 <https://github.com/Perl/perl5/issues/20763>]
π Calling the import method of an unknown package produces a warning π
historically, it's been possible to call the import or unimport method of any class β including ones which have not been defined β with an argument, and not experience an error. for instance, this code will not throw an error in Perl 5.38:
Class::That::Does::Not::Exist->import("foo");
but as of Perl 5.39.1, this is deprecated and will issue a warning. π’
note that calling these methods with no arguments continues to silently succeed and do nothing. for instance,
Class::That::Does::Not::Exist->import();
will continue to not throw an error. why? because every class implicitly inherits from the class UNIVERSAL, which now defines an import method. in older perls there was no such method defined, and instead the method calls for import and unimport were special cased to not throw errors if there was no such method defined. lore. π
this change was added because it makes it easier to detect case typos in use statements when running on case-insensitive file systems. for instance, on Windows or other platforms with case-insensitive file systems, on older perls the following code
use STRICT 'refs';
would silently do nothing, because the module is actually called strict.pm, not STRICT.pm β so it would be loaded but its import method would never be called. sneaky. π it will also detect cases where a user passes an argument when using a package that does not provide its own import β for instance, most "pure" class definitions do not define an import method.
π return no longer allows an indirect object π
the return operator syntax now rejects indirect objects. in most cases this would compile and even run, but it wasn't documented and could produce confusing results. example:
# note that sum hasn't been defined
sub sum_positive {
return sum grep $_ > 0, @_;
# unexpectedly parsed as:
# return *sum, grep $_ > 0, @_;
# ... with the bareword acting like an extra (typeglob) argument
}
say for sum_positive(-1, 2, 3)
produced:
*main::sum
2
3
yeah. that's the chaos we're no longer tolerating. π
[GH #21716 <https://github.com/Perl/perl5/issues/21716>]
π Class barewords no longer resolved as file handles in method calls under no feature "bareword_filehandles" π
under no feature "bareword_filehandles", bareword file handles continued to be resolved in method calls:
open FH, "<", $somefile or die;
no feature 'bareword_filehandles';
FH->binmode;
this has been fixed, so the:
FH->binmode;
will attempt to resolve FH as a class, typically resulting in a runtime error. π¬
the standard file handles such as STDOUT continue to be resolved as a handle:
no feature 'bareword_filehandles';
STDOUT->flush; # continues to work
note that once perl resolves a bareword name as a class, it will continue to do so:
package SomeClass {
sub somemethod{}
}
open SomeClass, "<", "somefile" or die;
# SomeClass resolved as a handle
SomeClass->binmode;
{
no feature "bareword_filehandles";
SomeClass->somemethod;
}
# SomeClass resolved as a class
SomeClass->binmode;
once she picks a lane, she stays in it. π
[GH #19426 <https://github.com/Perl/perl5/issues/19426>]
π§οΈ Deprecations π§οΈ
- using
gototo jump from an outer scope into an inner scope is deprecated and will be removed completely in Perl 5.42. so like, don't. [GH #21601 <https://github.com/Perl/perl5/issues/21601>]
π Performance Enhancements π
- the negation OPs have been modified to support the generic
TARGMYoptimization. faster is faster, we love efficiency π [GH #21442 <https://github.com/Perl/perl5/issues/21442>]
πΈ MODULES AND PRAGMATA πΈ
bestie this is the part where we go through every single module that got added or glow-up'd in this release. it's giving inventory, it's giving receipts, and yes we are listing all of them π
β¨ New Modules and Pragmata β¨
Term::Table0.018 β brand new in the core, bestie π- it's a dependency of
Test2::Suite, that's the whole reason it's here.
- it's a dependency of
Test2::Suite0.000162 β also brand new in the core β¨- this distribution is a whole comprehensive set of test tools for writing unit tests.
- it's the successor to
Test::Moreand similar modules. - the reason it's in core now: CPAN module tests can be written using this suite of tools without extra dependencies. no cap. π
π Updated Modules and Pragmata π
okay so here's the big list. everything below got a version bump, and a few of them got actual lore too π§
Archive::Tarβ upgraded from version2.40to3.02_001.attributesβ upgraded from version0.35to0.36.autodieβ upgraded from version2.36to2.37.Bβ upgraded from version1.88to1.89.B::Deparseβ upgraded from version1.74to1.76.Benchmarkβ upgraded from version1.24to1.25.bignumβ upgraded from version0.66to0.67.builtinβ upgraded from version0.008to0.014. this one ATE π₯builtinnow accepts a version bundle as an input argument, which requests that it import all of the functions that are considered a stable part of the module at the given Perl version. like, for example:
use builtin ':5.40';
- added the
load_module()builtin function as per PPC 0006 βhttps://github.com/Perl/PPCs/blob/main/ppcs/ppc0006-load-module.md.
bytesβ upgraded from version1.08to1.09.Compress::Raw::Bzip2β upgraded from version2.204_001to2.212.Compress::Raw::Zlibβ upgraded from version2.204_001to2.212.CPAN::Meta::Requirementsβ upgraded from version2.140to2.143.Data::Dumperβ upgraded from version2.188to2.189.DB_Fileβ upgraded from version1.858to1.859.Devel::Peekβ upgraded from version1.33to1.34.Devel::PPPortβ upgraded from version3.71to3.72.diagnosticsβ upgraded from version1.39to1.40.DynaLoaderβ upgraded from version1.54to1.56.Encodeβ upgraded from version3.19to3.21.Errnoβ upgraded from version1.37to1.38.- the
osversandarchnamebaked into the module (the ones that make sureErrnogets loaded by the perl that built it) are now more comprehensively escaped. π«ΆGH #21135βhttps://github.com/Perl/perl5/issues/21135
- the
experimentalβ upgraded from version0.031to0.032.Exporterβ upgraded from version5.77to5.78.ExtUtils::CBuilderβ upgraded from version0.280238to0.280240.ExtUtils::Manifestβ upgraded from version1.73to1.75.ExtUtils::Miniperlβ upgraded from version1.13to1.14.Fcntlβ upgraded from version1.15to1.18.- the old module documentation stub has been greatly expanded and revised. π
- adds support for the
O_TMPFILEflag on Linux.
featureβ upgraded from version1.82to1.89.- it now documents the
:allfeature bundle, and it also suggests a reason why you may not wish to use it. π
- it now documents the
fieldsβ upgraded from version2.24to2.25.File::Compareβ upgraded from version1.1007to1.1008.File::Findβ upgraded from version1.43to1.44.File::Globβ upgraded from version1.40to1.42.File::Specβ upgraded from version3.89to3.90.File::statβ upgraded from version1.13to1.14.FindBinβ upgraded from version1.53to1.54.Getopt::Longβ upgraded from version2.54to2.57.Getopt::Stdβ upgraded from version1.13to1.14.- documentation and test improvements only; no change in functionality. it's giving glow-up with zero plot twists π
Hash::Utilβ upgraded from version0.30to0.32.Hash::Util::FieldHashβ upgraded from version1.26to1.27.HTTP::Tinyβ upgraded from version0.086to0.088.I18N::Langinfoβ upgraded from version0.22to0.24.- it now handles the additional locale categories that Linux defines beyond those in the POSIX Standard.
- this fixes what is returned for the
ALT_DIGITSitem, which has never before worked properly in Perl. literal historic moment π
IOβ upgraded from version1.52to1.55.- fixed
IO::Handle/blockingon Windows, which has been non-functional since IO1.32.GH #17455βhttps://github.com/Perl/perl5/issues/17455
- fixed
IO-Compressβ upgraded from version2.204to2.212.IO::Socket::IPβ upgraded from version0.41_01to0.42.IO::Zlibβ upgraded from version1.14to1.15.localeβ upgraded from version1.10to1.12.Math::BigIntβ upgraded from version1.999837to2.003002.Math::BigInt::FastCalcβ upgraded from version0.5013to0.5018.Module::CoreListβ upgraded from version5.20230520to5.20240609.Module::Metadataβ upgraded from version1.000037to1.000038.mroβ upgraded from version1.28to1.29.NDBM_Fileβ upgraded from version1.16to1.17.Opcodeβ upgraded from version1.64to1.65.perl5db.plβ upgraded from version1.77to1.78.- made parsing of the
lcommand arguments saner.GH #21350βhttps://github.com/Perl/perl5/issues/21350
- made parsing of the
perlfaqβ upgraded from version5.20210520to5.20240218.PerlIO::encodingβ upgraded from version0.30to0.31.PerlIO::scalarβ upgraded from version0.31to0.32.PerlIO::viaβ upgraded from version0.18to0.19.Pod::Checkerβ upgraded from version1.75to1.77.Pod::Htmlβ upgraded from version1.34to1.35.Pod::Simpleβ upgraded from version3.43to3.45.podlatorsβ upgraded from version5.01to5.01_02.POSIXβ upgraded from version2.13to2.20. this one has a whole saga, bestie π- the
mktimefunction now works correctly on 32-bit platforms even if the platform'stime_ttype is larger than 32 bits.GH #21551βhttps://github.com/Perl/perl5/issues/21551 - the
T_SIGNOandT_FDtypemap entries have been fixed so they work with any variable name, rather than just the hardcodedsigandfd. - the mappings for
Mode_t,pid_t,Uid_t,Gid_tandTime_thave been updated to be integer types; previously they wereNVfloating-point. - adjusted the
signbit()on NaN test to handle the unusual bit pattern returned for NaN by Oracle Developer Studio's compiler.GH #21533βhttps://github.com/Perl/perl5/issues/21533
- the
reβ upgraded from version0.44to0.47.Safeβ upgraded from version2.44to2.46.SelfLoaderβ upgraded from version1.26to1.27.Socketβ upgraded from version2.036to2.038.strictβ upgraded from version1.12to1.13.Test::Harnessβ upgraded from version3.44to3.48.Test::Simpleβ upgraded from version1.302194to1.302199.Text::Tabsβ upgraded from version2021.0814to2024.001.Text::Wrapβ upgraded from version2021.0814to2024.001.threadsβ upgraded from version2.36to2.40.- an internal error has been made slightly more verbose:
Out of memory in perl:threads:ithread_create. π at least now you know what ran out of memory.
- an internal error has been made slightly more verbose:
threads::sharedβ upgraded from version1.68to1.69.Tie::Fileβ upgraded from version1.07to1.09.- old compatibility code for perl 5.005 that was no longer functional has been removed. bye boo π
Time::gmtimeβ upgraded from version1.04to1.05.Time::HiResβ upgraded from version1.9775to1.9777.Time::Localβ upgraded from version1.30to1.35.Time::localtimeβ upgraded from version1.03to1.04.Time::tmβ upgraded from version1.00to1.01.UNIVERSALβ upgraded from version1.15to1.17.User::grentβ upgraded from version1.04to1.05.User::pwentβ upgraded from version1.02to1.03.versionβ upgraded from version0.9929to0.9930.warningsβ upgraded from version1.65to1.69.XS::APItestβ upgraded from version1.32to1.36.XS::Typemapβ upgraded from version0.19to0.20.
π Documentation
β¨ Changes to Existing Documentation β¨
okay so bestie, the whole team tried to make the docs match everything listed in this doc, and if you spot something they missed you can open an issue at https://github.com/Perl/perl5/issues. π
And also, these specific glow-ups happened:
perlapi- Fixed the docs for
Perl_form,form_nocontext, andvform, which used to claim that any later call to one of them will destroy the previous returns from any. That has not been true since5.6.0β except it does still remain true if these are called during global destruction. With that caveat, the return of each of these is a fresh string in a temporary that will automatically be freed by a call to"FREETMPS"in perlapi, or at places such as statement boundaries. - Several internal functions now have docs β the various
newSUBfunctions,newANONLIST(),newANONHASH(),newSVREF()and similar. π
- Fixed the docs for
perlclass- Added a list of known bugs in the experimental
classfeature. (yes, we're being honest about them, iconic behaviour)
- Added a list of known bugs in the experimental
perlfunc- The docs for
local,my,our, andstategot updated to include examples and descriptions of their effects within a statement.
- The docs for
perlguts- A whole new section describing the experimental reference-counted argument stack build option (
PERL_RC_STACK).
- A whole new section describing the experimental reference-counted argument stack build option (
perlclib- Extensive guidance for interfacing with the standard C library, including many more functions to avoid, plus how to cope with locales and threads. π¦
perlhacktips- Documented that we can't use compound literals or array designators due to C++ compatibility.
[GH #21073 <https://github.com/Perl/perl5/issues/21073>] - Documented new functions
sv_mark_arenas()andsv_sweep_arenas()(which only exist onDEBUGGINGbuilds). - Added brief docs for some tools useful when developing perl itself on Windows or Cygwin.
- Documented that we can't use compound literals or array designators due to C++ compatibility.
perllol- Removed indirect object syntax in the
Dumpvalueexample.
- Removed indirect object syntax in the
perlre- Removed the statement suggesting
/pis a no-op.
- Removed the statement suggesting
perlref- Documented ref assignment in list context (as part of the
refaliasingfeature).
- Documented ref assignment in list context (as part of the
perlop- The section on the empty pattern
//got amended to mention that the current dynamic scope is used to find the last successful match.
- The section on the empty pattern
perlport- The
-Sfile test has been meaningful on Win32 since5.37.6. - The
-lfile test is now meaningful on Win32. - Some strange behaviour with
.at the end of names under Windows has been documented.
- The
perlvar- Added documentation for an alternative to
${^CAPTURE}.
- Added documentation for an alternative to
π¨ Diagnostics π¨
These are the additions and changes to diagnostic output, including warnings and fatal error messages. For the complete list of diagnostic messages, see perldiag.
π₯ New Diagnostics π₯
New Errors
Cannot use __CLASS__ outside of a method or field initializer expression(F) A__CLASS__expression yields the class name of the object instance executing the current method, and therefore it can only be placed inside an actual method (or method-like expression, such as a field initializer expression).get_layers: unknown argument '%s'(F) You calledPerlIO::get_layers()with an unknown argument. Legal arguments are provided in key/value pairs, with the keys being one ofinput,outputordetail, followed by a boolean.UNIVERSAL does not export anything(F) You asked UNIVERSAL to export something, but UNIVERSAL is the base class for all classes and contains no exportable symbols. (like babe, there's literally nothing to hand out π)Builtin version bundle "%s" is not supported by Perl(F) You attempted touse builtin :verfor a version number that is either older than5.39(when the ability was added), or newer than the current perl version.Invalid version bundle "%s"(F) A version number that is used to specify an import bundle during ause builtin ...statement must be formatted as:MAJOR.MINORwith an optional third component, which is ignored. Each component must be a number of 1 to 3 digits. No other characters are permitted. The value that was specified does not conform to these rules.Missing comma after first argument to return(F) While certain operators allow you to specify a filehandle or an "indirect object" before the argument list,returnisn't one of them.Out of memory during vec in lvalue context(F) An attempt was made to extend a string beyond the largest possible memory allocation by assigning tovec()called with a large second argument.
(This case used to throw a generic Out of memory! error.)
Cannot create an object of incomplete class "%s"(F) An attempt was made to create an object of a class where the start of the class definition has been seen, but the class has not been completed.
This can happen for a failed eval, or if you attempt to create an object at compile time before the class is complete:
eval "class Foo {"; Foo->new; # error
class Bar { BEGIN { Bar->new } }; # error
Previously perl would assert or crash. [GH #22159 <https://github.com/Perl/perl5/issues/22159>]
New Warnings
Forked open '%s' not meaningful in <>(S inplace) You had|-or-|in@ARGVand tried to use<>to read from it.
Previously this would fork and produce a confusing error message. [GH #21176 <https://github.com/Perl/perl5/issues/21176>]
Attempt to call undefined %s method with arguments ("%s"%s) via package "%s" (Perhaps you forgot to load the package?)(D deprecated::missing_import_called_with_args) You called theimport()orunimport()method of a class that has no import method defined in its inheritance graph, and passed an argument to the method. This is very often the sign of a misspelled package name in auseorrequirestatement that has silently succeeded due to a case insensitive file system.
Another common reason this may happen is when mistakenly attempting to import or unimport a symbol from a class definition or package which does not use Exporter or otherwise define its own import or unimport method.
π§ Changes to Existing Diagnostics π§
Name "%s::%s" used only once: possible typo
This warning now honors being marked as fatal. [GH #13814 <https://github.com/Perl/perl5/issues/13814>]
Out of memory in perl:%s
There used to be several places in the perl core that would print a generic Out of memory! message and abort when memory allocation failed, giving no indication which program it was that ran out of memory. These have been modified to include the word perl and the general area of the allocation failure, e.g. Out of memory in perl:util:safesysrealloc. [GH #21672 <https://github.com/Perl/perl5/issues/21672>]
Possible precedence issue with control flow operator (%s)
This warning now mentions the name of the control flow operator that triggered the diagnostic (e.g. return, exit, die, etc).
It also covers more cases: Previously, the warning was only triggered if a low-precedence logical operator (like and, or, xor) was involved. Now it is also shown for misleading code like this:
exit $x ? 0 : 1; # actually parses as: exit($x) ? 0 : 1;
exit $x == 0; # actually parses as: exit($x) == 0;
Use of uninitialized value%s
This warning is now slightly more accurate in cases involving length, pop, shift, or splice:
my $x;
length($x) == 0
# Before:
# Use of uninitialized value $x in numeric eq (==) at ...
# Now:
# Use of uninitialized value length($x) in numeric eq (==) at ...
That is, the warning no longer implies that $x was used directly as an operand of ==, which it wasn't.
Similarly:
my @xs;
shift @xs == 0
# Before:
# Use of uninitialized value within @xs in numeric eq (==) at ...
# Now:
# Use of uninitialized value shift(@xs) in numeric eq (==) at ...
This is more accurate because there never was an undef within @xs as the warning implied. (The warning for pop works analogously.)
Finally:
my @xs = (1, 2, 3);
splice(@xs, 0, 0) == 0
# Before:
# Use of uninitialized value within @xs in numeric eq (==) at ...
# Now:
# Use of uninitialized value in numeric eq (==) at ...
That is, in cases where splice returns undef, it no longer unconditionally blames its first argument. This was misleading because splice can return undef even if none of its arguments contain undef.
[GH #21930 <https://github.com/Perl/perl5/issues/21930>]
Old package separator "'" deprecated
Prevent this warning appearing spuriously when checking the heuristic for the You need to quote "%s" warning.
[GH #22145 <https://github.com/Perl/perl5/issues/22145>]
π οΈ Configuration and Compilation π οΈ
microperl, long broken and of unclear present purpose, has been removed as promised in Perl 5.18. (rip bestie, you were promised this ages ago π«Ά)- Fix here-doc used for code to probe
LC_ALLsyntax for disparate locales introduced in5.39.2.[GH #21451 <https://github.com/Perl/perl5/issues/21451>] - You can now separately enable high water mark checks for non-DEBUGGING or disable them for DEBUGGING builds with
-Accflags=-DPERL_USE_HWMor-Accflags=-DPERL_NO_HWMrespectively. The default remains the same.[GH #16607 <https://github.com/Perl/perl5/issues/16607>]
π§ͺ TESTING π§ͺ
bestie, the test suite got a whole glow-up this release. tests were added and changed to reflect all the other additions and changes, and on top of that, these significant changes happened:
- Update nm output parsing for Darwin in
t/porting/libperl.tto handle changes in the output of nm on Darwin. [GH #21117 <https://github.com/Perl/perl5/issues/21117>] t/op/magic.twould fail whenpswas the BusyBox implementation, since that doesn't support the-pflag and otherwise ignores a process id on the command-line. This caused TEST failures on BusyBox systems such as Alpine Linux. [GH #17542 <https://github.com/Perl/perl5/issues/17542>]porting/globvar.tnow uses the more portablenm -P ...to fetch the names defined in an object file. The parsing of the names found in the object is now separated from processing them to handle the duplication between local and global definitions on AIX. [GH #21637 <https://github.com/Perl/perl5/issues/21637>]- A test was added to
lib/locale_threads.tthat extensively stress tests locale handling. It turns out that the libc implementations on various platforms have bugs in this regard, including Linux, Windows, *BSD derivatives including Darwin, and others. Experimental versions of this test have been used in the past few years to find bugs in the Perl implementation and in those platforms, as well as to develop workarounds in the Perl implementation, where feasible, for the platform bugs. Multiple bug report tickets have been filed against platforms, and some have been fixed. The test checks that platforms that purport to support thread-safe locale handling actually do so (and that perl works properly on those that do; The read-only variable${^SAFE_LOCALES}is set to 1 if perl thinks the platform can handle this, whatever the platform's documentation says).
Also tested for is if the various locale categories can indeed be set independently to disparate locales. (An example of where you might want to do this is if you are a Western Canadian living and working in Holland. You likely will want to have the LC_MONETARY locale be set to where you are living, but have the other parts of your locale retain your native English values. Later, as you get a bit more comfortable with Dutch, and in order to communicate better with your colleagues, you might want to change LC_TIME and LC_NUMERIC to Dutch, while leaving LC_CTYPE and LC_COLLATE set to English indefinitely.)
- The test
t/porting/libperl.twill no longer run in maint releases. This test is sensitive to changes in the output of nm on various platforms, and tarballs aren't updated as we update this test in blead. [GH #21677 <https://github.com/Perl/perl5/issues/21677>]
π PLATFORM SUPPORT π
β¨ New Platforms β¨
- Serenity OS β Out of the box support for Serenity OS was added. she's new here and she's thriving π¦
π οΈ Platform-Specific Notes π οΈ
Windows
- Eliminated several header build warnings under MSVC with
/W4to reduce noise for embedders. [GH #21031 <https://github.com/Perl/perl5/issues/21031>] - Work around a bug in most 32-bit Mingw builds, where the generated code, including the code in the gcc support library, assumes 16-byte stack alignment, which 32-bit Windows does not preserve. [GH #21313 <https://github.com/Perl/perl5/issues/21313>]
- Enable
copysign,signbit,acosh,asinh,atanh,exp2,tgammain the bundled configuration used for MSVC. [GH #21610 <https://github.com/Perl/perl5/issues/21610>] - The build process no longer supports Visual Studio 2013. This was failing to build at a very basic level and there have been no reports of such failures. [GH #21624 <https://github.com/Perl/perl5/issues/21624>]
heads up bestie: Visual Studio 2013 is out. she's not coming to the build party anymore. π
Linux
- The hints file has been updated to handle the Intel oneAPI DPC++/C++ compiler.
MacOS/Darwin
- Don't set
MACOSX_DEPLOYMENT_TARGETwhen building on OS X 10.5. [GH #21367 <https://github.com/Perl/perl5/issues/21367>]
VMS
- Fixed the configure "installation prefix" prompt to accept a string rather than yes/no.
- Fixed compilation by defining proper value for
perl_lc_all_category_positions_init. - Increased buffer size when reading config_H.SH to fix compilation under clang.
Oracle Developer Studio (Solaris, Oracle Linux)
- Due to an apparent code generation bug, the default optimization level for the Oracle Developer Studio (formerly Sun Workshop) compiler is now
-xO1. [GH #21535 <https://github.com/Perl/perl5/issues/21535>]
π§ INTERNAL CHANGES π§
PERL_RC_STACKbuild option added.
This new build option is highly experimental and is not enabled by default. Perl can be built with it by using the Configure option -Accflags='-DPERL_RC_STACK'.
It makes the argument stack bump the reference count of SVs pushed onto it. It is mostly functional, but currently slow and incomplete.
It is intended in the long term that this build option will become the default option, and then finally the only option; but this will be many releases away.
In particular, there is currently no support within XS code for using these new features. So under this build option, all XS functions are called via a backwards-compatibility wrapper which slows down such calls.
In future releases, better support for XS code is intended to be added. It is expected that straightforward XS code will eventually be able to make use of a reference-counted stack without modification, with any heavy lifting being handled by the XS compiler (xsubpp) and the macros which it outputs. But code which implements PP() functions will eventually have to be modified to use a new PP API: rpp_foo() rather than PUSHs() etc. But this new API is not yet stable, nor has it yet been back-ported via Devel::PPPort.
See perlguts for more details.
- A new API function has been added that simplifies C (or XS) code that creates
LISTOPoptree fragments.newLISTOPn()is a variadic function that takes aNULL-terminated list of child op pointers, and constructs a new checkedLISTOPto contain them all. This is simpler than creating a new plainOP_LIST, adding each child individually, and finally callingop_convert_list()in most code fragments. iconic API behaviour, honestly β¨ - The
eval_sv()API now accepts theG_USEHINTSflag, which uses the hints such as strict and features fromPL_curcopinstead of the default, which is to use default hints, e.g. nouse vX.XX;, no strict, default features.
Beware if you use this flag in XS code: your evaluated code will need to support whatever strictness or features are in effect at the point your XS function is called.
[GH #21415 <https://github.com/Perl/perl5/issues/21415>]
PERL_VERSION_LEhas been fixed to properly check for "less than or equal" rather than "less than". πdAX,dITEMSand hencedXSARGSnow declareAXanditemsasStack_off_trather thanSSize_t. This reverts back to compatibility with pre-64-bit stack support for default builds of perl whereStack_off_tisI32. [GH #21782 <https://github.com/Perl/perl5/issues/21782>]- A new function is now available to
XScode,sv_langinfoin perlapi. This provides the same information as the existingPerl_langinfo8in perlapi, but returns an SV instead of achar *, so that programmers don't have to concern themselves with the UTF-8ness of the result. This new function is now the preferred interface forXScode to the nl_langinfo(3)libcfunction. From Perl space, this information continues to be provided by the I18N::Langinfo module. π - glibc has an undocumented equivalent function to querylocale(), which our experience indicates is reliable. When this is function is used, it removes the need for perl to keep its own records, hence is more efficient and guaranteed to be accurate. Use of this function can be disabled by defining the
NO_NL_LOCALE_NAMEbuild option
β¨ Selected Bug Fixes β¨
okay bestie, sit down, hydrate, this is the big long list of "we fixed the thing" and honestly? it ate π
- The delimiter pair
SYRIAC COLON SKEWED LEFT/RIGHTgot removed from the ones that theextra_paired_delimitersfeature recognizes. (go peep "Quote and Quote-like Operators" in perlop for the full lore.) Why? Because those characters are normally written right-to-left, and that could be visually confusing, no cap [GH #22228 <https://github.com/Perl/perl5/issues/22228>]. The change was actually to forbid any right-to-left delimiters, but this pair is literally the only current instance that meets that criterion. And by policy, this means theextra_paired_delimitersfeature cannot be considered to have been stable long enough for its experimental status to be removed. the drama π use 5.36;or later didn't enable the post parse reporting ofName "%s::%s" used only once: possible typowarnings when enabling warnings. [GH #21271 <https://github.com/Perl/perl5/issues/21271>]- Fixed a crash or assertion when cleaning up a closure that refers to an outside
oursub. [GH #21067 <https://github.com/Perl/perl5/issues/21067>] - Fixed a number of issues where
I32was used as a string offset or size rather thanSSize_torSTRLEN/size_t[GH #21012 <https://github.com/Perl/perl5/issues/21012>] ~$strwhen$strwas more than 2GB in size would do nothing or produce an incomplete result. nothing?? embarrassing.- String repeat,
$str x $count, didn't handle$strover 2GB in size, throwing an error. Now such strings are repeated. π - Complex substitution after the 2GB point in a string could access incorrect or invalid offsets in the string.
sv_utf8_decode()would truncate the SV'spos()value. This wasn't visible viautf8::decode().- When compiling a constant folded hash key, the length was truncated when creating the shared SV. Since hash keys over 2GB are not supported, throw a compilation error instead.
msgrcv()incorrectly called get magic on the buffer SV and failed to call set magic on completion. [GH #21012 <https://github.com/Perl/perl5/issues/21012>]msgrcv()used the size parameter to resize the buffer before validating it. [GH #21012 <https://github.com/Perl/perl5/issues/21012>]- Inheriting from a class that was hierarchically an ancestor of the new class, eg.
class A::B :isa(A) { ... }, would not attempt to load the parent class. [GH #21332 <https://github.com/Perl/perl5/issues/21332>] - Declared references can now be used with
statevariables. slay [GH #21351 <https://github.com/Perl/perl5/issues/21351>] - Trailing elements in an
unshifted and resized array will now always be initialized. [GH #21265 <https://github.com/Perl/perl5/issues/21265>] - Make
use 5.036respect the -X flag
perl's -X flag disables all warnings globally, but Β«use 5.036Β» didn't respect that until now. [GH #21431 <https://github.com/Perl/perl5/issues/21431>]
- Fixed an OP leak when an error was produced for initializer for a class field. [GH #20812 <https://github.com/Perl/perl5/issues/20812>]
- Fixed a leak of the return value when smartmatching against a code reference.
- Fixed a slowdown in repeated substitution replacements using special variables, such as
s/....x$1/g. It actually makes all string concatenations involving such "magic" variables less slow, but the slowdown was more noticeable on repeated substitutions due to extra memory usage that was only freed after the last iteration. The slowdown started in perl 5.28.0 - which generally sped up string concatenation but slowed down when using special variables. [GH #21360 <https://github.com/Perl/perl5/issues/21360>] - Lexical names from the enclosing scope in a lexical sub or closure weren't visible to code executed by calling
eval EXPR;from theDBpackage. This was introduced in 5.18 in an attempt to prevent subs from retaining a reference to their outer scope, but this broke the special behaviour ofeval EXPR;in package DB.
This incidentally fixed a TODO test for B::Deparse. [GH #19370 <https://github.com/Perl/perl5/pull/19370>]
- Optionally support an argument stack over 2**32 entries on 64-bit platforms. This requires 32GB of memory just for the argument stack pointers itself, so you will require a significantly more memory to take advantage of this. 32GB just for pointers bestie π«
To enable this add -Accflags=-DPERL_STACK_OFFSET_SSIZET or equivalent to the Configure command-line.
[GH #20917 <https://github.com/Perl/perl5/issues/20917>] [GH #21523 <https://github.com/Perl/perl5/issues/21523>]
- Fixed various problems with
join()where modifications to the separator could be handled inconsistently, or could access released memory. Changes to the separator from magic or overloading for values in theLISTno longer have an effect on the resulting joined string. [GH #21458 <https://github.com/Perl/perl5/issues/21458>] - Don't clear the integer flag
IOKfrom lines in the@{"_<$sourcefile"}array when adbstateop is removed for that line. This was broken when fixing [GH #19198 <https://github.com/Perl/perl5/issues/19198>]. [GH #21564 <https://github.com/Perl/perl5/issues/21564>] - Many bug fixes have been made for using locales under threads and in embedded perls. And workarounds for libc bugs have been added. As a result thread-safe locale handling is now the default under OpenBSD, and MingW when compiled with UCRT.
However, testing has shown that Darwin's implementation of thread-safe locale handling has bugs. So now Perl doesn't attempt to use the thread-safe operations when compiled on Darwin.
As before, you can check to see if your program is running with thread-safe locales by checking if the value of ${^SAFE_LOCALES} is 1.
- Various bugs have been fixed when perl is configured with
-Accflags=-DNO_LOCALE_NUMERICor any other locale category (or categories). - Not all locale categories need be set to the same locale. Perl now works around bugs in the libc implementations of locale handling on some platforms that previously could result in mojibake. mojibake jumpscare π
LC_ALLis represented in one of two ways when not all locale categories are set to the same locale. On some platforms, such as Linux and Windows, the representation is of the form of a series of 'category=locale-name' pairs. On other platforms, such as *BSD, the representation is positional likename1 / name2 / .... name1 is always for a particular category as defined by the platform, as are the other names. The sequence that separates the names (the " / " above) also varies by platform. Previously, perl had problems with platforms that used the positional notation. This is now fixed.- A bug has been fixed in the regexp engine with an optimisation that applies to the
+quantifier where it was followed by a(*SKIP)pattern.
[GH #21534 <https://github.com/Perl/perl5/issues/21534>]
- The tmps (mortal) stack now grows exponentially. Previously it grew linearly, so if it was growing incrementally, such as through many calls to
sv_2mortal(), on a system whererealloc()is O(size), the performance would be O(n*n). With exponential grows this changes to amortized O(n). [GH #21654 <https://github.com/Perl/perl5/issues/21654>] - Lexical subs now have a new stub in the pad for each recursive call into the containing function. This fixes two problems:
- If the lexical sub called the containing function, a
Can't undef active subroutineerror would be thrown. For example:
- If the lexical sub called the containing function, a
use v5.36.0;
sub outer($oc) {
my sub inner ($c) {
outer($c-1) if $c; # Can't undef active subroutine
}
inner($oc);
}
outer(2);
[GH #18606 <https://github.com/Perl/perl5/issues/18606>]
- If the lexical sub was called from a recursive call into the containing function, this would overwrite the bindings to the closed over variables in the lexical sub, so calls into the lexical sub from the outer recursive call would have access to the variables from the inner recursive call:
use v5.36.0;
sub outer ($x) {
my sub inner ($label) {
say "$label $x";
}
inner("first");
outer("inner") if $x eq "outer";
# this call to inner() sees the wrong $x
inner("second");
}
outer("outer");
[GH #21987 <https://github.com/Perl/perl5/issues/21987>]
prepare_export_lexical()was separately savingPL_comppadandPL_curpad, this could result inPL_curpadbeing restored to a no longer valid value, resulting in a panic when importing lexicals in some cases. [GH #21981 <https://github.com/Perl/perl5/issues/21981>]- A string
eval()operation in the scope of ause VERSIONdeclaration would sometimes emit spuriousDowngrading a use VERSION declarationwarnings due to an inconsistency in the way the version number was stored. This is now fixed. [GH #22121 <https://github.com/Perl/perl5/issues/22121>]
πΈ Known Problems πΈ
- perlivp is missing streamzip on Windows
The streamzip utility does not get installed on Windows but should get installed.
π¦ Errata From Previous Releases π¦
- perl5300delta has been updated to include the removal of the
arybasemodule that happened at the same time as the removal of$[.
π ACKNOWLEDGEMENTS π
okay bestie, this is the part where we give credit where credit is so due, because none of this happened by magic π«
Perl 5.40.0 represents approximately 11 months of development since Perl 5.38.0 and contains approximately 160,000 lines of changes across 1,500 files from 75 authors. not me getting emotional over a version number π
Excluding auto-generated files, documentation and release tools, there were approximately 110,000 lines of changes to 1,200 .pm, .t, .c and .h files. the way that's a whole city of code fr fr ποΈ
Perl continues to flourish into its fourth decade thanks to a vibrant community of users and developers. The following people are known to have contributed the improvements that became Perl 5.40.0:
Abe Timmerman, Alexander Kanavin, Amory Meltzer, Aristotle Pagaltzis, Arne Johannessen, Beckett Normington, Bernard Quatermass, Bernd, Bruno Meneguele, Chad Granum, Chris 'BinGOs' Williams, Christoph Lamprecht, Craig A. Berry, Dagfinn Ilmari MannsΓ₯ker, Dan Book, Dan Church, Daniel BΓΆhmer, Dan Jacobson, Dan Kogai, David Golden, David Mitchell, E. Choroba, Elvin Aslanov, Erik Huelsmann, Eugen Konkov, Gianni Ceccarelli, Graham Knop, Greg Kennedy, guoguangwu, Hauke D, H.Merijn Brand, Hugo van der Sanden, iabyn, Jake Hamby, Jakub Wilk, James E Keenan, James Raspass, Joe McMahon, Johan Vromans, John Karr, Karen Etheridge, Karl Williamson, Leon Timmermans, Lukas Mai, Marco Fontani, Marek Rouchal, Martijn Lievaart, Mathias Kende, Matthew Horsfall, Max Maischein, Nicolas Mendoza, Nicolas R, OpossumPetya, Paul Evans, Paul Marquess, Peter John Acklam, Philippe Bruhat (BooK), Raul E Rangel, Renee Baecker, Ricardo Signes, Richard Leach, Scott Baker, Sevan Janiyan, Sisyphus, Steve Hay, TAKAI Kousuke, Todd Rinaldo, Tomasz Konojacki, Tom Hughes, Tony Cook, William Lyu, x-yuri, Yves Orton, Zakariyya Mughal, ΠΠΈΠ»ΡΠ½ ΠΠ°Π»Π°ΡΠ·ΠΎΠ².
π every single one of y'all, iconic.
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.
so if you filed a bug and you're not on the list β we see you, we appreciate you, you're valid π«Ά the script just can't read the bug tracker's mind.
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.
π REPORTING BUGS π
If you find what you think is a bug, you might check the perl bug database at https://github.com/Perl/perl5/issues. There may also be information at https://www.perl.org/, the Perl Home Page. π
If you believe you have an unreported bug, please open an issue at https://github.com/Perl/perl5/issues. Be sure to trim your bug down to a tiny but sufficient test case β yes, the tiny part matters, bestie, nobody can debug your entire 4,000-line app π
If the bug you are reporting has security implications which make it inappropriate to send to a public issue tracker, then see "SECURITY VULNERABILITY CONTACT INFORMATION" in perlsec for details of how to report the issue. do not drop a zero-day in a public issue, please and thank you π
π«Ά GIVE THANKS π«Ά
If you wish to thank the Perl 5 Porters for the work we had done in Perl 5, you can do so by running the perlthanks program:
perlthanks
This will send an email to the Perl 5 Porters list with your show of thanks. π genuinely the nicest thing you can do for a maintainer, no cap.
π SEE ALSO π
- The
Changesfile for an explanation of how to view exhaustive details on what changed. - The
INSTALLfile for how to build Perl. - The
READMEfile for general stuff. - The
ArtisticandCopyingfiles for copyright information.
and that's a wrap on the whole page, bestie π this lore came straight from perl v5.42.3, dated 2026-08-03 β go forth and perlthanks somebody, they deserve it π
β¨
π¦ where this page comes from
- fedora 43: perl-doc 5.42.3-524.fc43 Β· (GPL-1.0-or-later OR Artistic-1.0-Perl) AND Unicode-3.0 AND LicenseRef-Fedora-UltraPermissive
- fedora 44: perl-doc 5.42.3-525.fc44 Β· (GPL-1.0-or-later OR Artistic-1.0-Perl) AND Unicode-3.0 AND LicenseRef-Fedora-UltraPermissive
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms