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<Carp> has been upgraded from version 1.42 to 1.43.
135 L<Cwd> has been upgraded from version 3.67 to 3.68.
139 L<ExtUtils::CBuilder> has been upgraded from version 0.280225 to 0.280227.
143 L<Time::HiRes> has been upgraded from version 1.9742 to 1.9743.
147 =head2 Removed Modules and Pragmata
159 XXX Changes to files in F<pod/> go here. Consider grouping entries by
160 file and be sure to link to the appropriate page, e.g. L<perlfunc>.
162 =head2 New Documentation
164 XXX Changes which create B<new> files in F<pod/> go here.
168 XXX Description of the purpose of the new file here
170 =head2 Changes to Existing Documentation
172 We have attempted to update the documentation to reflect the changes
173 listed in this document. If you find any we have missed, send email
174 to L<perlbug@perl.org|mailto:perlbug@perl.org>.
176 XXX Changes which significantly change existing files in F<pod/> go here.
177 However, any changes to F<pod/perldiag.pod> should go in the L</Diagnostics>
180 Additionally, the following selected changes have been made:
188 XXX Description of the change here
194 The following additions or changes have been made to diagnostic output,
195 including warnings and fatal error messages. For the complete list of
196 diagnostic messages, see L<perldiag>.
198 XXX New or changed warnings emitted by the core's C<C> code go here. Also
199 include any changes in L<perldiag> that reconcile it to the C<C> code.
201 =head2 New Diagnostics
203 XXX Newly added diagnostic messages go under here, separated into New Errors
212 XXX L<message|perldiag/"message">
222 XXX L<message|perldiag/"message">
226 =head2 Changes to Existing Diagnostics
228 XXX Changes (i.e. rewording) of diagnostic messages go here
234 XXX Describe change here
238 =head1 Utility Changes
240 XXX Changes to installed programs such as F<perlbug> and F<xsubpp> go here.
241 Most of these are built within the directory F<utils>.
243 [ List utility changes as a =head2 entry for each utility and =item
244 entries for each change
245 Use L<XXX> with program names to get proper documentation linking. ]
257 =head1 Configuration and Compilation
259 XXX Changes to F<Configure>, F<installperl>, F<installman>, and analogous tools
260 go here. Any other changes to the Perl build process should be listed here.
261 However, any platform-specific changes should be listed in the
262 L</Platform Support> section, instead.
264 [ List changes as a =item entry ].
276 XXX Any significant changes to the testing of a freshly built perl should be
277 listed here. Changes which create B<new> files in F<t/> go here as do any
278 large changes to the testing harness (e.g. when parallel testing was added).
279 Changes to existing files in F<t/> aren't worth summarizing, although the bugs
280 that they represent may be covered elsewhere.
282 XXX If there were no significant test changes, say this:
284 Tests were added and changed to reflect the other additions and changes
287 XXX If instead there were significant changes, say this:
289 Tests were added and changed to reflect the other additions and
290 changes in this release. Furthermore, these significant changes were
293 [ List each test improvement as a =item entry ]
303 =head1 Platform Support
305 XXX Any changes to platform support should be listed in the sections below.
307 [ Within the sections, list each platform as a =item entry with specific
308 changes as paragraphs below it. ]
312 XXX List any platforms that this version of perl compiles on, that previous
313 versions did not. These will either be enabled by new files in the F<hints/>
314 directories, or new subdirectories and F<README> files at the top level of the
319 =item XXX-some-platform
325 =head2 Discontinued Platforms
327 XXX List any platforms that this version of perl no longer compiles on.
331 =item XXX-some-platform
337 =head2 Platform-Specific Notes
339 XXX List any changes for specific platforms. This could include configuration
340 and compilation changes or changes in portability/compatibility. However,
341 changes within modules for platforms should generally be listed in the
342 L</Modules and Pragmata> section.
346 =item XXX-some-platform
352 =head1 Internal Changes
354 XXX Changes which affect the interface available to C<XS> code go here. Other
355 significant internal changes for future core maintainers should be noted as
358 [ List each change as a =item entry ]
368 =head1 Selected Bug Fixes
370 XXX Important bug fixes in the core language are summarized here. Bug fixes in
371 files in F<ext/> and F<lib/> are best summarized in L</Modules and Pragmata>.
373 [ List each fix as a =item entry ]
379 List assignment (C<aassign>) could in some rare cases allocate an
380 entry on the mortal stack and leave the entry uninitialized. [perl
385 Attempting to apply an attribute to an C<our> variable where a
386 function of that name already exists could result in a NULL pointer
387 being supplied where an SV was expected, crashing perl. [perl
392 C<split ' '> now correctly handles the argument being split when in the
393 scope of the L<< C<unicode_strings>|feature/"The 'unicode_strings' feature"
394 >> feature. Previously, when a string using the single-byte internal
395 representation contained characters that are whitespace by Unicode rules but
396 not by ASCII rules, it treated those characters as part of fields rather
397 than as field separators. [perl #130907]
401 Several built-in functions previously had bugs that could cause them to
402 write to the internal stack without allocating room for the item being
403 written. In rare situations, this could have led to a crash. These bugs have
404 now been fixed, and if any similar bugs are introduced in future, they will
405 be detected automatically in debugging builds.
409 Using a symbolic ref with postderef syntax as the key in a hash lookup was
410 yielding an assertion failure on debugging builds. [perl #131627]
414 Array and hash variables whose names begin with a caret now admit indexing
415 inside their curlies when interpolated into strings, as in C<<
416 "${^CAPTURE[0]}" >> to index C<@{^CAPTURE}>. [perl #131664]
420 =head1 Known Problems
422 XXX Descriptions of platform agnostic bugs we know we can't fix go here. Any
423 tests that had to be C<TODO>ed for the release would be noted here. Unfixed
424 platform specific bugs also go here.
426 [ List each fix as a =item entry ]
436 =head1 Errata From Previous Releases
442 XXX Add anything here that we forgot to add, or were mistaken about, in
443 the perldelta of a previous release.
449 XXX If any significant core contributor has died, we've added a short obituary
452 =head1 Acknowledgements
454 XXX Generate this with:
456 perl Porting/acknowledgements.pl v5.25.5..HEAD
458 =head1 Reporting Bugs
460 If you find what you think is a bug, you might check the perl bug database
461 at L<https://rt.perl.org/> . There may also be information at
462 L<http://www.perl.org/> , the Perl Home Page.
464 If you believe you have an unreported bug, please run the L<perlbug> program
465 included with your release. Be sure to trim your bug down to a tiny but
466 sufficient test case. Your bug report, along with the output of C<perl -V>,
467 will be sent off to perlbug@perl.org to be analysed by the Perl porting team.
469 If the bug you are reporting has security implications which make it
470 inappropriate to send to a publicly archived mailing list, then see
471 L<perlsec/SECURITY VULNERABILITY CONTACT INFORMATION>
472 for details of how to report the issue.
476 If you wish to thank the Perl 5 Porters for the work we had done in Perl 5,
477 you can do so by running the C<perlthanks> program:
481 This will send an email to the Perl 5 Porters list with your show of thanks.
485 The F<Changes> file for an explanation of how to view exhaustive details on
488 The F<INSTALL> file for how to build Perl.
490 The F<README> file for general stuff.
492 The F<Artistic> and F<Copying> files for copyright information.