- Incompatible Changes
- Core Enhancements
- New Platforms
- Modules and Pragmata
- Utility Changes
- New Documentation
- Changes to Existing Documentation
- Performance Enhancements
- Installation and Configuration Improvements
- Selected Bug Fixes
- New or Changed Diagnostics
- Changed Internals
- New Tests
- Known Problems
- Platform Specific Notes
- Reporting Bugs
- SEE ALSO
[ this is a template for a new perldelta file. Any text flagged as XXX needs to be processed before release. ]
perldelta - what is new for perl v5.11.6
This document describes differences between the 5.11.5 release and the 5.11.6 release.
If you are upgrading from an earlier release such as 5.11.4, first read perl5115delta, which describes differences between 5.11.4 and 5.11.5.
XXX Any important notices here
XXX For a release on a stable branch, this section aspires to be:
There are no changes intentionally incompatible with 5.XXX.XXX. If any exist, they are bugs and reports are welcome.
XXX New core language features go here. Summarise user-visible core language enhancements. Particularly prominent performance optimisations could go here, but most should go in the "Performance Enhancements" section.
XXX List any platforms that this version of perl compiles on, that previous versions did not. These will either be enabled by new files in the hints/ directories, or new subdirectories and README files at the top level of the source tree.
XXX All changes to installed files in cpan/, dist/, ext/ and lib/ go here. If Module::CoreList is updated, generate an initial draft of the following sections using Porting/corelist-perldelta.pl, which prints stub entries to STDOUT. Results can be pasted in place of the '=head2' entries below. A paragraph summary for important changes should then be added by hand. In an ideal world, dual-life modules would have a Changes file that could be cribbed.
XXX Changes to installed programs such as perlbug and xsubpp go here. Most of these are built within the directories utils and x2p.
XXX Changes which create new files in pod/ go here.
XXX Changes which significantly change existing files in pod/ go here. Any changes to pod/perldiag.pod should go in "New or Changed Diagnostics".
XXX Changes which enhance performance without changing behaviour go here. There may well be none in a stable release.
XXX Changes to Configure, installperl, installman, and analogous tools go here.
XXX Important bug fixes in the core language are summarised here. Bug fixes in files in ext/ and lib/ are best summarised in "Modules and Pragmata".
XXX New or changed warnings emitted by the core's
C code go here.
XXX Changes which affect the interface available to
XS code go here.
XXX Changes which create new files in t/ go here. Changes to existing files in t/ aren't worth summarising, although the bugs that they represent may be.
XXX Descriptions of platform agnostic bugs we know we can't fix go here. Any tests that had to be
TODOed for the release would be noted here, unless they were specific to a particular platform (see below).
This is a list of some significant unfixed bugs, which are regressions from either 5.XXX.XXX or 5.XXX.XXX.
XXX Add any new known deprecations here.
The following items are now deprecated.
XXX Any changes specific to a particular platform. VMS and Win32 are the usual stars here. It's probably best to group changes under the same section layout as the main perldelta
XXX If any significant core contributor has died, we've added a short obituary here.
XXX The list of people to thank goes here.
If you find what you think is a bug, you might check the articles recently posted to the comp.lang.perl.misc newsgroup and the perl bug database at http://rt.perl.org/perlbug/ . There may also be information at http://www.perl.org/ , the Perl Home Page.
If you believe you have an unreported bug, please run the perlbug program included with your release. Be sure to trim your bug down to a tiny but sufficient test case. Your bug report, along with the output of
perl -V, will be sent off to email@example.com to be analysed by the Perl porting team.
If the bug you are reporting has security implications, which make it inappropriate to send to a publicly archived mailing list, then please send it to firstname.lastname@example.org. This points to a closed subscription unarchived mailing list, which includes all the core committers, who be able to help assess the impact of issues, figure out a resolution, and help co-ordinate the release of patches to mitigate or fix the problem across all platforms on which Perl is supported. Please only use this address for security issues in the Perl core, not for modules independently distributed on CPAN.
The Changes file for an explanation of how to view exhaustive details on what changed.
The INSTALL file for how to build Perl.
The README file for general stuff.
The Artistic and Copying files for copyright information.