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.35.1
12 This document describes differences between the 5.35.0 release and the 5.35.1
15 If you are upgrading from an earlier release such as 5.34.0, first read
16 L<perl5350delta>, which describes differences between 5.34.0 and 5.35.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 ]
50 XXX Any deprecated features, syntax, modules etc. should be listed here.
52 =head2 Module removals
54 XXX Remove this section if not applicable.
56 The following modules will be removed from the core distribution in a
57 future release, and will at that time need to be installed from CPAN.
58 Distributions on CPAN which require these modules will need to list them as
61 The core versions of these modules will now issue C<"deprecated">-category
62 warnings to alert you to this fact. To silence these deprecation warnings,
63 install the modules in question from CPAN.
65 Note that these are (with rare exceptions) fine modules that you are encouraged
66 to continue to use. Their disinclusion from core primarily hinges on their
67 necessity to bootstrapping a fully functional, CPAN-capable Perl installation,
68 not usually on concerns over their design.
74 XXX Note that deprecated modules should be listed here even if they are listed
75 as an updated module in the L</Modules and Pragmata> section.
79 [ List each other deprecation as a =head2 entry ]
81 =head1 Performance Enhancements
83 XXX Changes which enhance performance without changing behaviour go here.
84 There may well be none in a stable release.
86 [ List each enhancement as an =item entry ]
96 =head1 Modules and Pragmata
98 XXX All changes to installed files in F<cpan/>, F<dist/>, F<ext/> and F<lib/>
99 go here. If Module::CoreList is updated, generate an initial draft of the
100 following sections using F<Porting/corelist-perldelta.pl>. A paragraph summary
101 for important changes should then be added by hand. In an ideal world,
102 dual-life modules would have a F<Changes> file that could be cribbed.
104 The list of new and updated modules is modified automatically as part of
105 preparing a Perl release, so the only reason to manually add entries here is if
106 you're summarising the important changes in the module update. (Also, if the
107 manually-added details don't match the automatically-generated ones, the
108 release manager will have to investigate the situation carefully.)
110 [ Within each section, list entries as an =item entry ]
112 =head2 New Modules and Pragmata
118 XXX Remove this section if not applicable.
122 =head2 Updated Modules and Pragmata
128 L<File::Copy> has been upgraded from version 2.35 to 2.36.
130 Inode numbers are now compared as strings, so that large inode numbers
131 are correctly distinguished. (GH #18788)
135 L<PathTools|Cwd> has been upgraded from version 3.80 to 3.81.
137 Inodes numbers are now compared as strings, so that large inode numbers
138 are correctly distinguished. (GH #18788)
142 =head2 Removed Modules and Pragmata
154 XXX Changes to files in F<pod/> go here. Consider grouping entries by
155 file and be sure to link to the appropriate page, e.g. L<perlfunc>.
157 =head2 New Documentation
159 XXX Changes which create B<new> files in F<pod/> go here.
163 XXX Description of the purpose of the new file here
165 =head2 Changes to Existing Documentation
167 We have attempted to update the documentation to reflect the changes
168 listed in this document. If you find any we have missed, open an issue
169 at L<https://github.com/Perl/perl5/issues>.
171 XXX Changes which significantly change existing files in F<pod/> go here.
172 However, any changes to F<pod/perldiag.pod> should go in the L</Diagnostics>
175 Additionally, the following selected changes have been made:
183 XXX Description of the change here
189 The following additions or changes have been made to diagnostic output,
190 including warnings and fatal error messages. For the complete list of
191 diagnostic messages, see L<perldiag>.
193 XXX New or changed warnings emitted by the core's C<C> code go here. Also
194 include any changes in L<perldiag> that reconcile it to the C<C> code.
196 =head2 New Diagnostics
198 XXX Newly added diagnostic messages go under here, separated into New Errors
207 XXX L<message|perldiag/"message">
217 XXX L<message|perldiag/"message">
221 =head2 Changes to Existing Diagnostics
223 XXX Changes (i.e. rewording) of diagnostic messages go here
229 L<Can't modify %s in %s|perldiag/"Can't modify %s in %s">
230 (for scalar assignment to C<undef>)
232 Attempting to perform a scalar assignment to C<undef>, for example via
233 C<undef = $foo;>, previously triggered a fatal runtime error with the
234 message "L<Modification of a read-only value attempted|perldiag/"Modification of a read-only value attempted">."
235 It is more helpful to detect such attempted assignments prior to
236 runtime, so they are now compile time errors, resulting in the message
237 "Can't modify undef operator in scalar assignment".
241 XXX Describe change here
245 =head1 Utility Changes
247 XXX Changes to installed programs such as F<perldoc> and F<xsubpp> go here.
248 Most of these are built within the directory F<utils>.
250 [ List utility changes as a =head2 entry for each utility and =item
251 entries for each change
252 Use L<XXX> with program names to get proper documentation linking. ]
264 =head1 Configuration and Compilation
266 XXX Changes to F<Configure>, F<installperl>, F<installman>, and analogous tools
267 go here. Any other changes to the Perl build process should be listed here.
268 However, any platform-specific changes should be listed in the
269 L</Platform Support> section, instead.
271 [ List changes as an =item entry ].
283 XXX Any significant changes to the testing of a freshly built perl should be
284 listed here. Changes which create B<new> files in F<t/> go here as do any
285 large changes to the testing harness (e.g. when parallel testing was added).
286 Changes to existing files in F<t/> aren't worth summarizing, although the bugs
287 that they represent may be covered elsewhere.
289 XXX If there were no significant test changes, say this:
291 Tests were added and changed to reflect the other additions and changes
294 XXX If instead there were significant changes, say this:
296 Tests were added and changed to reflect the other additions and
297 changes in this release. Furthermore, these significant changes were
300 [ List each test improvement as an =item entry ]
310 =head1 Platform Support
312 XXX Any changes to platform support should be listed in the sections below.
314 [ Within the sections, list each platform as an =item entry with specific
315 changes as paragraphs below it. ]
319 XXX List any platforms that this version of perl compiles on, that previous
320 versions did not. These will either be enabled by new files in the F<hints/>
321 directories, or new subdirectories and F<README> files at the top level of the
326 =item XXX-some-platform
332 =head2 Discontinued Platforms
334 XXX List any platforms that this version of perl no longer compiles on.
338 =item XXX-some-platform
344 =head2 Platform-Specific Notes
346 XXX List any changes for specific platforms. This could include configuration
347 and compilation changes or changes in portability/compatibility. However,
348 changes within modules for platforms should generally be listed in the
349 L</Modules and Pragmata> section.
353 =item XXX-some-platform
359 =head1 Internal Changes
361 XXX Changes which affect the interface available to C<XS> code go here. Other
362 significant internal changes for future core maintainers should be noted as
365 [ List each change as an =item entry ]
375 =head1 Selected Bug Fixes
377 XXX Important bug fixes in the core language are summarized here. Bug fixes in
378 files in F<ext/> and F<lib/> are best summarized in L</Modules and Pragmata>.
380 [ List each fix as an =item entry ]
386 utime() now correctly sets errno/C<$!> when called on a closed handle.
390 =head1 Known Problems
392 XXX Descriptions of platform agnostic bugs we know we can't fix go here. Any
393 tests that had to be C<TODO>ed for the release would be noted here. Unfixed
394 platform specific bugs also go here.
396 [ List each fix as an =item entry ]
406 =head1 Errata From Previous Releases
412 XXX Add anything here that we forgot to add, or were mistaken about, in
413 the perldelta of a previous release.
419 Raun "Spider" Boardman (SPIDB on CPAN), author of at least 66 commits to the
420 Perl 5 core distribution between 1996 and 2002, passed away May 24 2021 from
421 complications of COVID. He will be missed.
423 =head1 Acknowledgements
425 XXX Generate this with:
427 perl Porting/acknowledgements.pl v5.35.0..HEAD
429 =head1 Reporting Bugs
431 If you find what you think is a bug, you might check the perl bug database
432 at L<https://github.com/Perl/perl5/issues>. There may also be information at
433 L<http://www.perl.org/>, the Perl Home Page.
435 If you believe you have an unreported bug, please open an issue at
436 L<https://github.com/Perl/perl5/issues>. Be sure to trim your bug down to a
437 tiny but sufficient test case.
439 If the bug you are reporting has security implications which make it
440 inappropriate to send to a public issue tracker, then see
441 L<perlsec/SECURITY VULNERABILITY CONTACT INFORMATION>
442 for details of how to report the issue.
446 If you wish to thank the Perl 5 Porters for the work we had done in Perl 5,
447 you can do so by running the C<perlthanks> program:
451 This will send an email to the Perl 5 Porters list with your show of thanks.
455 The F<Changes> file for an explanation of how to view exhaustive details on
458 The F<INSTALL> file for how to build Perl.
460 The F<README> file for general stuff.
462 The F<Artistic> and F<Copying> files for copyright information.