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.29.1
12 This document describes differences between the 5.29.0 release and the 5.29.1
15 If you are upgrading from an earlier release such as 5.28.0, first read
16 L<perl5290delta>, which describes differences between 5.28.0 and 5.29.0.
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 Delimiters must now be graphemes
50 See L<perldeprecation/Use of unassigned code point or non-standalone grapheme for a delimiter.>
52 =head2 Some formerly deprecated uses of an unescaped left brace C<"{">
53 in regular expression patterns are now illegal
55 But to avoid breaking code unnecessarily, most instances that issued a
56 deprecation warning, remain legal and now have a non-deprecation warning
57 raised. See L<perldeprecation/Unescaped left braces in regular
62 XXX Any deprecated features, syntax, modules etc. should be listed here.
64 =head2 Module removals
66 XXX Remove this section if not applicable.
68 The following modules will be removed from the core distribution in a
69 future release, and will at that time need to be installed from CPAN.
70 Distributions on CPAN which require these modules will need to list them as
73 The core versions of these modules will now issue C<"deprecated">-category
74 warnings to alert you to this fact. To silence these deprecation warnings,
75 install the modules in question from CPAN.
77 Note that these are (with rare exceptions) fine modules that you are encouraged
78 to continue to use. Their disinclusion from core primarily hinges on their
79 necessity to bootstrapping a fully functional, CPAN-capable Perl installation,
80 not usually on concerns over their design.
86 XXX Note that deprecated modules should be listed here even if they are listed
87 as an updated module in the L</Modules and Pragmata> section.
91 [ List each other deprecation as a =head2 entry ]
93 =head1 Performance Enhancements
95 XXX Changes which enhance performance without changing behaviour go here.
96 There may well be none in a stable release.
98 [ List each enhancement as an =item entry ]
104 Translating from UTF-8 into the code point it represents now is done via
105 a deterministic finite automaton, speeding it up. As a typical example,
106 C<ord("\x7fff")> now requires 12% fewer instructions than before.
107 The performance of checking that a sequence of bytes is valid UTF-8 is
108 similarly improved, again by using a dfa.
112 =head1 Modules and Pragmata
114 XXX All changes to installed files in F<cpan/>, F<dist/>, F<ext/> and F<lib/>
115 go here. If Module::CoreList is updated, generate an initial draft of the
116 following sections using F<Porting/corelist-perldelta.pl>. A paragraph summary
117 for important changes should then be added by hand. In an ideal world,
118 dual-life modules would have a F<Changes> file that could be cribbed.
120 The list of new and updated modules is modified automatically as part of
121 preparing a Perl release, so the only reason to manually add entries here is if
122 you're summarising the important changes in the module update. (Also, if the
123 manually-added details don't match the automatically-generated ones, the
124 release manager will have to investigate the situation carefully.)
126 [ Within each section, list entries as an =item entry ]
128 =head2 New Modules and Pragmata
134 XXX Remove this section if not applicable.
138 =head2 Updated Modules and Pragmata
144 L<XXX> has been upgraded from version A.xx to B.yy.
146 If there was something important to note about this change, include that here.
150 =head2 Removed Modules and Pragmata
162 XXX Changes to files in F<pod/> go here. Consider grouping entries by
163 file and be sure to link to the appropriate page, e.g. L<perlfunc>.
165 =head2 New Documentation
167 XXX Changes which create B<new> files in F<pod/> go here.
171 XXX Description of the purpose of the new file here
173 =head2 Changes to Existing Documentation
175 We have attempted to update the documentation to reflect the changes
176 listed in this document. If you find any we have missed, send email
177 to L<perlbug@perl.org|mailto:perlbug@perl.org>.
179 XXX Changes which significantly change existing files in F<pod/> go here.
180 However, any changes to F<pod/perldiag.pod> should go in the L</Diagnostics>
183 Additionally, the following selected changes have been made:
191 XXX Description of the change here
197 The following additions or changes have been made to diagnostic output,
198 including warnings and fatal error messages. For the complete list of
199 diagnostic messages, see L<perldiag>.
201 XXX New or changed warnings emitted by the core's C<C> code go here. Also
202 include any changes in L<perldiag> that reconcile it to the C<C> code.
204 =head2 New Diagnostics
206 XXX Newly added diagnostic messages go under here, separated into New Errors
215 XXX L<message|perldiag/"message">
225 XXX L<message|perldiag/"message">
229 =head2 Changes to Existing Diagnostics
231 XXX Changes (i.e. rewording) of diagnostic messages go here
237 XXX Describe change here
241 =head1 Utility Changes
243 XXX Changes to installed programs such as F<perlbug> and F<xsubpp> go here.
244 Most of these are built within the directory F<utils>.
246 [ List utility changes as a =head2 entry for each utility and =item
247 entries for each change
248 Use L<XXX> with program names to get proper documentation linking. ]
260 =head1 Configuration and Compilation
262 XXX Changes to F<Configure>, F<installperl>, F<installman>, and analogous tools
263 go here. Any other changes to the Perl build process should be listed here.
264 However, any platform-specific changes should be listed in the
265 L</Platform Support> section, instead.
267 [ List changes as an =item entry ].
279 XXX Any significant changes to the testing of a freshly built perl should be
280 listed here. Changes which create B<new> files in F<t/> go here as do any
281 large changes to the testing harness (e.g. when parallel testing was added).
282 Changes to existing files in F<t/> aren't worth summarizing, although the bugs
283 that they represent may be covered elsewhere.
285 XXX If there were no significant test changes, say this:
287 Tests were added and changed to reflect the other additions and changes
290 XXX If instead there were significant changes, say this:
292 Tests were added and changed to reflect the other additions and
293 changes in this release. Furthermore, these significant changes were
296 [ List each test improvement as an =item entry ]
306 =head1 Platform Support
308 XXX Any changes to platform support should be listed in the sections below.
310 [ Within the sections, list each platform as an =item entry with specific
311 changes as paragraphs below it. ]
315 XXX List any platforms that this version of perl compiles on, that previous
316 versions did not. These will either be enabled by new files in the F<hints/>
317 directories, or new subdirectories and F<README> files at the top level of the
322 =item XXX-some-platform
328 =head2 Discontinued Platforms
330 XXX List any platforms that this version of perl no longer compiles on.
334 =item XXX-some-platform
340 =head2 Platform-Specific Notes
342 XXX List any changes for specific platforms. This could include configuration
343 and compilation changes or changes in portability/compatibility. However,
344 changes within modules for platforms should generally be listed in the
345 L</Modules and Pragmata> section.
349 =item XXX-some-platform
355 =head1 Internal Changes
357 XXX Changes which affect the interface available to C<XS> code go here. Other
358 significant internal changes for future core maintainers should be noted as
361 [ List each change as an =item entry ]
371 =head1 Selected Bug Fixes
373 XXX Important bug fixes in the core language are summarized here. Bug fixes in
374 files in F<ext/> and F<lib/> are best summarized in L</Modules and Pragmata>.
376 [ List each fix as an =item entry ]
386 =head1 Known Problems
388 XXX Descriptions of platform agnostic bugs we know we can't fix go here. Any
389 tests that had to be C<TODO>ed for the release would be noted here. Unfixed
390 platform specific bugs also go here.
392 [ List each fix as an =item entry ]
402 =head1 Errata From Previous Releases
408 XXX Add anything here that we forgot to add, or were mistaken about, in
409 the perldelta of a previous release.
415 XXX If any significant core contributor or member of the CPAN community has
416 died, add a short obituary here.
418 =head1 Acknowledgements
420 XXX Generate this with:
422 perl Porting/acknowledgements.pl v5.27.11..HEAD
424 =head1 Reporting Bugs
426 If you find what you think is a bug, you might check the perl bug database
427 at L<https://rt.perl.org/> . There may also be information at
428 L<http://www.perl.org/> , the Perl Home Page.
430 If you believe you have an unreported bug, please run the L<perlbug> program
431 included with your release. Be sure to trim your bug down to a tiny but
432 sufficient test case. Your bug report, along with the output of C<perl -V>,
433 will be sent off to perlbug@perl.org to be analysed by the Perl porting team.
435 If the bug you are reporting has security implications which make it
436 inappropriate to send to a publicly archived mailing list, then see
437 L<perlsec/SECURITY VULNERABILITY CONTACT INFORMATION>
438 for details of how to report the issue.
442 If you wish to thank the Perl 5 Porters for the work we had done in Perl 5,
443 you can do so by running the C<perlthanks> program:
447 This will send an email to the Perl 5 Porters list with your show of thanks.
451 The F<Changes> file for an explanation of how to view exhaustive details on
454 The F<INSTALL> file for how to build Perl.
456 The F<README> file for general stuff.
458 The F<Artistic> and F<Copying> files for copyright information.