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.1
12 This document describes differences between the 5.27.0 release and the 5.27.1
15 If you are upgrading from an earlier release such as 5.26.0, first read
16 L<perl5270delta>, which describes differences between 5.26.0 and 5.27.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 Comma-less variable lists in formats are no longer allowed
50 Omitting the commas between variables passed to formats is no longer
51 allowed. This has been deprecated since perl 5.000.
53 =head2 The C<:locked> and C<:unique> attributes have been removed
55 These have been no-ops and deprecated since perl 5.12 and 5.10,
60 XXX Any deprecated features, syntax, modules etc. should be listed here.
62 =head2 Some uses of unescaped C<"{"> are no longer fatal
64 Perl 5.26.0 fatalized some uses of an unescaped left brace, but an
65 exception was made at the last minute, specifically crafted to be a
66 minimal change to allow GNU Autoconf to work. This code is heavily
67 depended upon, and continues to use the deprecated usage. Its use of an
68 unescaped left brace is one where we have no intention of repurposing
69 C<"{"> to be something other than itself.
71 That exception is now generalized to include various other such cases
72 where the C<"{"> will not be repurposed. This is to get real experience
73 with this more complicated change now, in case we need to issue a dot
74 release if we find other things like Autoconf that are important to work
77 Note that these uses continue to raise a deprecation message.
79 =head2 Module removals
81 XXX Remove this section if inapplicable.
83 The following modules will be removed from the core distribution in a
84 future release, and will at that time need to be installed from CPAN.
85 Distributions on CPAN which require these modules will need to list them as
88 The core versions of these modules will now issue C<"deprecated">-category
89 warnings to alert you to this fact. To silence these deprecation warnings,
90 install the modules in question from CPAN.
92 Note that these are (with rare exceptions) fine modules that you are encouraged
93 to continue to use. Their disinclusion from core primarily hinges on their
94 necessity to bootstrapping a fully functional, CPAN-capable Perl installation,
95 not usually on concerns over their design.
101 XXX Note that deprecated modules should be listed here even if they are listed
102 as an updated module in the L</Modules and Pragmata> section.
106 [ List each other deprecation as a =head2 entry ]
108 =head1 Performance Enhancements
110 XXX Changes which enhance performance without changing behaviour go here.
111 There may well be none in a stable release.
113 [ List each enhancement as a =item entry ]
123 =head1 Modules and Pragmata
125 XXX All changes to installed files in F<cpan/>, F<dist/>, F<ext/> and F<lib/>
126 go here. If Module::CoreList is updated, generate an initial draft of the
127 following sections using F<Porting/corelist-perldelta.pl>. A paragraph summary
128 for important changes should then be added by hand. In an ideal world,
129 dual-life modules would have a F<Changes> file that could be cribbed.
131 [ Within each section, list entries as a =item entry ]
133 =head2 New Modules and Pragmata
143 =head2 Updated Modules and Pragmata
149 L<XXX> has been upgraded from version A.xx to B.yy.
153 =head2 Removed Modules and Pragmata
165 XXX Changes to files in F<pod/> go here. Consider grouping entries by
166 file and be sure to link to the appropriate page, e.g. L<perlfunc>.
168 =head2 New Documentation
170 XXX Changes which create B<new> files in F<pod/> go here.
174 XXX Description of the purpose of the new file here
176 =head2 Changes to Existing Documentation
178 XXX Changes which significantly change existing files in F<pod/> go here.
179 However, any changes to F<pod/perldiag.pod> should go in the L</Diagnostics>
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 [ List each test improvement as a =item entry ]
292 =head1 Platform Support
294 XXX Any changes to platform support should be listed in the sections below.
296 [ Within the sections, list each platform as a =item entry with specific
297 changes as paragraphs below it. ]
301 XXX List any platforms that this version of perl compiles on, that previous
302 versions did not. These will either be enabled by new files in the F<hints/>
303 directories, or new subdirectories and F<README> files at the top level of the
308 =item XXX-some-platform
314 =head2 Discontinued Platforms
316 XXX List any platforms that this version of perl no longer compiles on.
320 =item XXX-some-platform
326 =head2 Platform-Specific Notes
328 XXX List any changes for specific platforms. This could include configuration
329 and compilation changes or changes in portability/compatibility. However,
330 changes within modules for platforms should generally be listed in the
331 L</Modules and Pragmata> section.
335 =item XXX-some-platform
341 =head1 Internal Changes
343 XXX Changes which affect the interface available to C<XS> code go here. Other
344 significant internal changes for future core maintainers should be noted as
347 [ List each change as a =item entry ]
353 The C<PL_statbuf> interpreter variable has been removed.
357 =head1 Selected Bug Fixes
359 XXX Important bug fixes in the core language are summarized here. Bug fixes in
360 files in F<ext/> and F<lib/> are best summarized in L</Modules and Pragmata>.
362 [ List each fix as a =item entry ]
372 =head1 Known Problems
374 XXX Descriptions of platform agnostic bugs we know we can't fix go here. Any
375 tests that had to be C<TODO>ed for the release would be noted here. Unfixed
376 platform specific bugs also go here.
378 [ List each fix as a =item entry ]
388 =head1 Errata From Previous Releases
394 XXX Add anything here that we forgot to add, or were mistaken about, in
395 the perldelta of a previous release.
401 XXX If any significant core contributor has died, we've added a short obituary
404 =head1 Acknowledgements
406 XXX Generate this with:
408 perl Porting/acknowledgements.pl v5.25.5..HEAD
410 =head1 Reporting Bugs
412 If you find what you think is a bug, you might check the perl bug database
413 at L<https://rt.perl.org/> . There may also be information at
414 L<http://www.perl.org/> , the Perl Home Page.
416 If you believe you have an unreported bug, please run the L<perlbug> program
417 included with your release. Be sure to trim your bug down to a tiny but
418 sufficient test case. Your bug report, along with the output of C<perl -V>,
419 will be sent off to perlbug@perl.org to be analysed by the Perl porting team.
421 If the bug you are reporting has security implications which make it
422 inappropriate to send to a publicly archived mailing list, then see
423 L<perlsec/SECURITY VULNERABILITY CONTACT INFORMATION>
424 for details of how to report the issue.
428 If you wish to thank the Perl 5 Porters for the work we had done in Perl 5,
429 you can do so by running the C<perlthanks> program:
433 This will send an email to the Perl 5 Porters list with your show of thanks.
437 The F<Changes> file for an explanation of how to view exhaustive details on
440 The F<INSTALL> file for how to build Perl.
442 The F<README> file for general stuff.
444 The F<Artistic> and F<Copying> files for copyright information.