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.27.2
12 This document describes differences between the 5.27.1 release and the 5.27.2
15 If you are upgrading from an earlier release such as 5.27.0, first read
16 L<perl5271delta>, which describes differences between 5.27.0 and 5.27.1.
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 ]
30 =head2 Unicode 10.0 is supported
32 A list of changes is at
33 L<http://www.unicode.org/versions/Unicode10.0.0>.
37 XXX Any security-related notices go here. In particular, any security
38 vulnerabilities closed should be noted here rather than in the
39 L</Selected Bug Fixes> section.
41 [ List each security issue as a =head2 entry ]
43 =head1 Incompatible Changes
45 XXX For a release on a stable branch, this section aspires to be:
47 There are no changes intentionally incompatible with 5.XXX.XXX
48 If any exist, they are bugs, and we request that you submit a
49 report. See L</Reporting Bugs> below.
51 [ List each incompatible change as a =head2 entry ]
55 XXX Any deprecated features, syntax, modules etc. should be listed here.
57 =head2 Module removals
59 XXX Remove this section if inapplicable.
61 The following modules will be removed from the core distribution in a
62 future release, and will at that time need to be installed from CPAN.
63 Distributions on CPAN which require these modules will need to list them as
66 The core versions of these modules will now issue C<"deprecated">-category
67 warnings to alert you to this fact. To silence these deprecation warnings,
68 install the modules in question from CPAN.
70 Note that these are (with rare exceptions) fine modules that you are encouraged
71 to continue to use. Their disinclusion from core primarily hinges on their
72 necessity to bootstrapping a fully functional, CPAN-capable Perl installation,
73 not usually on concerns over their design.
79 XXX Note that deprecated modules should be listed here even if they are listed
80 as an updated module in the L</Modules and Pragmata> section.
84 [ List each other deprecation as a =head2 entry ]
86 =head1 Performance Enhancements
88 XXX Changes which enhance performance without changing behaviour go here.
89 There may well be none in a stable release.
91 [ List each enhancement as a =item entry ]
101 =head1 Modules and Pragmata
103 XXX All changes to installed files in F<cpan/>, F<dist/>, F<ext/> and F<lib/>
104 go here. If Module::CoreList is updated, generate an initial draft of the
105 following sections using F<Porting/corelist-perldelta.pl>. A paragraph summary
106 for important changes should then be added by hand. In an ideal world,
107 dual-life modules would have a F<Changes> file that could be cribbed.
109 [ Within each section, list entries as a =item entry ]
111 =head2 New Modules and Pragmata
121 =head2 Updated Modules and Pragmata
127 L<XXX> has been upgraded from version A.xx to B.yy.
131 L<ExtUtils::CBuilder> has been upgraded from version 0.280225 to 0.280227.
135 L<Time::HiRes> has been upgraded from version 1.9742 to 1.9743.
139 =head2 Removed Modules and Pragmata
151 XXX Changes to files in F<pod/> go here. Consider grouping entries by
152 file and be sure to link to the appropriate page, e.g. L<perlfunc>.
154 =head2 New Documentation
156 XXX Changes which create B<new> files in F<pod/> go here.
160 XXX Description of the purpose of the new file here
162 =head2 Changes to Existing Documentation
164 We have attempted to update the documentation to reflect the changes
165 listed in this document. If you find any we have missed, send email
166 to L<perlbug@perl.org|mailto:perlbug@perl.org>.
168 XXX Changes which significantly change existing files in F<pod/> go here.
169 However, any changes to F<pod/perldiag.pod> should go in the L</Diagnostics>
172 Additionally, the following selected changes have been made:
180 XXX Description of the change here
186 The following additions or changes have been made to diagnostic output,
187 including warnings and fatal error messages. For the complete list of
188 diagnostic messages, see L<perldiag>.
190 XXX New or changed warnings emitted by the core's C<C> code go here. Also
191 include any changes in L<perldiag> that reconcile it to the C<C> code.
193 =head2 New Diagnostics
195 XXX Newly added diagnostic messages go under here, separated into New Errors
204 XXX L<message|perldiag/"message">
214 XXX L<message|perldiag/"message">
218 =head2 Changes to Existing Diagnostics
220 XXX Changes (i.e. rewording) of diagnostic messages go here
226 XXX Describe change here
230 =head1 Utility Changes
232 XXX Changes to installed programs such as F<perlbug> and F<xsubpp> go here.
233 Most of these are built within the directory F<utils>.
235 [ List utility changes as a =head2 entry for each utility and =item
236 entries for each change
237 Use L<XXX> with program names to get proper documentation linking. ]
249 =head1 Configuration and Compilation
251 XXX Changes to F<Configure>, F<installperl>, F<installman>, and analogous tools
252 go here. Any other changes to the Perl build process should be listed here.
253 However, any platform-specific changes should be listed in the
254 L</Platform Support> section, instead.
256 [ List changes as a =item entry ].
268 XXX Any significant changes to the testing of a freshly built perl should be
269 listed here. Changes which create B<new> files in F<t/> go here as do any
270 large changes to the testing harness (e.g. when parallel testing was added).
271 Changes to existing files in F<t/> aren't worth summarizing, although the bugs
272 that they represent may be covered elsewhere.
274 XXX If there were no significant test changes, say this:
276 Tests were added and changed to reflect the other additions and changes
279 XXX If instead there were significant changes, say this:
281 Tests were added and changed to reflect the other additions and
282 changes in this release. Furthermore, these significant changes were
285 [ List each test improvement as a =item entry ]
295 =head1 Platform Support
297 XXX Any changes to platform support should be listed in the sections below.
299 [ Within the sections, list each platform as a =item entry with specific
300 changes as paragraphs below it. ]
304 XXX List any platforms that this version of perl compiles on, that previous
305 versions did not. These will either be enabled by new files in the F<hints/>
306 directories, or new subdirectories and F<README> files at the top level of the
311 =item XXX-some-platform
317 =head2 Discontinued Platforms
319 XXX List any platforms that this version of perl no longer compiles on.
323 =item XXX-some-platform
329 =head2 Platform-Specific Notes
331 XXX List any changes for specific platforms. This could include configuration
332 and compilation changes or changes in portability/compatibility. However,
333 changes within modules for platforms should generally be listed in the
334 L</Modules and Pragmata> section.
338 =item XXX-some-platform
344 =head1 Internal Changes
346 XXX Changes which affect the interface available to C<XS> code go here. Other
347 significant internal changes for future core maintainers should be noted as
350 [ List each change as a =item entry ]
360 =head1 Selected Bug Fixes
362 XXX Important bug fixes in the core language are summarized here. Bug fixes in
363 files in F<ext/> and F<lib/> are best summarized in L</Modules and Pragmata>.
365 [ List each fix as a =item entry ]
371 List assignment (C<aassign>) could in some rare cases allocate an
372 entry on the mortal stack and leave the entry uninitialized. [perl
377 Attempting to apply an attribute to an C<our> variable where a
378 function of that name already exists could result in a NULL pointer
379 being supplied where an SV was expected, crashing perl. [perl
384 C<split ' '> now correctly handles the argument being split when in the
385 scope of the L<< C<unicode_strings>|feature/"The 'unicode_strings' feature"
386 >> feature. Previously, when a string using the single-byte internal
387 representation contained characters that are whitespace by Unicode rules but
388 not by ASCII rules, it treated those characters as part of fields rather
389 than as field separators. [perl #130907]
393 Several built-in functions previously had bugs that could cause them to
394 write to the internal stack without allocating room for the item being
395 written. In rare situations, this could have led to a crash. These bugs have
396 now been fixed, and if any similar bugs are introduced in future, they will
397 be detected automatically in debugging builds.
401 Using a symbolic ref with postderef syntax as the key in a hash lookup was
402 yielding an assertion failure on debugging builds. [perl #131627]
406 Array and hash variables whose names begin with a caret now admit indexing
407 inside their curlies when interpolated into strings, as in C<<
408 "${^CAPTURE[0]}" >> to index C<@{^CAPTURE}>. [perl #131664]
412 =head1 Known Problems
414 XXX Descriptions of platform agnostic bugs we know we can't fix go here. Any
415 tests that had to be C<TODO>ed for the release would be noted here. Unfixed
416 platform specific bugs also go here.
418 [ List each fix as a =item entry ]
428 =head1 Errata From Previous Releases
434 XXX Add anything here that we forgot to add, or were mistaken about, in
435 the perldelta of a previous release.
441 XXX If any significant core contributor has died, we've added a short obituary
444 =head1 Acknowledgements
446 XXX Generate this with:
448 perl Porting/acknowledgements.pl v5.25.5..HEAD
450 =head1 Reporting Bugs
452 If you find what you think is a bug, you might check the perl bug database
453 at L<https://rt.perl.org/> . There may also be information at
454 L<http://www.perl.org/> , the Perl Home Page.
456 If you believe you have an unreported bug, please run the L<perlbug> program
457 included with your release. Be sure to trim your bug down to a tiny but
458 sufficient test case. Your bug report, along with the output of C<perl -V>,
459 will be sent off to perlbug@perl.org to be analysed by the Perl porting team.
461 If the bug you are reporting has security implications which make it
462 inappropriate to send to a publicly archived mailing list, then see
463 L<perlsec/SECURITY VULNERABILITY CONTACT INFORMATION>
464 for details of how to report the issue.
468 If you wish to thank the Perl 5 Porters for the work we had done in Perl 5,
469 you can do so by running the C<perlthanks> program:
473 This will send an email to the Perl 5 Porters list with your show of thanks.
477 The F<Changes> file for an explanation of how to view exhaustive details on
480 The F<INSTALL> file for how to build Perl.
482 The F<README> file for general stuff.
484 The F<Artistic> and F<Copying> files for copyright information.