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.19.3
12 This document describes differences between the 5.19.2 release and the 5.19.3
15 If you are upgrading from an earlier release such as 5.19.1, first read
16 L<perl5192delta>, which describes differences between 5.19.1 and 5.19.2.
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 B<-F> now implies B<-a> and B<-a> implies B<-n>
32 Previously B<-F> without B<-a> was a no-op, and B<-a> without B<-n> or
33 B<-p> was a no-op, with this change, if you supply B<-F> then both
34 B<-a> and B<-n> are implied and if you supply B<-a> then B<-n> is implied.
36 You can still use B<-p> for its extra behaviour. [perl #116190]
40 XXX Any security-related notices go here. In particular, any security
41 vulnerabilities closed should be noted here rather than in the
42 L</Selected Bug Fixes> section.
44 [ List each security issue as a =head2 entry ]
46 =head1 Incompatible Changes
48 XXX For a release on a stable branch, this section aspires to be:
50 There are no changes intentionally incompatible with 5.XXX.XXX
51 If any exist, they are bugs, and we request that you submit a
52 report. See L</Reporting Bugs> below.
54 [ List each incompatible change as a =head2 entry ]
58 XXX Any deprecated features, syntax, modules etc. should be listed here.
60 =head2 Module removals
62 XXX Remove this section if inapplicable.
64 The following modules will be removed from the core distribution in a
65 future release, and will at that time need to be installed from CPAN.
66 Distributions on CPAN which require these modules will need to list them as
69 The core versions of these modules will now issue C<"deprecated">-category
70 warnings to alert you to this fact. To silence these deprecation warnings,
71 install the modules in question from CPAN.
73 Note that these are (with rare exceptions) fine modules that you are encouraged
74 to continue to use. Their disinclusion from core primarily hinges on their
75 necessity to bootstrapping a fully functional, CPAN-capable Perl installation,
76 not usually on concerns over their design.
80 XXX Note that deprecated modules should be listed here even if they are listed
81 as an updated module in the L</Modules and Pragmata> section.
85 [ List each other deprecation as a =head2 entry ]
87 =head1 Performance Enhancements
89 XXX Changes which enhance performance without changing behaviour go here.
90 There may well be none in a stable release.
92 [ List each enhancement as a =item entry ]
102 =head1 Modules and Pragmata
104 XXX All changes to installed files in F<cpan/>, F<dist/>, F<ext/> and F<lib/>
105 go here. If Module::CoreList is updated, generate an initial draft of the
106 following sections using F<Porting/corelist-perldelta.pl>, which prints stub
107 entries to STDOUT. Results can be pasted in place of the '=head2' entries
108 below. A paragraph summary for important changes should then be added by hand.
109 In an ideal world, dual-life modules would have a F<Changes> file that could be
112 [ Within each section, list entries as a =item entry ]
114 =head2 New Modules and Pragmata
124 =head2 Updated Modules and Pragmata
130 L<B> has been upgraded from version 1.44 to 1.45.
132 Calling the C<GV> method on C<B::CV> objects created from a lexical
133 sub would return nonsense, possibly crashing perl. C<GV> now returns
134 C<undef> for lexical subs. [perl #118525]
136 Added the C<NAME_HEK> method to return the name of a lexical sub.
140 L<bignum> has been upgraded from version 0.35 to 0.36.
142 L<bigrat> wasn't correctly updating an internal variable when C<use>d
143 with a C<lib> option.
145 L<Carp> has been upgraded from 1.30 to 1.31
147 L<Carp> now handles objects with string overloads. It also allows objects
148 to specify how they appear in the stack dump with a C<CARP_TRACE> method,
149 and also allows the user to specify their own formatter for objects without
150 C<CARP_TRACE> as well as other references. [perl #92446]
154 L<Compress::Raw::Bzip2> has been upgraded from 2.061 to 2.062.
158 L<Compress::Raw::Zlib> has been upgraded from 2.061 to 2.062.
162 L<Config::Perl::V> has been upgraded from version 0.18 to 0.19.
166 L<Data::Dumper> has been upgraded from version 2.147 to 2.148.
168 The compatbility of the XS implementation with the pure perl version
169 under C<Useqq> has been improved. [perl #118933]
173 L<Devel::Peek> has been upgraded from version 1.12 to 1.13.
175 The C<SvREFCNT_inc()> and C<SvREFCNT_dec()> functions have been
176 removed and C<SvREFCNT()> will now work on non-scalars. [perl #117793]
180 L<Exporter> has been upgraded from version 5.68 to 5.69.
182 L<Exporter> would ignore custom C<$SIG{__WARN__}> handlers in
183 C<Exporter::Heavy>. [perl #39739]
187 The IO-Compress module collection has been upgraded from 2.061 to 2.062.
191 L<IPC::Cmd> has been upgraded from version 0.82 to 0.84.
193 C<run_forked> has various fixes/improvements, L<Socket> is only used where
194 needed and a regression introduced in 0.78 has been fixed.
198 The libnet module collection has been upgraded from version 1.22 to 1.23.
202 L<List::Util> has been upgraded from version 1.27 to 1.30
204 L<List::Util> now includes C<pairgrep>, C<pairmap>, C<pairs>, C<pairkeys>,
205 C<pairvalues> and C<pairfirst> functions that operate on even-sized lists of
210 L<parent> has been upgraded from version 0.225 to 0.226.
214 L<Socket> has been upgraded from version 2.010 to 2.011.
216 Handle FreeBSD (or other platforms) returning shorter AF_UNIX sockaddr
217 structures due to embedded sun_len. [cpan #86613]
221 L<Storable> has been upgraded from version 2.45 to 2.46.
223 Avoid creating temporary objects for STORABLE_attach when they aren't
224 required. [perl #118907]
228 L<Time::Piece> has been upgraded from version 1.21 to 1.22.
232 =head2 Removed Modules and Pragmata
244 XXX Changes to files in F<pod/> go here. Consider grouping entries by
245 file and be sure to link to the appropriate page, e.g. L<perlfunc>.
247 =head2 New Documentation
249 XXX Changes which create B<new> files in F<pod/> go here.
253 XXX Description of the purpose of the new file here
255 =head2 Changes to Existing Documentation
257 XXX Changes which significantly change existing files in F<pod/> go here.
258 However, any changes to F<pod/perldiag.pod> should go in the L</Diagnostics>
261 =head3 L<perlopentut>
267 The C<open> tutorial has been completely rewriten by Tom Christiansen, and now
268 focuses on covering only the basics, rather than providing a comprehensive
269 reference to all things openable. This rewrite came as the result of a
270 vigorous discussion on perl5-porters kicked off by a set of improvements
271 written by Alexander Hartmaier to the existing C<perlopentut>. A "more than
272 you ever wanted to know about C<open>" document may follow in subsequent
279 The following additions or changes have been made to diagnostic output,
280 including warnings and fatal error messages. For the complete list of
281 diagnostic messages, see L<perldiag>.
283 XXX New or changed warnings emitted by the core's C<C> code go here. Also
284 include any changes in L<perldiag> that reconcile it to the C<C> code.
286 =head2 New Diagnostics
288 XXX Newly added diagnostic messages go under here, separated into New Errors
297 XXX L<message|perldiag/"message">
307 XXX L<message|perldiag/"message">
311 =head2 Changes to Existing Diagnostics
313 XXX Changes (i.e. rewording) of diagnostic messages go here
319 XXX Describe change here
323 =head1 Utility Changes
325 XXX Changes to installed programs such as F<perlbug> and F<xsubpp> go here.
326 Most of these are built within the directories F<utils> and F<x2p>.
328 [ List utility changes as a =head3 entry for each utility and =item
329 entries for each change
330 Use L<XXX> with program names to get proper documentation linking. ]
342 =head1 Configuration and Compilation
344 XXX Changes to F<Configure>, F<installperl>, F<installman>, and analogous tools
345 go here. Any other changes to the Perl build process should be listed here.
346 However, any platform-specific changes should be listed in the
347 L</Platform Support> section, instead.
349 [ List changes as a =item entry ].
361 XXX Any significant changes to the testing of a freshly built perl should be
362 listed here. Changes which create B<new> files in F<t/> go here as do any
363 large changes to the testing harness (e.g. when parallel testing was added).
364 Changes to existing files in F<t/> aren't worth summarizing, although the bugs
365 that they represent may be covered elsewhere.
367 [ List each test improvement as a =item entry ]
377 =head1 Platform Support
379 XXX Any changes to platform support should be listed in the sections below.
381 [ Within the sections, list each platform as a =item entry with specific
382 changes as paragraphs below it. ]
386 XXX List any platforms that this version of perl compiles on, that previous
387 versions did not. These will either be enabled by new files in the F<hints/>
388 directories, or new subdirectories and F<README> files at the top level of the
393 =item XXX-some-platform
399 =head2 Discontinued Platforms
401 XXX List any platforms that this version of perl no longer compiles on.
405 =item XXX-some-platform
411 =head2 Platform-Specific Notes
413 XXX List any changes for specific platforms. This could include configuration
414 and compilation changes or changes in portability/compatibility. However,
415 changes within modules for platforms should generally be listed in the
416 L</Modules and Pragmata> section.
420 =item XXX-some-platform
426 =head1 Internal Changes
428 XXX Changes which affect the interface available to C<XS> code go here. Other
429 significant internal changes for future core maintainers should be noted as
432 [ List each change as a =item entry ]
438 C<sv_pos_b2u_flags> has been added to the API. It is similar to
439 C<sv_pos_b2u>, but supports long strings on 64-bit platforms.
443 =head1 Selected Bug Fixes
445 XXX Important bug fixes in the core language are summarized here. Bug fixes in
446 files in F<ext/> and F<lib/> are best summarized in L</Modules and Pragmata>.
448 [ List each fix as a =item entry ]
454 Autovivifying a subroutine stub via C<\&$glob> started causing crashes in
455 Perl 5.18.0 if the $glob was merely a copy of a real glob, i.e., a scalar
456 that had had a glob assigned to it. This has been fixed [perl #119051].
460 On 64-bit platforms C<pos> can now be set to a value higher than 2**31-1
465 Perl used to leak an implementation detail when it came to referencing the
466 return values of certain operators. C<for ($a+$b) { warn \$_; warn \$_ }>
467 used to display two different memory addresses, because the C<\> operator
468 was copying the variable. Under threaded builds, it would also happen for
469 constants (C<for(1) { ... }>). This has been fixed [perl #21979, #78194,
470 #89188, #109746, #114838, #115388].
474 The range operator C<..> was returning the same modifiable scalars with
475 each call, unless it was the only thing in a C<foreach> loop header. This
476 meant that changes to values within the list returned would be visible the
477 next time the operator was executed [perl #3105].
481 =head1 Known Problems
483 XXX Descriptions of platform agnostic bugs we know we can't fix go here. Any
484 tests that had to be C<TODO>ed for the release would be noted here. Unfixed
485 platform specific bugs also go here.
487 [ List each fix as a =item entry ]
499 XXX If any significant core contributor has died, we've added a short obituary
502 =head1 Acknowledgements
504 XXX Generate this with:
506 perl Porting/acknowledgements.pl v5.19.2..HEAD
508 =head1 Reporting Bugs
510 If you find what you think is a bug, you might check the articles recently
511 posted to the comp.lang.perl.misc newsgroup and the perl bug database at
512 http://rt.perl.org/perlbug/ . There may also be information at
513 http://www.perl.org/ , the Perl Home Page.
515 If you believe you have an unreported bug, please run the L<perlbug> program
516 included with your release. Be sure to trim your bug down to a tiny but
517 sufficient test case. Your bug report, along with the output of C<perl -V>,
518 will be sent off to perlbug@perl.org to be analysed by the Perl porting team.
520 If the bug you are reporting has security implications, which make it
521 inappropriate to send to a publicly archived mailing list, then please send it
522 to perl5-security-report@perl.org. This points to a closed subscription
523 unarchived mailing list, which includes all the core committers, who will be
524 able to help assess the impact of issues, figure out a resolution, and help
525 co-ordinate the release of patches to mitigate or fix the problem across all
526 platforms on which Perl is supported. Please only use this address for
527 security issues in the Perl core, not for modules independently distributed on
532 The F<Changes> file for an explanation of how to view exhaustive details on
535 The F<INSTALL> file for how to build Perl.
537 The F<README> file for general stuff.
539 The F<Artistic> and F<Copying> files for copyright information.