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.10
12 This document describes differences between the 5.29.9 release and the 5.29.10
15 If you are upgrading from an earlier release such as 5.29.8, first read
16 L<perl5299delta>, which describes differences between 5.29.8 and 5.29.9.
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 =head2 Perl now supports draft Unicode 12.1
30 Unicode 12.1 differs from 12.0 only in the addition of a single
31 character, that for the new Japanese era name. The intent is to ship
32 Perl 5.30 with Unicode 12.1. The final release of 12.1 is scheduled for
33 May 7, 2019. Hopefully, there won't be any code changes to the draft
34 after the release of Perl 5.29.10.
38 XXX Any security-related notices go here. In particular, any security
39 vulnerabilities closed should be noted here rather than in the
40 L</Selected Bug Fixes> section.
42 [ List each security issue as a =head2 entry ]
44 =head1 Incompatible Changes
46 XXX For a release on a stable branch, this section aspires to be:
48 There are no changes intentionally incompatible with 5.XXX.XXX
49 If any exist, they are bugs, and we request that you submit a
50 report. See L</Reporting Bugs> below.
52 [ List each incompatible change as a =head2 entry ]
56 XXX Any deprecated features, syntax, modules etc. should be listed here.
58 =head2 Module removals
60 XXX Remove this section if not applicable.
62 The following modules will be removed from the core distribution in a
63 future release, and will at that time need to be installed from CPAN.
64 Distributions on CPAN which require these modules will need to list them as
67 The core versions of these modules will now issue C<"deprecated">-category
68 warnings to alert you to this fact. To silence these deprecation warnings,
69 install the modules in question from CPAN.
71 Note that these are (with rare exceptions) fine modules that you are encouraged
72 to continue to use. Their disinclusion from core primarily hinges on their
73 necessity to bootstrapping a fully functional, CPAN-capable Perl installation,
74 not usually on concerns over their design.
80 XXX Note that deprecated modules should be listed here even if they are listed
81 as an updated module in the L</Modules and Pragmata> section.
85 [ List each other deprecation as a =head2 entry ]
87 =head1 Performance Enhancements
89 XXX Changes which enhance performance without changing behaviour go here.
90 There may well be none in a stable release.
92 [ List each enhancement as an =item entry ]
102 =head1 Modules and Pragmata
104 XXX All changes to installed files in F<cpan/>, F<dist/>, F<ext/> and F<lib/>
105 go here. If Module::CoreList is updated, generate an initial draft of the
106 following sections using F<Porting/corelist-perldelta.pl>. A paragraph summary
107 for important changes should then be added by hand. In an ideal world,
108 dual-life modules would have a F<Changes> file that could be cribbed.
110 The list of new and updated modules is modified automatically as part of
111 preparing a Perl release, so the only reason to manually add entries here is if
112 you're summarising the important changes in the module update. (Also, if the
113 manually-added details don't match the automatically-generated ones, the
114 release manager will have to investigate the situation carefully.)
116 [ Within each section, list entries as an =item entry ]
118 =head2 New Modules and Pragmata
124 XXX Remove this section if not applicable.
128 =head2 Updated Modules and Pragmata
134 L<XXX> has been upgraded from version A.xx to B.yy.
136 If there was something important to note about this change, include that here.
140 L<Module::CoreList> has been upgraded from version 5.20190320 to 5.20190420.
144 =head2 Removed Modules and Pragmata
156 XXX Changes to files in F<pod/> go here. Consider grouping entries by
157 file and be sure to link to the appropriate page, e.g. L<perlfunc>.
159 =head2 New Documentation
161 XXX Changes which create B<new> files in F<pod/> go here.
165 XXX Description of the purpose of the new file here
167 =head2 Changes to Existing Documentation
169 We have attempted to update the documentation to reflect the changes
170 listed in this document. If you find any we have missed, send email
171 to L<perlbug@perl.org|mailto:perlbug@perl.org>.
173 XXX Changes which significantly change existing files in F<pod/> go here.
174 However, any changes to F<pod/perldiag.pod> should go in the L</Diagnostics>
177 Additionally, the following selected changes have been made:
185 XXX Description of the change here
191 The following additions or changes have been made to diagnostic output,
192 including warnings and fatal error messages. For the complete list of
193 diagnostic messages, see L<perldiag>.
195 XXX New or changed warnings emitted by the core's C<C> code go here. Also
196 include any changes in L<perldiag> that reconcile it to the C<C> code.
198 =head2 New Diagnostics
200 XXX Newly added diagnostic messages go under here, separated into New Errors
209 XXX L<message|perldiag/"message">
219 XXX L<message|perldiag/"message">
223 =head2 Changes to Existing Diagnostics
225 XXX Changes (i.e. rewording) of diagnostic messages go here
231 XXX Describe change here
235 =head1 Utility Changes
237 XXX Changes to installed programs such as F<perlbug> and F<xsubpp> go here.
238 Most of these are built within the directory F<utils>.
240 [ List utility changes as a =head2 entry for each utility and =item
241 entries for each change
242 Use L<XXX> with program names to get proper documentation linking. ]
254 =head1 Configuration and Compilation
256 XXX Changes to F<Configure>, F<installperl>, F<installman>, and analogous tools
257 go here. Any other changes to the Perl build process should be listed here.
258 However, any platform-specific changes should be listed in the
259 L</Platform Support> section, instead.
261 [ List changes as an =item entry ].
273 XXX Any significant changes to the testing of a freshly built perl should be
274 listed here. Changes which create B<new> files in F<t/> go here as do any
275 large changes to the testing harness (e.g. when parallel testing was added).
276 Changes to existing files in F<t/> aren't worth summarizing, although the bugs
277 that they represent may be covered elsewhere.
279 XXX If there were no significant test changes, say this:
281 Tests were added and changed to reflect the other additions and changes
284 XXX If instead there were significant changes, say this:
286 Tests were added and changed to reflect the other additions and
287 changes in this release. Furthermore, these significant changes were
290 [ List each test improvement as an =item entry ]
300 =head1 Platform Support
302 XXX Any changes to platform support should be listed in the sections below.
304 [ Within the sections, list each platform as an =item entry with specific
305 changes as paragraphs below it. ]
309 XXX List any platforms that this version of perl compiles on, that previous
310 versions did not. These will either be enabled by new files in the F<hints/>
311 directories, or new subdirectories and F<README> files at the top level of the
316 =item XXX-some-platform
322 =head2 Discontinued Platforms
324 XXX List any platforms that this version of perl no longer compiles on.
328 =item XXX-some-platform
334 =head2 Platform-Specific Notes
336 XXX List any changes for specific platforms. This could include configuration
337 and compilation changes or changes in portability/compatibility. However,
338 changes within modules for platforms should generally be listed in the
339 L</Modules and Pragmata> section.
349 Support for compiling perl on Windows using Microsoft Visual Studio 2019
350 (containing Visual C++ 14.2) has been added.
356 =head1 Internal Changes
358 XXX Changes which affect the interface available to C<XS> code go here. Other
359 significant internal changes for future core maintainers should be noted as
362 [ List each change as an =item entry ]
368 A new function L<perlapi/C<my_strtod>> or its synonym, Strtod(), is
369 now available with the same signature as the libc strtod(). It provides
370 strotod() equivalent behavior on all platforms, using the best available
371 precision, depending on platform capabilities and F<Configure> options,
372 while handling locale-related issues, such as if the radix character
373 should be a dot or comma.
377 =head1 Selected Bug Fixes
379 XXX Important bug fixes in the core language are summarized here. Bug fixes in
380 files in F<ext/> and F<lib/> are best summarized in L</Modules and Pragmata>.
382 [ List each fix as an =item entry ]
388 Perl now exposes POSIX C<getcwd> as C<Internals::getcwd()> if
389 available. This is intended for use by C<Cwd.pm> during bootstrapping
390 and may be removed or changed without notice. This fixes some
391 bootstrapping issues while building perl in a directory where some
392 ancestor directory isn't readable. [perl #133951]
396 =head1 Known Problems
398 XXX Descriptions of platform agnostic bugs we know we can't fix go here. Any
399 tests that had to be C<TODO>ed for the release would be noted here. Unfixed
400 platform specific bugs also go here.
402 [ List each fix as an =item entry ]
412 =head1 Errata From Previous Releases
418 The perldelta for 5.29.9 listed the enhancement about regular expression
419 lookbehind in the C<Security> section rather than the C<Core Enhancements>
420 section. Its title should also have indicated that it is "Limited"
421 variable-length lookbehind (up to 255 characters). (Note that a
422 technique has now been published to achieve arbitrary variable length
423 lookbehind with pre-existing Perl constructs and is linked to in L<perlre>.
425 L<http://www.drregex.com/2019/02/variable-length-lookbehinds-actually.html>.)
427 XXX Add anything here that we forgot to add, or were mistaken about, in
428 the perldelta of a previous release.
434 XXX If any significant core contributor or member of the CPAN community has
435 died, add a short obituary here.
437 =head1 Acknowledgements
439 XXX Generate this with:
441 perl Porting/acknowledgements.pl v5.29.9..HEAD
443 =head1 Reporting Bugs
445 If you find what you think is a bug, you might check the perl bug database
446 at L<https://rt.perl.org/>. There may also be information at
447 L<http://www.perl.org/>, the Perl Home Page.
449 If you believe you have an unreported bug, please run the L<perlbug> program
450 included with your release. Be sure to trim your bug down to a tiny but
451 sufficient test case. Your bug report, along with the output of C<perl -V>,
452 will be sent off to perlbug@perl.org to be analysed by the Perl porting team.
454 If the bug you are reporting has security implications which make it
455 inappropriate to send to a publicly archived mailing list, then see
456 L<perlsec/SECURITY VULNERABILITY CONTACT INFORMATION>
457 for details of how to report the issue.
461 If you wish to thank the Perl 5 Porters for the work we had done in Perl 5,
462 you can do so by running the C<perlthanks> program:
466 This will send an email to the Perl 5 Porters list with your show of thanks.
470 The F<Changes> file for an explanation of how to view exhaustive details on
473 The F<INSTALL> file for how to build Perl.
475 The F<README> file for general stuff.
477 The F<Artistic> and F<Copying> files for copyright information.