5 [ this is a template for a new perldelta file. Any text flagged as XXX needs
6 to be processed before release. ]
8 perldelta - what is new for perl v5.31.5
12 This document describes differences between the 5.31.4 release and the 5.31.5
15 If you are upgrading from an earlier release such as 5.31.3, first read
16 L<perl5314delta>, which describes differences between 5.31.3 and 5.31.4.
20 XXX Any important notices here
22 =head1 Core Enhancements
24 XXX New core language features go here. Summarize user-visible core language
25 enhancements. Particularly prominent performance optimisations could go
26 here, but most should go in the L</Performance Enhancements> section.
28 [ List each enhancement as a =head2 entry ]
32 XXX Any security-related notices go here. In particular, any security
33 vulnerabilities closed should be noted here rather than in the
34 L</Selected Bug Fixes> section.
36 [ List each security issue as a =head2 entry ]
38 =head1 Incompatible Changes
40 XXX For a release on a stable branch, this section aspires to be:
42 There are no changes intentionally incompatible with 5.XXX.XXX
43 If any exist, they are bugs, and we request that you submit a
44 report. See L</Reporting Bugs> below.
46 [ List each incompatible change as a =head2 entry ]
48 =head2 Modifiable variables are no longer permitted in constants
53 $sub = sub () { $var };
55 where C<$var> is referenced elsewhere in some sort of modiable context
56 now produces an exception when the sub is defined.
58 This error can be avoided by adding a return to the sub definition:
60 $sub = sub () { return $var };
62 This has been deprecated since perl 5.22.
68 XXX Any deprecated features, syntax, modules etc. should be listed here.
70 =head2 Module removals
72 XXX Remove this section if not applicable.
74 The following modules will be removed from the core distribution in a
75 future release, and will at that time need to be installed from CPAN.
76 Distributions on CPAN which require these modules will need to list them as
79 The core versions of these modules will now issue C<"deprecated">-category
80 warnings to alert you to this fact. To silence these deprecation warnings,
81 install the modules in question from CPAN.
83 Note that these are (with rare exceptions) fine modules that you are encouraged
84 to continue to use. Their disinclusion from core primarily hinges on their
85 necessity to bootstrapping a fully functional, CPAN-capable Perl installation,
86 not usually on concerns over their design.
92 XXX Note that deprecated modules should be listed here even if they are listed
93 as an updated module in the L</Modules and Pragmata> section.
97 [ List each other deprecation as a =head2 entry ]
99 =head1 Performance Enhancements
101 XXX Changes which enhance performance without changing behaviour go here.
102 There may well be none in a stable release.
104 [ List each enhancement as an =item entry ]
114 =head1 Modules and Pragmata
116 XXX All changes to installed files in F<cpan/>, F<dist/>, F<ext/> and F<lib/>
117 go here. If Module::CoreList is updated, generate an initial draft of the
118 following sections using F<Porting/corelist-perldelta.pl>. A paragraph summary
119 for important changes should then be added by hand. In an ideal world,
120 dual-life modules would have a F<Changes> file that could be cribbed.
122 The list of new and updated modules is modified automatically as part of
123 preparing a Perl release, so the only reason to manually add entries here is if
124 you're summarising the important changes in the module update. (Also, if the
125 manually-added details don't match the automatically-generated ones, the
126 release manager will have to investigate the situation carefully.)
128 [ Within each section, list entries as an =item entry ]
130 =head2 New Modules and Pragmata
136 XXX Remove this section if not applicable.
140 =head2 Updated Modules and Pragmata
146 L<XXX> has been upgraded from version A.xx to B.yy.
148 If there was something important to note about this change, include that here.
152 =head2 Removed Modules and Pragmata
164 XXX Changes to files in F<pod/> go here. Consider grouping entries by
165 file and be sure to link to the appropriate page, e.g. L<perlfunc>.
167 =head2 New Documentation
169 XXX Changes which create B<new> files in F<pod/> go here.
173 XXX Description of the purpose of the new file here
175 =head2 Changes to Existing Documentation
177 We have attempted to update the documentation to reflect the changes
178 listed in this document. If you find any we have missed, send email
179 to L<perlbug@perl.org|mailto:perlbug@perl.org>.
181 XXX Changes which significantly change existing files in F<pod/> go here.
182 However, any changes to F<pod/perldiag.pod> should go in the L</Diagnostics>
185 Additionally, the following selected changes have been made:
193 XXX Description of the change here
199 The following additions or changes have been made to diagnostic output,
200 including warnings and fatal error messages. For the complete list of
201 diagnostic messages, see L<perldiag>.
203 XXX New or changed warnings emitted by the core's C<C> code go here. Also
204 include any changes in L<perldiag> that reconcile it to the C<C> code.
206 =head2 New Diagnostics
208 XXX Newly added diagnostic messages go under here, separated into New Errors
217 XXX L<message|perldiag/"message">
227 XXX L<message|perldiag/"message">
231 =head2 Changes to Existing Diagnostics
233 XXX Changes (i.e. rewording) of diagnostic messages go here
239 XXX Describe change here
243 =head1 Utility Changes
245 XXX Changes to installed programs such as F<perlbug> and F<xsubpp> go here.
246 Most of these are built within the directory F<utils>.
248 [ List utility changes as a =head2 entry for each utility and =item
249 entries for each change
250 Use L<XXX> with program names to get proper documentation linking. ]
262 =head1 Configuration and Compilation
264 XXX Changes to F<Configure>, F<installperl>, F<installman>, and analogous tools
265 go here. Any other changes to the Perl build process should be listed here.
266 However, any platform-specific changes should be listed in the
267 L</Platform Support> section, instead.
269 [ List changes as an =item entry ].
275 Perl now no longer probes for C<d_u32align>, defaulting to C<define>
276 on all platforms. This check was error prone when it was done, which
277 was on 32-bit platforms only. [perl #133495]
283 XXX Any significant changes to the testing of a freshly built perl should be
284 listed here. Changes which create B<new> files in F<t/> go here as do any
285 large changes to the testing harness (e.g. when parallel testing was added).
286 Changes to existing files in F<t/> aren't worth summarizing, although the bugs
287 that they represent may be covered elsewhere.
289 XXX If there were no significant test changes, say this:
291 Tests were added and changed to reflect the other additions and changes
294 XXX If instead there were significant changes, say this:
296 Tests were added and changed to reflect the other additions and
297 changes in this release. Furthermore, these significant changes were
300 [ List each test improvement as an =item entry ]
310 =head1 Platform Support
312 XXX Any changes to platform support should be listed in the sections below.
314 [ Within the sections, list each platform as an =item entry with specific
315 changes as paragraphs below it. ]
319 XXX List any platforms that this version of perl compiles on, that previous
320 versions did not. These will either be enabled by new files in the F<hints/>
321 directories, or new subdirectories and F<README> files at the top level of the
326 =item XXX-some-platform
332 =head2 Discontinued Platforms
334 XXX List any platforms that this version of perl no longer compiles on.
338 =item XXX-some-platform
344 =head2 Platform-Specific Notes
346 XXX List any changes for specific platforms. This could include configuration
347 and compilation changes or changes in portability/compatibility. However,
348 changes within modules for platforms should generally be listed in the
349 L</Modules and Pragmata> section.
353 =item XXX-some-platform
359 =head1 Internal Changes
361 XXX Changes which affect the interface available to C<XS> code go here. Other
362 significant internal changes for future core maintainers should be noted as
365 [ List each change as an =item entry ]
371 Added the C<<PL_curstackinfo->si_cxsubix>> field. This records the stack
372 index of the most recently pushed sub/format/eval context. It is set and
373 restored automatically by C<cx_pushsub()>, C<cx_popsub()> etc., but would
374 need to be manually managed if you do any unusual manipulation of the
379 Various macros dealing with character type classification and changing
380 case where the input is encoded in UTF-8 now require an extra parameter
381 to prevent potential reads beyond the end of the buffer. Use of these
382 has generated a deprecation warning since 5.26. Details are in
383 L<perldeprecation/In XS code, use of various macros dealing with UTF-8.>
387 =head1 Selected Bug Fixes
389 XXX Important bug fixes in the core language are summarized here. Bug fixes in
390 files in F<ext/> and F<lib/> are best summarized in L</Modules and Pragmata>.
392 [ List each fix as an =item entry ]
402 =head1 Known Problems
404 XXX Descriptions of platform agnostic bugs we know we can't fix go here. Any
405 tests that had to be C<TODO>ed for the release would be noted here. Unfixed
406 platform specific bugs also go here.
408 [ List each fix as an =item entry ]
418 =head1 Errata From Previous Releases
424 XXX Add anything here that we forgot to add, or were mistaken about, in
425 the perldelta of a previous release.
431 XXX If any significant core contributor or member of the CPAN community has
432 died, add a short obituary here.
434 =head1 Acknowledgements
436 XXX Generate this with:
438 perl Porting/acknowledgements.pl v5.31.4..HEAD
440 =head1 Reporting Bugs
442 If you find what you think is a bug, you might check the perl bug database
443 at L<https://rt.perl.org/>. There may also be information at
444 L<https://www.perl.org/>, the Perl Home Page.
446 If you believe you have an unreported bug, please run the L<perlbug> program
447 included with your release. Be sure to trim your bug down to a tiny but
448 sufficient test case. Your bug report, along with the output of C<perl -V>,
449 will be sent off to perlbug@perl.org to be analysed by the Perl porting team.
451 If the bug you are reporting has security implications which make it
452 inappropriate to send to a publicly archived mailing list, then see
453 L<perlsec/SECURITY VULNERABILITY CONTACT INFORMATION>
454 for details of how to report the issue.
458 If you wish to thank the Perl 5 Porters for the work we had done in Perl 5,
459 you can do so by running the C<perlthanks> program:
463 This will send an email to the Perl 5 Porters list with your show of thanks.
467 The F<Changes> file for an explanation of how to view exhaustive details on
470 The F<INSTALL> file for how to build Perl.
472 The F<README> file for general stuff.
474 The F<Artistic> and F<Copying> files for copyright information.