5 [ this is a template for a new perldelta file. Any text flagged as
6 XXX needs to be processed before release. ]
8 perldelta - what is new for perl v5.13.6
12 This document describes differences between the 5.13.5 release and
15 If you are upgrading from an earlier release such as 5.13.4, first read
16 L<perl5135delta>, which describes differences between 5.13.4 and
21 XXX Any important notices here
23 =head1 Core Enhancements
25 XXX New core language features go here. Summarise user-visible core language
26 enhancements. Particularly prominent performance optimisations could go
27 here, but most should go in the L</Performance Enhancements> section.
29 [ List each enhancement as a =head2 entry ]
31 =head2 C<(?^...)> regex construct added to signify default modifiers
33 A caret (also called a "cirumflex accent") C<"^"> immediately following
34 a C<"(?"> in a regular expression now means that the subexpression is to
35 not inherit the surrounding modifiers such as C</i>, but to revert to the
36 Perl defaults. Any modifiers following the caret override the defaults.
38 The stringification of regular expressions now uses this notation. The
39 main purpose of this is to allow tests that rely on the stringification
40 to not have to change when new modifiers are added. See
41 L<perlre/Extended Patterns>.
45 XXX Any security-related notices go here. In particular, any security
46 vulnerabilities closed should be noted here rather than in the
47 L</Selected Bug Fixes> section.
49 [ List each security issue as a =head2 entry ]
51 =head1 Incompatible Changes
53 =head2 Stringification of regexes has changed
55 Default regular expression modifiers are now notated by using
56 C<(?^...)>. Code relying on the old stringification will fail. The
57 purpose of this is so that when new modifiers are added, such code will
58 not have to change, as the stringification will automatically
59 incorporate the new modifiers.
61 Code that needs to work properly with both old- and new-style regexes
62 can use something like the following:
64 # Accept both old and new-style stringification
65 my $modifiers = (qr/foobar/ =~ /\Q(?^/) ? '^' : '-xism';
67 And then use C<$modifiers> instead of C<-xism>.
69 [ List each incompatible change as a =head2 entry ]
73 XXX Any deprecated features, syntax, modules etc. should be listed here.
74 In particular, deprecated modules should be listed here even if they are
75 listed as an updated module in the L</Modules and Pragmata> section.
77 [ List each deprecation as a =head2 entry ]
79 =head1 Performance Enhancements
81 XXX Changes which enhance performance without changing behaviour go here. There
82 may well be none in a stable release.
84 [ List each enhancement as a =item entry ]
94 =head1 Modules and Pragmata
96 XXX All changes to installed files in F<cpan/>, F<dist/>, F<ext/> and F<lib/>
97 go here. If Module::CoreList is updated, generate an initial draft of the
98 following sections using F<Porting/corelist-perldelta.pl>, which prints stub
99 entries to STDOUT. Results can be pasted in place of the '=head2' entries
100 below. A paragraph summary for important changes should then be added by hand.
101 In an ideal world, dual-life modules would have a F<Changes> file that could be
104 [ Within each section, list entries as a =item entry ]
106 =head2 New Modules and Pragmata
116 =head2 Updated Modules and Pragmata
122 C<NEXT> has been upgraded from version 0.64 to 0.65.
126 C<PathTools> has been upgraded from version 3.31_01 to 3.33.
130 C<Unicode::Normalize> has been upgraded from version 1.06 to 1.07
134 =head2 Removed Modules and Pragmata
146 XXX Changes to files in F<pod/> go here. Consider grouping entries by
147 file and be sure to link to the appropriate page, e.g. L<perlfunc>.
149 =head2 New Documentation
151 XXX Changes which create B<new> files in F<pod/> go here.
155 XXX Description of the purpose of the new file here
157 =head2 Changes to Existing Documentation
159 XXX Changes which significantly change existing files in F<pod/> go here.
160 However, any changes to F<pod/perldiag.pod> should go in the L</Diagnostics>
169 XXX Description of the change here
175 The following additions or changes have been made to diagnostic output,
176 including warnings and fatal error messages. For the complete list of
177 diagnostic messages, see L<perldiag>.
179 XXX New or changed warnings emitted by the core's C<C> code go here. Also
180 include any changes in L<perldiag> that reconcile it to the C<C> code.
182 [ Within each section, list entries as a =item entry ]
184 =head2 New Diagnostics
186 XXX Newly added diagnostic messages go here
196 =head2 Changes to Existing Diagnostics
198 XXX Changes (i.e. rewording) of diagnostic messages go here
208 =head1 Utility Changes
210 XXX Changes to installed programs such as F<perlbug> and F<xsubpp> go
211 here. Most of these are built within the directories F<utils> and F<x2p>.
213 [ List utility changes as a =head3 entry for each utility and =item
214 entries for each change
215 Use L<XXX> with program names to get proper documentation linking. ]
227 =head1 Configuration and Compilation
229 XXX Changes to F<Configure>, F<installperl>, F<installman>, and analogous tools
230 go here. Any other changes to the Perl build process should be listed here.
231 However, any platform-specific changes should be listed in the
232 L</Platform Support> section, instead.
234 [ List changes as a =item entry ].
246 XXX Any significant changes to the testing of a freshly built perl should be
247 listed here. Changes which create B<new> files in F<t/> go here as do any
248 large changes to the testing harness (e.g. when parallel testing was added).
249 Changes to existing files in F<t/> aren't worth summarising, although the bugs
250 that they represent may be covered elsewhere.
252 [ List each test improvement as a =item entry ]
262 =head1 Platform Support
264 XXX Any changes to platform support should be listed in the sections below.
266 [ Within the sections, list each platform as a =item entry with specific
267 changes as paragraphs below it. ]
271 XXX List any platforms that this version of perl compiles on, that previous
272 versions did not. These will either be enabled by new files in the F<hints/>
273 directories, or new subdirectories and F<README> files at the top level of the
278 =item XXX-some-platform
284 =head2 Discontinued Platforms
286 XXX List any platforms that this version of perl no longer compiles on.
290 =item XXX-some-platform
296 =head2 Platform-Specific Notes
298 XXX List any changes for specific platforms. This could include configuration
299 and compilation changes or changes in portability/compatibility. However,
300 changes within modules for platforms should generally be listed in the
301 L</Modules and Pragmata> section.
305 =item XXX-some-platform
311 =head1 Internal Changes
313 XXX Changes which affect the interface available to C<XS> code go here.
314 Other significant internal changes for future core maintainers should
317 [ List each test improvement as a =item entry ]
327 =head1 Selected Bug Fixes
329 XXX Important bug fixes in the core language are summarised here.
330 Bug fixes in files in F<ext/> and F<lib/> are best summarised in
331 L</Modules and Pragmata>.
333 [ List each fix as a =item entry ]
339 A regular expression match in the right-hand side of a substitution
340 (C<s///>) that is in the same scope will no longer cause match variables to
341 have the wrong values on subsequent iterations. This can happen when an
342 array or hash subscript is interpolated in the right-hand side, as in
343 C<s|(.)|@a{ print($1), /./ }|g>
344 L<[perl #19078]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=19078>.
348 Constant-folding used to cause
350 $text =~ ( 1 ? /phoo/ : /bear/)
356 at compile time. Now it correctly matches against C<$_>
357 L<[perl #20444]|http://rt.perl.org/rt3//Public/Bug/Display.html?id=20444>.
361 =head1 Known Problems
363 XXX Descriptions of platform agnostic bugs we know we can't fix go here. Any
364 tests that had to be C<TODO>ed for the release would be noted here, unless
365 they were specific to a particular platform (see below).
367 This is a list of some significant unfixed bugs, which are regressions
368 from either 5.XXX.XXX or 5.XXX.XXX.
370 [ List each fix as a =item entry ]
382 XXX If any significant core contributor has died, we've added a short obituary
385 =head1 Acknowledgements
387 XXX The list of people to thank goes here.
389 =head1 Reporting Bugs
391 If you find what you think is a bug, you might check the articles
392 recently posted to the comp.lang.perl.misc newsgroup and the perl
393 bug database at http://rt.perl.org/perlbug/ . There may also be
394 information at http://www.perl.org/ , the Perl Home Page.
396 If you believe you have an unreported bug, please run the B<perlbug>
397 program included with your release. Be sure to trim your bug down
398 to a tiny but sufficient test case. Your bug report, along with the
399 output of C<perl -V>, will be sent off to perlbug@perl.org to be
400 analysed by the Perl porting team.
402 If the bug you are reporting has security implications, which make it
403 inappropriate to send to a publicly archived mailing list, then please send
404 it to perl5-security-report@perl.org. This points to a closed subscription
405 unarchived mailing list, which includes all the core committers, who be able
406 to help assess the impact of issues, figure out a resolution, and help
407 co-ordinate the release of patches to mitigate or fix the problem across all
408 platforms on which Perl is supported. Please only use this address for
409 security issues in the Perl core, not for modules independently
414 The F<Changes> file for an explanation of how to view exhaustive details
417 The F<INSTALL> file for how to build Perl.
419 The F<README> file for general stuff.
421 The F<Artistic> and F<Copying> files for copyright information.