perldelta - what is new for perl v5.40.1
This document describes differences between the 5.40.0 release and the 5.40.1 release.
If you are upgrading from an earlier release such as 5.39.0, first read perl5400delta, which describes differences between 5.39.0 and 5.40.0.
There are no changes intentionally incompatible with 5.40.0. If any exist, they are bugs, and we request that you submit a report. See "Reporting Bugs" below.
File::Spec has been upgraded from version 3.90 to 3.91.
Module::CoreList has been upgraded from version 5.20240609 to 5.20250118_40.
warnings has been upgraded from version 1.69 to 1.70.
We have attempted to update the documentation to reflect the changes listed in this document. If you find any we have missed, open an issue at https://github.com/Perl/perl5/issues.
Fixed compilation on platforms (e.g. "Gentoo Prefix") with only a C locale. [GH #22569] Bug first reported downstream at bugs.gentoo.org/939014.
Fixed compilation error on some systems due to a typo in a printf() format. [GH #22793]
Tests were added and changed to reflect the other additions and changes in this release.
Starting in Perl 5.39.8, "strftime" in POSIX would crash or produce odd errors (such as Out of memory in perl:util:safesysmalloc) when given a format string that wasn't actually a string, but a number, undef, or an object (even one with overloaded string conversion).
Now strftime stringifies its first argument, as before. [GH #22498]
Builds with -msse and quadmath on 32-bit x86 systems would crash with a misaligned access early in the build. [GH #22577]
Using goto to tail call, or using the call_sv() and related APIs to call, any of trim(), refaddr(), reftype(), ceil(), floor() or stringify() in the builtin:: package would crash or assert due to a TARG handling bug. [GH #22542]
Fixed an issue where `utf8n_to_uvchr` failed to correctly identify certain invalid UTF-8 sequences as invalid. Specifically, sequences that start with continuation bytes or unassigned bytes could cause unexpected behaviour or a panic. This fix ensures that such invalid sequences are now properly detected and handled. This correction also resolves related issues in modules that handle UTF-8 processing, such as `Encode.pm`.
Fixed a double free error or possible memory leak when failing to compile certain regexps. [GH #21661]
Perl 5.40.1 represents approximately 7 months of development since Perl 5.40.0 and contains approximately 5,600 lines of changes across 54 files from 15 authors.
Excluding auto-generated files, documentation and release tools, there were approximately 1,800 lines of changes to 19 .pm, .t, .c and .h files.
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.1:
Andrei Horodniceanu, Chris 'BinGOs' Williams, E. Choroba, Graham Knop, James E Keenan, Karen Etheridge, Karl Williamson, Lukas Mai, Masahiro Honma, Max Maischein, Philippe Bruhat (BooK), Richard Leach, Steve Hay, Thibault Duponchelle, Tony Cook.
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 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.
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.
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:
perlthanksThis will send an email to the Perl 5 Porters list with your show of thanks.
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.