4 This has been completed up to 3ea0c5818 except for:
5 a1da11a30dfa4f3543dcab00834ff535202f5085 (GNU/Hurd hints)
9 [ this is a template for a new perldelta file. Any text flagged as
10 XXX needs to be processed before release. ]
12 perldelta - what is new for perl v5.15.5
16 This document describes differences between the 5.15.4 release and
19 If you are upgrading from an earlier release such as 5.15.3, first read
20 L<perl5154delta>, which describes differences between 5.15.3 and
25 XXX Any important notices here
27 =head1 Core Enhancements
29 XXX New core language features go here. Summarise user-visible core language
30 enhancements. Particularly prominent performance optimisations could go
31 here, but most should go in the L</Performance Enhancements> section.
35 The C<$[> variable is back again, but is now implemented as a module, so
36 programs that do not mention it (i.e., most of them), will not incur any
37 run-time penalty. It is disabled in the scope of C<use v5.16>.
39 XXX That last sentence is not true yet.
41 The new implementation has some bug fixes. See L<arybase>.
43 =head2 new dot feature
45 C<use feature 'dot'> tells the compiler to accept . everywhere it would
46 normally accept -> and to accept ~ as concatenation.
50 XXX Any security-related notices go here. In particular, any security
51 vulnerabilities closed should be noted here rather than in the
52 L</Selected Bug Fixes> section.
54 [ List each security issue as a =head2 entry ]
56 =head1 Incompatible Changes
58 XXX For a release on a stable branch, this section aspires to be:
60 There are no changes intentionally incompatible with 5.XXX.XXX
61 If any exist, they are bugs and reports are welcome.
63 [ List each incompatible change as a =head2 entry ]
67 XXX Any deprecated features, syntax, modules etc. should be listed here.
68 In particular, deprecated modules should be listed here even if they are
69 listed as an updated module in the L</Modules and Pragmata> section.
71 [ List each deprecation as a =head2 entry ]
73 =head1 Performance Enhancements
75 XXX Changes which enhance performance without changing behaviour go here. There
76 may well be none in a stable release.
78 [ List each enhancement as a =item entry ]
84 Due to changes in L<File::Glob>, Perl's C<glob> function and its
85 C<< <...> >> equivalent are now much faster. The splitting of the pattern
86 into words has been rewritten in C, resulting in speed-ups of 20% in some
89 This does not affect VMS, as it does not use File::Glob.
93 =head1 Modules and Pragmata
95 XXX All changes to installed files in F<cpan/>, F<dist/>, F<ext/> and F<lib/>
96 go here. If Module::CoreList is updated, generate an initial draft of the
97 following sections using F<Porting/corelist-perldelta.pl>, which prints stub
98 entries to STDOUT. Results can be pasted in place of the '=head2' entries
99 below. A paragraph summary for important changes should then be added by hand.
100 In an ideal world, dual-life modules would have a F<Changes> file that could be
103 [ Within each section, list entries as a =item entry ]
105 =head2 New Modules and Pragmata
111 L<arybase> -- this new module implements the C<$[> variable.
115 =head2 Updated Modules and Pragmata
121 L<Archive::Extract> has been upgraded from version 0.56 to version 0.58.
125 L<B::Deparse> has been upgraded from version 1.08 to 1.08.
127 It now correctly deparses C<CORE::do> and C<CORE::glob>.
131 L<CPANPLUS::Dist::Build> has been upgraded from version 0.58 to version 0.60.
135 L<ExtUtils::MakeMaker> has been upgraded from version 6.61_01 to version 6.63_01.
139 L<File::Glob> has been upgrade from version 1.13 to 1.14.
141 It has a new C<:bsd_glob> export tag, intended to replace C<:glob>. Like
142 C<:glob> it overrides C<glob> with a function that does not split the glob
143 pattern into words, but, unlike C<:glob>, it iterates properly in scalar
144 context, instead of returning the last file.
146 There are other changes affecting Perl's own C<glob> operator (which uses
147 File::Glob internally, except on VMS). See L</Performance Enhancements>
148 and L</Selected Bug Fixes>.
152 L<HTTP::Tiny> has been upgraded from version 0.013 to version 0.016.
154 Adds additional shorthand methods for all common HTTP verbs,
155 a C<post_form()> method for POST-ing x-www-form-urlencoded data and
156 a C<www_form_urlencode()> utility method.
160 L<perlfaq> has been upgraded from version 5.0150035 to version 5.0150036.
164 L<Socket> as been upgraded from version 1.94_01 to 1.94_02.
166 It has new functions and constants for handling IPv6 sockets:
182 L<Unicode::Collate> has been upgraded from version 0.80 to version 0.81.
184 Locales updated to CLDR 2.0: mk, mt, nb, nn, ro, ru.
185 Newly supported locales: ml, mr, or, pa.
189 =head2 Removed Modules and Pragmata
201 XXX Changes to files in F<pod/> go here. Consider grouping entries by
202 file and be sure to link to the appropriate page, e.g. L<perlfunc>.
204 =head2 New Documentation
206 XXX Changes which create B<new> files in F<pod/> go here.
210 XXX Description of the purpose of the new file here
212 =head2 Changes to Existing Documentation
214 XXX Changes which significantly change existing files in F<pod/> go here.
215 However, any changes to F<pod/perldiag.pod> should go in the L</Diagnostics>
224 XXX Description of the change here
230 The following additions or changes have been made to diagnostic output,
231 including warnings and fatal error messages. For the complete list of
232 diagnostic messages, see L<perldiag>.
234 XXX New or changed warnings emitted by the core's C<C> code go here. Also
235 include any changes in L<perldiag> that reconcile it to the C<C> code.
237 [ Within each section, list entries as a =item entry that links to perldiag,
242 L<Invalid version object|perldiag/"Invalid version object">
245 =head2 New Diagnostics
247 XXX Newly added diagnostic messages go here
255 XXX L<message|perldiag/"message">
265 XXX L<message|perldiag/"message">
269 =head2 Changes to Existing Diagnostics
271 XXX Changes (i.e. rewording) of diagnostic messages go here
277 XXX Describe change here
281 =head1 Utility Changes
283 XXX Changes to installed programs such as F<perlbug> and F<xsubpp> go
284 here. Most of these are built within the directories F<utils> and F<x2p>.
286 [ List utility changes as a =head3 entry for each utility and =item
287 entries for each change
288 Use L<XXX> with program names to get proper documentation linking. ]
300 =head1 Configuration and Compilation
302 XXX Changes to F<Configure>, F<installperl>, F<installman>, and analogous tools
303 go here. Any other changes to the Perl build process should be listed here.
304 However, any platform-specific changes should be listed in the
305 L</Platform Support> section, instead.
307 [ List changes as a =item entry ].
319 XXX Any significant changes to the testing of a freshly built perl should be
320 listed here. Changes which create B<new> files in F<t/> go here as do any
321 large changes to the testing harness (e.g. when parallel testing was added).
322 Changes to existing files in F<t/> aren't worth summarising, although the bugs
323 that they represent may be covered elsewhere.
325 [ List each test improvement as a =item entry ]
335 =head1 Platform Support
337 XXX Any changes to platform support should be listed in the sections below.
339 [ Within the sections, list each platform as a =item entry with specific
340 changes as paragraphs below it. ]
344 XXX List any platforms that this version of perl compiles on, that previous
345 versions did not. These will either be enabled by new files in the F<hints/>
346 directories, or new subdirectories and F<README> files at the top level of the
351 =item XXX-some-platform
357 =head2 Discontinued Platforms
359 XXX List any platforms that this version of perl no longer compiles on.
363 =item XXX-some-platform
369 =head2 Platform-Specific Notes
371 XXX List any changes for specific platforms. This could include configuration
372 and compilation changes or changes in portability/compatibility. However,
373 changes within modules for platforms should generally be listed in the
374 L</Modules and Pragmata> section.
378 =item XXX-some-platform
384 =head1 Internal Changes
386 XXX Changes which affect the interface available to C<XS> code go here.
387 Other significant internal changes for future core maintainers should
390 [ List each change as a =item entry ]
396 C<PL_curstash> is now reference-counted.
400 =head1 Selected Bug Fixes
402 XXX Important bug fixes in the core language are summarised here.
403 Bug fixes in files in F<ext/> and F<lib/> are best summarised in
404 L</Modules and Pragmata>.
406 [ List each fix as a =item entry ]
412 Perl now holds an extra reference count on the package that code is
413 currently compiling in. This means that the following code no longer crashes [perl #101486]:
416 BEGIN {*Foo:: = *Bar::}
421 F<dumpvar.pl>, and consequently the C<x> command in the debugger, have been
422 fixed to handle objects blessed into classes whose names contain "=". The
423 contents of such objects used not to be dumped [perl #101814].
427 The C<x> repetition operator no longer crashes on 64-bit builds with large
428 repeate counts [perl #94560].
432 A fix to C<glob> under miniperl (used to configure modules when perl itself
433 is built) in Perl 5.15.3 stopped C<< <~> >> from returning the home
434 directory, because it cleared %ENV before calling csh. Now C<$ENV{HOME}>
435 is preserved. This fix probably does not affect anything. If
436 L<File::Glob> fails to load for some reason, Perl reverts to using csh.
437 So it would apply in that case.
441 On OSes other than VMS, Perl's C<glob> operator (and the C<< <...> >> form)
442 use L<File::Glob> underneath. L<File::Glob> splits the pattern into words,
443 before feeding each word to its C<bsd_glob> function.
445 There were several inconsistencies in the way the split was done. Now
446 quotation marks (' and ") are always treated as shell-style word delimiters
447 (that allow whitespace as part of a word) and backslashes are always
448 preserved, unless they exist to escape quotation marks. Before, those
449 would only sometimes be the case, depending on whether the pattern
450 contained whitespace. Also, escaped whitespace at the end of the pattern
451 is no longer stripped.
455 C<CORE::glob> now works as a way to call the default globbing function. It
456 used to respect overrides, despite the C<CORE::> prefix.
460 In 5.14, C</[[:lower:]]/i> and C</[[:upper:]]/i> no longer matched the
461 opposite case. This has been fixed [perl #101970].
465 A regular expression match with an overloaded object on the right-hand side
466 would in some cases stringify the object too many times.
470 The C-level C<pregcomp> function could become confused as to whether the
471 pattern was in UTF8 if the pattern was an overloaded, tied, or otherwise
472 magical scalar [perl #101940].
476 =head1 Known Problems
478 XXX Descriptions of platform agnostic bugs we know we can't fix go here. Any
479 tests that had to be C<TODO>ed for the release would be noted here, unless
480 they were specific to a particular platform (see below).
482 This is a list of some significant unfixed bugs, which are regressions
483 from either 5.XXX.XXX or 5.XXX.XXX.
485 [ List each fix as a =item entry ]
497 XXX If any significant core contributor has died, we've added a short obituary
500 =head1 Acknowledgements
502 XXX Generate this with:
504 perl Porting/acknowledgements.pl v5.15.4..HEAD
506 =head1 Reporting Bugs
508 If you find what you think is a bug, you might check the articles
509 recently posted to the comp.lang.perl.misc newsgroup and the perl
510 bug database at http://rt.perl.org/perlbug/ . There may also be
511 information at http://www.perl.org/ , the Perl Home Page.
513 If you believe you have an unreported bug, please run the L<perlbug>
514 program included with your release. Be sure to trim your bug down
515 to a tiny but sufficient test case. Your bug report, along with the
516 output of C<perl -V>, will be sent off to perlbug@perl.org to be
517 analysed by the Perl porting team.
519 If the bug you are reporting has security implications, which make it
520 inappropriate to send to a publicly archived mailing list, then please send
521 it to perl5-security-report@perl.org. This points to a closed subscription
522 unarchived mailing list, which includes
523 all the core committers, who will be able
524 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
532 The F<Changes> file for an explanation of how to view exhaustive details
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.