4 This has been completed up to d54f8cf785.
8 [ this is a template for a new perldelta file. Any text flagged as
9 XXX needs to be processed before release. ]
11 perldelta - what is new for perl v5.13.8
15 This document describes differences between the 5.13.8 release and
18 If you are upgrading from an earlier release such as 5.13.6, first read
19 L<perl5137delta>, which describes differences between 5.13.6 and
24 XXX Any important notices here
26 =head1 Core Enhancements
28 XXX New core language features go here. Summarise user-visible core language
29 enhancements. Particularly prominent performance optimisations could go
30 here, but most should go in the L</Performance Enhancements> section.
32 [ List each enhancement as a =head2 entry ]
34 =head2 C<-d:-foo> calls C<Devel::foo::unimport>
36 The syntax C<-dI<B<:>foo>> was extended in 5.6.1 to make C<-dI<:fooB<=bar>>>
37 equivalent to C<-MDevel::foo=bar>, which expands
38 internally to C<use Devel::foo 'bar';>.
39 F<perl> now allows prefixing the module name with C<->, with the same
40 semantics as C<-M>, I<i.e.>
46 Equivalent to C<-M-Devel::foo>, expands to
47 C<no Devel::foo;>, calls C<< Devel::foo->unimport() >>
52 Equivalent to C<-M-Devel::foo=bar>, expands to C<no Devel::foo 'bar';>,
53 calls C<< Devel::foo->unimport('bar') >> if the method exists.
57 This is particularly useful to suppresses the default actions of a
58 C<Devel::*> module's C<import> method whilst still loading it for debugging.
62 XXX Any security-related notices go here. In particular, any security
63 vulnerabilities closed should be noted here rather than in the
64 L</Selected Bug Fixes> section.
66 [ List each security issue as a =head2 entry ]
68 =head1 Incompatible Changes
70 =head2 Attempting to use C<:=> as an empty attribute list is now a syntax error
72 Previously C<my $pi := 4;> was exactly equivalent to C<my $pi : = 4;>,
73 with the C<:> being treated as the start of an attribute list, ending before
74 the C<=>. The use of C<:=> to mean C<: => was deprecated in 5.12.0, and is now
75 a syntax error. This will allow the future use of C<:=> as a new token.
77 We find no Perl 5 code on CPAN using this construction, outside the core's
78 tests for it, so we believe that this change will have very little impact on
81 If it is absolutely necessary to have empty attribute lists (for example,
82 because of a code generator) then avoid the error by adding a space before
87 XXX Any deprecated features, syntax, modules etc. should be listed here.
88 In particular, deprecated modules should be listed here even if they are
89 listed as an updated module in the L</Modules and Pragmata> section.
91 [ List each deprecation as a =head2 entry ]
93 =head2 C<?PATTERN?> is deprecated
95 C<?PATTERN?> (without the initial m) has been deprecated and now produces
98 =head2 C<sv_compile_2op> is now deprecated
100 The C<sv_compile_2op> is now deprecated, and will be removed. Searches suggest
101 that nothing on CPAN is using it, so this should have zero impact.
103 It attempted to provide an API to compile code down to an optree, but failed
104 to bind correctly to lexicals in the enclosing scope. It's not possible to
105 fix this problem within the constraints of its parameters and return value.
107 =head1 Performance Enhancements
109 XXX Changes which enhance performance without changing behaviour go here. There
110 may well be none in a stable release.
112 [ List each enhancement as a =item entry ]
122 =head1 Modules and Pragmata
124 XXX All changes to installed files in F<cpan/>, F<dist/>, F<ext/> and F<lib/>
125 go here. If Module::CoreList is updated, generate an initial draft of the
126 following sections using F<Porting/corelist-perldelta.pl>, which prints stub
127 entries to STDOUT. Results can be pasted in place of the '=head2' entries
128 below. A paragraph summary for important changes should then be added by hand.
129 In an ideal world, dual-life modules would have a F<Changes> file that could be
132 [ Within each section, list entries as a =item entry ]
134 =head2 New Modules and Pragmata
144 =head2 Updated Modules and Pragmata
150 C<IPC::Cmd> has been upgraded from 0.64 to 0.66
152 Resolves an issue with splitting Win32 command lines
153 and documentation enhancements.
157 C<MIME::Base64> has been upgraded from 3.10 to 3.13
159 Now provides encode_base64url and decode_base64url functions to process
160 the base64 scheme for "URL applications".
164 C<overload> has been upgraded from 1.11 to 1.12.
168 C<PerlIO::scalar> has been upgraded from 0.10 to 0.11.
170 A C<read> after a C<seek> beyond the end of the string no longer thinks it
172 L<[perl #78716]|http://rt.perl.org/rt3/Public/Bug/Display.html?id=78716>.
176 C<Socket> has been upgraded from 1.91 to 1.92.
178 It has several new functions for handling IPv6 addresses.
182 C<Time::HiRes> has been upgraded from 1.9721 to 1.9721_01.
186 C<Unicode::Collate> has been upgraded from 0.67 to 0.68
190 C<Unicode::UCD> has been upgraded from 0.29 to 0.30.
194 C<version> has been upgraded from 0.82 to 0.86.
198 =head2 Removed Modules and Pragmata
210 XXX Changes to files in F<pod/> go here. Consider grouping entries by
211 file and be sure to link to the appropriate page, e.g. L<perlfunc>.
213 =head2 New Documentation
215 XXX Changes which create B<new> files in F<pod/> go here.
219 XXX Description of the purpose of the new file here
221 =head2 Changes to Existing Documentation
223 XXX Changes which significantly change existing files in F<pod/> go here.
224 However, any changes to F<pod/perldiag.pod> should go in the L</Diagnostics>
233 XXX Description of the change here
239 The following additions or changes have been made to diagnostic output,
240 including warnings and fatal error messages. For the complete list of
241 diagnostic messages, see L<perldiag>.
243 XXX New or changed warnings emitted by the core's C<C> code go here. Also
244 include any changes in L<perldiag> that reconcile it to the C<C> code.
246 [ Within each section, list entries as a =item entry ]
248 =head2 New Diagnostics
250 XXX Newly added diagnostic messages go here
260 =head2 Changes to Existing Diagnostics
262 XXX Changes (i.e. rewording) of diagnostic messages go here
272 =head1 Utility Changes
274 XXX Changes to installed programs such as F<perlbug> and F<xsubpp> go
275 here. Most of these are built within the directories F<utils> and F<x2p>.
277 [ List utility changes as a =head3 entry for each utility and =item
278 entries for each change
279 Use L<XXX> with program names to get proper documentation linking. ]
291 =head1 Configuration and Compilation
293 XXX Changes to F<Configure>, F<installperl>, F<installman>, and analogous tools
294 go here. Any other changes to the Perl build process should be listed here.
295 However, any platform-specific changes should be listed in the
296 L</Platform Support> section, instead.
298 [ List changes as a =item entry ].
310 XXX Any significant changes to the testing of a freshly built perl should be
311 listed here. Changes which create B<new> files in F<t/> go here as do any
312 large changes to the testing harness (e.g. when parallel testing was added).
313 Changes to existing files in F<t/> aren't worth summarising, although the bugs
314 that they represent may be covered elsewhere.
316 [ List each test improvement as a =item entry ]
326 =head1 Platform Support
328 XXX Any changes to platform support should be listed in the sections below.
330 [ Within the sections, list each platform as a =item entry with specific
331 changes as paragraphs below it. ]
335 XXX List any platforms that this version of perl compiles on, that previous
336 versions did not. These will either be enabled by new files in the F<hints/>
337 directories, or new subdirectories and F<README> files at the top level of the
342 =item XXX-some-platform
348 =head2 Discontinued Platforms
350 XXX List any platforms that this version of perl no longer compiles on.
354 =item XXX-some-platform
360 =head2 Platform-Specific Notes
362 XXX List any changes for specific platforms. This could include configuration
363 and compilation changes or changes in portability/compatibility. However,
364 changes within modules for platforms should generally be listed in the
365 L</Modules and Pragmata> section.
369 =item XXX-some-platform
375 =head1 Internal Changes
377 XXX Changes which affect the interface available to C<XS> code go here.
378 Other significant internal changes for future core maintainers should
381 [ List each test improvement as a =item entry ]
391 =head1 Selected Bug Fixes
393 XXX Important bug fixes in the core language are summarised here.
394 Bug fixes in files in F<ext/> and F<lib/> are best summarised in
395 L</Modules and Pragmata>.
397 [ List each fix as a =item entry ]
403 C<BEGIN {require 5.12.0}> now behaves as documented, rather than behaving
404 identically to C<use 5.12.0;>. Previously, C<require> in a C<BEGIN> block
405 was erroneously executing the C<use feature ':5.12.0'> and
406 C<use strict; use warnings;> behaviour, which only C<use> was documented to
408 L<[perl #69050]|http://rt.perl.org/rt3/Public/Bug/Display.html?id=69050>.
413 L<[perl #69050]|http://rt.perl.org/rt3/Public/Bug/Display.html?id=69050>,
414 C<use 6> and C<no 5> no longer leak memory.
418 C<eval "BEGIN{die}"> no longer leaks memory on non-threaded builds.
422 PerlIO no longer crashes when called recursively, e.g., from a signal
423 handler. Now it just leaks memory
424 L<[perl #75556]|http://rt.perl.org/rt3/Public/Bug/Display.html?id=75556>.
428 Defining a constant with the same name as one of perl's special blocks
429 (e.g., INIT) stopped working in 5.12.0, but has now been fixed
430 L<[perl #78634]|http://rt.perl.org/rt3/Public/Bug/Display.html?id=78634>.
434 A reference to a literal value used as a hash key (C<$hash{\"foo"}>) used
435 to be stringified, even if the hash was tied
436 L<[perl #79178]|http://rt.perl.org/rt3/Public/Bug/Display.html?id=79178>.
440 =head1 Known Problems
442 XXX Descriptions of platform agnostic bugs we know we can't fix go here. Any
443 tests that had to be C<TODO>ed for the release would be noted here, unless
444 they were specific to a particular platform (see below).
446 This is a list of some significant unfixed bugs, which are regressions
447 from either 5.XXX.XXX or 5.XXX.XXX.
449 [ List each fix as a =item entry ]
455 A number of bugs with regular expression bracketed character classes
456 have been fixed, mostly having to do with matching characters in the
457 non-ASCII Latin-1 range.
463 XXX If any significant core contributor has died, we've added a short obituary
466 =head1 Acknowledgements
468 XXX The list of people to thank goes here.
470 =head1 Reporting Bugs
472 If you find what you think is a bug, you might check the articles
473 recently posted to the comp.lang.perl.misc newsgroup and the perl
474 bug database at http://rt.perl.org/perlbug/ . There may also be
475 information at http://www.perl.org/ , the Perl Home Page.
477 If you believe you have an unreported bug, please run the L<perlbug>
478 program included with your release. Be sure to trim your bug down
479 to a tiny but sufficient test case. Your bug report, along with the
480 output of C<perl -V>, will be sent off to perlbug@perl.org to be
481 analysed by the Perl porting team.
483 If the bug you are reporting has security implications, which make it
484 inappropriate to send to a publicly archived mailing list, then please send
485 it to perl5-security-report@perl.org. This points to a closed subscription
486 unarchived mailing list, which includes all the core committers, who be able
487 to help assess the impact of issues, figure out a resolution, and help
488 co-ordinate the release of patches to mitigate or fix the problem across all
489 platforms on which Perl is supported. Please only use this address for
490 security issues in the Perl core, not for modules independently
495 The F<Changes> file for an explanation of how to view exhaustive details
498 The F<INSTALL> file for how to build Perl.
500 The F<README> file for general stuff.
502 The F<Artistic> and F<Copying> files for copyright information.