perldelta - what is new for perl v5.43.1
This document describes differences between the 5.43.0 release and the 5.43.1 release.
If you are upgrading from an earlier release such as 5.42.0, first read perl5430delta, which describes differences between 5.42.0 and 5.43.0.
experimental has been upgraded from version 0.035 to 0.036.
ExtUtils::ParseXS has been upgraded from version 3.57 to 3.58.
ExtUtils::Typemaps has been upgraded from version 3.57 to 3.58.
File::Fetch has been upgraded from version 1.04 to 1.08.
Module::CoreList has been upgraded from version 5.20250703 to 5.20250720.
PerlIO::via has been upgraded from version 0.19 to 0.20.
Pod::Simple has been upgraded from version 3.45 to 3.47.
Socket has been upgraded from version 2.038 to 2.040.
Test::Harness has been upgraded from version 3.50 to 3.52.
Test::Simple has been upgraded from version 1.302210 to 1.302214.
Unicode::UCD has been upgraded from version 0.81 to 0.82.
The following additions or changes have been made to diagnostic output, including warnings and fatal error messages. For the complete list of diagnostic messages, see perldiag.
This warning was issued in the reverse order (right-to-left) when both operands of a binary operator are uninitialized values. This is now fixed to be consistent with evaluation order of operands.
The XS parser, ExtUtils::ParseXS, has been extensively restructured internally. Most of these changes shouldn't be visible externally, but might affect XS code which was using invalid or unsupported syntax.
When both operands of arithmetic operators (+, -, etc.) are overloaded objects which have no method for that operator but have a 0+ method and the fallback option set to TRUE, perl will normally call the 0+ method for the left operand first and then call one for the right operand, i.e. in the same order with operand evaluation order. But if use integer; is in effect, the 0+ methods used to be called in wrong (reverse) order.
"WELL VOLUNTEERED!" echoed across conference rooms and IRC channels. Matt S. Trout's battle cry that transformed reluctant volunteers into community leaders.
With profound sadness, we announce Matt's passing. Since the early 2000s, Matt shaped Perl through sheer force of will: IRC operator, PAUSE administrator, Shadowcat Systems co-founder, architect of DBIx::Class. His opinions came wrapped in profanity and delivered at maximum volume. He suffered no fools and grew to sometimes realize he should apologize. Yet this same abrasive exterior protected fierce dedication to mentoring, developers he harangued into volunteering now lead the community themselves. Matt's deliberately mind-bending code pushed Perl forward. Every modern Perl developer touches his legacy daily.
Well volunteered, Matt. Rest in peace.
Perl 5.43.1 represents approximately 2 weeks of development since Perl 5.43.0 and contains approximately 15,000 lines of changes across 410 files from 21 authors.
Excluding auto-generated files, documentation and release tools, there were approximately 12,000 lines of changes to 360 .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.43.1:
Alexander Karelas, Chad Granum, Chris 'BinGOs' Williams, Chris Prather, Dagfinn Ilmari Mannsåker, Dan Book, Daniel Dragan, Daniel Laügt, Dave Cross, David Mitchell, James E Keenan, Karen Etheridge, Karl Williamson, Leon Timmermans, Paul Evans, Philippe Bruhat (BooK), Richard Leach, Štěpán Němec, TAKAI Kousuke, 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.