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.15.8
12 This document describes differences between the 5.15.7 release and
15 If you are upgrading from an earlier release such as 5.15.6, first read
16 L<perl5157delta>, which describes differences between 5.15.6 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 Improved ability to mix locales and Unicode, including UTF-8 locales
33 An optional parameter has been added to C<use locale>
35 use locale ':not_characters';
37 which tells Perl to use all but the C<LC_CTYPE> and C<LC_COLLATE>
38 portions of the current locale. Instead, the character set is assumed
39 to be Unicode. This allows locales and Unicode to be seamlessly mixed,
40 including the increasingly frequent UTF-8 locales. When using this
41 hybrid form of locales, the C<:locale> layer to the L<open> pragma can
42 be used to interface with the file system, and there are CPAN modules
43 available for ARGV and environment variable conversions.
45 Full details are in L<perllocale>.
47 >>>>>>> Add :not_characters parameter to 'use locale'
51 XXX Any security-related notices go here. In particular, any security
52 vulnerabilities closed should be noted here rather than in the
53 L</Selected Bug Fixes> section.
55 [ List each security issue as a =head2 entry ]
57 =head1 Incompatible Changes
59 XXX For a release on a stable branch, this section aspires to be:
61 There are no changes intentionally incompatible with 5.XXX.XXX
62 If any exist, they are bugs, and we request that you submit a
63 report. See L</Reporting Bugs> below.
65 [ List each incompatible change as a =head2 entry ]
69 XXX Any deprecated features, syntax, modules etc. should be listed here.
70 In particular, deprecated modules should be listed here even if they are
71 listed as an updated module in the L</Modules and Pragmata> section.
73 [ List each deprecation as a =head2 entry ]
75 =head1 Performance Enhancements
77 XXX Changes which enhance performance without changing behaviour go here. There
78 may well be none in a stable release.
80 [ List each enhancement as a =item entry ]
90 =head1 Modules and Pragmata
92 XXX All changes to installed files in F<cpan/>, F<dist/>, F<ext/> and F<lib/>
93 go here. If Module::CoreList is updated, generate an initial draft of the
94 following sections using F<Porting/corelist-perldelta.pl>, which prints stub
95 entries to STDOUT. Results can be pasted in place of the '=head2' entries
96 below. A paragraph summary for important changes should then be added by hand.
97 In an ideal world, dual-life modules would have a F<Changes> file that could be
100 [ Within each section, list entries as a =item entry ]
102 =head2 New Modules and Pragmata
112 =head2 Updated Modules and Pragmata
118 L<Pod::Parser> has been upgraded from version 1.37 to version 1.50.
122 =head2 Removed Modules and Pragmata
134 XXX Changes to files in F<pod/> go here. Consider grouping entries by
135 file and be sure to link to the appropriate page, e.g. L<perlfunc>.
137 =head2 New Documentation
139 XXX Changes which create B<new> files in F<pod/> go here.
143 XXX Description of the purpose of the new file here
145 =head2 Changes to Existing Documentation
147 XXX Changes which significantly change existing files in F<pod/> go here.
148 However, any changes to F<pod/perldiag.pod> should go in the L</Diagnostics>
157 XXX Description of the change here
163 The following additions or changes have been made to diagnostic output,
164 including warnings and fatal error messages. For the complete list of
165 diagnostic messages, see L<perldiag>.
167 XXX New or changed warnings emitted by the core's C<C> code go here. Also
168 include any changes in L<perldiag> that reconcile it to the C<C> code.
170 [ Within each section, list entries as a =item entry that links to perldiag,
175 L<Invalid version object|perldiag/"Invalid version object">
178 =head2 New Diagnostics
180 XXX Newly added diagnostic messages go here
188 XXX L<message|perldiag/"message">
198 XXX L<message|perldiag/"message">
202 =head2 Changes to Existing Diagnostics
204 XXX Changes (i.e. rewording) of diagnostic messages go here
210 XXX Describe change here
214 =head1 Utility Changes
216 XXX Changes to installed programs such as F<perlbug> and F<xsubpp> go
217 here. Most of these are built within the directories F<utils> and F<x2p>.
219 [ List utility changes as a =head3 entry for each utility and =item
220 entries for each change
221 Use L<XXX> with program names to get proper documentation linking. ]
233 =head1 Configuration and Compilation
235 XXX Changes to F<Configure>, F<installperl>, F<installman>, and analogous tools
236 go here. Any other changes to the Perl build process should be listed here.
237 However, any platform-specific changes should be listed in the
238 L</Platform Support> section, instead.
240 [ List changes as a =item entry ].
252 XXX Any significant changes to the testing of a freshly built perl should be
253 listed here. Changes which create B<new> files in F<t/> go here as do any
254 large changes to the testing harness (e.g. when parallel testing was added).
255 Changes to existing files in F<t/> aren't worth summarising, although the bugs
256 that they represent may be covered elsewhere.
258 [ List each test improvement as a =item entry ]
268 =head1 Platform Support
270 XXX Any changes to platform support should be listed in the sections below.
272 [ Within the sections, list each platform as a =item entry with specific
273 changes as paragraphs below it. ]
277 XXX List any platforms that this version of perl compiles on, that previous
278 versions did not. These will either be enabled by new files in the F<hints/>
279 directories, or new subdirectories and F<README> files at the top level of the
284 =item XXX-some-platform
290 =head2 Discontinued Platforms
292 XXX List any platforms that this version of perl no longer compiles on.
296 =item XXX-some-platform
302 =head2 Platform-Specific Notes
304 XXX List any changes for specific platforms. This could include configuration
305 and compilation changes or changes in portability/compatibility. However,
306 changes within modules for platforms should generally be listed in the
307 L</Modules and Pragmata> section.
311 =item XXX-some-platform
317 =head1 Internal Changes
319 XXX Changes which affect the interface available to C<XS> code go here.
320 Other significant internal changes for future core maintainers should
323 [ List each change as a =item entry ]
333 =head1 Selected Bug Fixes
335 XXX Important bug fixes in the core language are summarised here.
336 Bug fixes in files in F<ext/> and F<lib/> are best summarised in
337 L</Modules and Pragmata>.
339 [ List each fix as a =item entry ]
349 =head1 Known Problems
351 XXX Descriptions of platform agnostic bugs we know we can't fix go here. Any
352 tests that had to be C<TODO>ed for the release would be noted here, unless
353 they were specific to a particular platform (see below).
355 This is a list of some significant unfixed bugs, which are regressions
356 from either 5.XXX.XXX or 5.XXX.XXX.
358 [ List each fix as a =item entry ]
370 XXX If any significant core contributor has died, we've added a short obituary
373 =head1 Acknowledgements
375 XXX Generate this with:
377 perl Porting/acknowledgements.pl v5.15.7..HEAD
379 =head1 Reporting Bugs
381 If you find what you think is a bug, you might check the articles
382 recently posted to the comp.lang.perl.misc newsgroup and the perl
383 bug database at http://rt.perl.org/perlbug/ . There may also be
384 information at http://www.perl.org/ , the Perl Home Page.
386 If you believe you have an unreported bug, please run the L<perlbug>
387 program included with your release. Be sure to trim your bug down
388 to a tiny but sufficient test case. Your bug report, along with the
389 output of C<perl -V>, will be sent off to perlbug@perl.org to be
390 analysed by the Perl porting team.
392 If the bug you are reporting has security implications, which make it
393 inappropriate to send to a publicly archived mailing list, then please send
394 it to perl5-security-report@perl.org. This points to a closed subscription
395 unarchived mailing list, which includes
396 all the core committers, who will be able
397 to help assess the impact of issues, figure out a resolution, and help
398 co-ordinate the release of patches to mitigate or fix the problem across all
399 platforms on which Perl is supported. Please only use this address for
400 security issues in the Perl core, not for modules independently
405 The F<Changes> file for an explanation of how to view exhaustive details
408 The F<INSTALL> file for how to build Perl.
410 The F<README> file for general stuff.
412 The F<Artistic> and F<Copying> files for copyright information.