[ this is a template for a new perldelta file. Any text flagged as XXX needs to be processed before release. ]
perldelta - what is new for perl v5.41.11
This document describes differences between the 5.41.10 release and the 5.41.11 release.
If you are upgrading from an earlier release such as 5.41.9, first readperl54110delta, which describes differences between 5.41.9 and 5.41.10.
XXX Any important notices here
XXX New core language features go here. Summarize user-visible core language enhancements. Particularly prominent performance optimisations could go here, but most should go in the"Performance Enhancements" section.
[ List each enhancement as a =head2 entry ]
XXX Any security-related notices go here. In particular, any security vulnerabilities closed should be noted here rather than in the"Selected Bug Fixes" section.
[ List each security issue as a =head2 entry ]
XXX For a release on a stable branch, this section aspires to be:
There are no changes intentionally incompatible with 5.XXX.XXXIf any exist, they are bugs, and we request that you submit areport. See L</Reporting Bugs> below.[ List each incompatible change as a =head2 entry ]
XXX Any deprecated features, syntax, modules etc. should be listed here.
XXX Remove this section if not applicable.
The following modules will be removed from the core distribution in a future release, and will at that time need to be installed from CPAN. Distributions on CPAN which require these modules will need to list them as prerequisites.
The core versions of these modules will now issuedeprecated-category warnings to alert you to this fact. To silence these deprecation warnings, install the modules in question from CPAN.
Note that these are (with rare exceptions) fine modules that you are encouraged to continue to use. Their disinclusion from core primarily hinges on their necessity to bootstrapping a fully functional, CPAN-capable Perl installation, not usually on concerns over their design.
XXX Note that deprecated modules should be listed here even if they are listed as an updated module in the"Modules and Pragmata" section.
[ List each other deprecation as a =head2 entry ]
XXX Changes which enhance performance without changing behaviour go here. There may well be none in a stable release.
[ List each enhancement as an =item entry ]
XXX
XXX All changes to installed files incpan/,dist/,ext/ andlib/ go here. IfModule::CoreList is updated, generate an initial draft of the following sections usingPorting/corelist-perldelta.pl. A paragraph summary for important changes should then be added by hand. In an ideal world, dual-life modules would have aChanges file that could be cribbed.
The list of new and updated modules is modified automatically as part of preparing a Perl release, so the only reason to manually add entries here is if you're summarising the important changes in the module update. (Also, if the manually-added details don't match the automatically-generated ones, the release manager will have to investigate the situation carefully.)
[ Within each section, list entries as an =item entry ]
XXX Remove this section ifPorting/corelist-perldelta.pl did not add any content here.
XXX has been upgraded from version A.xx to B.yy.
XXX If there was something important to note about this change, include that here.
XXX Remove this section ifPorting/corelist-perldelta.pl did not add any content here.
XXX Changes to files inpod/ go here. Consider grouping entries by file and be sure to link to the appropriate page, e.g.perlfunc.
XXX Changes which createnew files inpod/ go here.
XXX Description of the purpose of the new file here
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 athttps://github.com/Perl/perl5/issues.
XXX Changes which significantly change existing files inpod/ go here. However, any changes topod/perldiag.pod should go in the"Diagnostics" section.
Additionally, the following selected changes have been made:
XXX Description of the change here
The following additions or changes have been made to diagnostic output, including warnings and fatal error messages. For the complete list of diagnostic messages, seeperldiag.
XXX New or changed warnings emitted by the core'sC code go here. Also include any changes inperldiag that reconcile it to theC code.
XXX Newly added diagnostic messages go under here, separated into"New Errors" and"New Warnings"
XXXmessage
XXXmessage
XXX Changes (i.e. rewording) of diagnostic messages go here
XXX Describe change here
XXX Changes to installed programs such asperldoc andxsubpp go here. Most of these are built within the directoryutils.
[ List utility changes as a =head2 entry for each utility and =item entries for each change UseXXX with program names to get proper documentation linking. ]
XXX
XXX Changes toConfigure,installperl,installman, and analogous tools go here. Any other changes to the Perl build process should be listed here. However, any platform-specific changes should be listed in the"Platform Support" section, instead.
[ List changes as an =item entry ].
XXX
XXX Any significant changes to the testing of a freshly built perl should be listed here. Changes which createnew files int/ go here as do any large changes to the testing harness (e.g. when parallel testing was added). Changes to existing files int/ aren't worth summarizing, although the bugs that they represent may be covered elsewhere.
XXX If there were no significant test changes, say this:
Tests were added and changed to reflect the other additions and changes in this release.
XXX If instead there were significant changes, say this:
Tests were added and changed to reflect the other additions and changes in this release. Furthermore, these significant changes were made:
[ List each test improvement as an =item entry ]
XXX
XXX Any changes to platform support should be listed in the sections below.
[ Within the sections, list each platform as an =item entry with specific changes as paragraphs below it. ]
XXX List any platforms that this version of perl compiles on, that previous versions did not. These will either be enabled by new files in thehints/ directories, or new subdirectories andREADME files at the top level of the source tree.
XXX
XXX List any platforms that this version of perl no longer compiles on.
XXX
XXX List any changes for specific platforms. This could include configuration and compilation changes or changes in portability/compatibility. However, changes within modules for platforms should generally be listed in the"Modules and Pragmata" section.
XXX
XXX Changes which affect the interface available toXS code go here. Other significant internal changes for future core maintainers should be noted as well.
[ List each change as an =item entry ]
XXX
XXX Important bug fixes in the core language are summarized here. Bug fixes in files inext/ andlib/ are best summarized in"Modules and Pragmata".
XXX Include references to GitHub issues and PRs as: [GH #12345] and the release manager will later use a regex to expand these into links.
[ List each fix as an =item entry ]
XXX
XXX Descriptions of platform agnostic bugs we know we can't fix go here. Any tests that had to beTODOed for the release would be noted here. Unfixed platform specific bugs also go here.
[ List each fix as an =item entry ]
XXX
XXX Add anything here that we forgot to add, or were mistaken about, in theperldelta of a previous release.
XXX If any significant core contributor or member of the CPAN community has died, add a short obituary here.
XXX Generate this with:
perl Porting/acknowledgements.pl v5.41.10..HEADIf you find what you think is a bug, you might check the perl bug database athttps://github.com/Perl/perl5/issues. There may also be information athttps://www.perl.org/, the Perl Home Page.
If you believe you have an unreported bug, please open an issue athttps://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 theperlthanks program:
perlthanksThis will send an email to the Perl 5 Porters list with your show of thanks.
TheChanges file for an explanation of how to view exhaustive details on what changed.
TheINSTALL file for how to build Perl.
TheREADME file for general stuff.
TheArtistic andCopying files for copyright information.
Perldoc Browser is maintained by Dan Book (DBOOK). Please contact him via theGitHub issue tracker oremail regarding any issues with the site itself, search, or rendering of documentation.
The Perl documentation is maintained by the Perl 5 Porters in the development of Perl. Please contact them via thePerl issue tracker, themailing list, orIRC to report any issues with the contents or format of the documentation.