4 changelogged up to commit 65bfe90c
5 * PERL_STATIC_INLINE might want to be mentioned
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.13.4
16 This document describes differences between the 5.13.4 release and
19 If you are upgrading from an earlier release such as 5.13.2, first read
20 L<perl5133delta>, which describes differences between 5.13.2 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.
33 [ List each enhancement as a =head2 entry ]
37 XXX Any security-related notices go here. In particular, any security
38 vulnerabilities closed should be noted here rather than in the
39 L</Selected Bug Fixes> section.
41 [ List each security issue as a =head2 entry ]
43 =head1 Incompatible Changes
45 XXX For a release on a stable branch, this section aspires to be:
47 There are no changes intentionally incompatible with 5.XXX.XXX. If any
48 exist, they are bugs and reports are welcome.
50 [ List each incompatible change as a =head2 entry ]
54 XXX Any deprecated features, syntax, modules etc. should be listed here.
55 In particular, deprecated modules should be listed here even if they are
56 listed as an updated module in the L</Modules and Pragmata> section.
58 [ List each deprecation as a =head2 entry ]
60 =head1 Performance Enhancements
62 XXX Changes which enhance performance without changing behaviour go here. There
63 may well be none in a stable release.
65 [ List each enhancement as a =item * entry ]
75 =head1 Modules and Pragmata
77 XXX All changes to installed files in F<cpan/>, F<dist/>, F<ext/> and F<lib/>
78 go here. If Module::CoreList is updated, generate an initial draft of the
79 following sections using F<Porting/corelist-perldelta.pl>, which prints stub
80 entries to STDOUT. Results can be pasted in place of the '=head2' entries
81 below. A paragraph summary for important changes should then be added by hand.
82 In an ideal world, dual-life modules would have a F<Changes> file that could be
85 [ Within each section, list entries as a =item NAME entry ]
87 =head2 New Modules and Pragmata
97 =head2 Updated Modules and Pragmata
101 =item C<Archive::Tar>
103 Upgraded from version 1.64 to 1.66.
105 Among other things, the new version adds a new option to C<ptar> to allow safe
106 creation of tarballs without world-writable files on Windows, allowing those
107 archives to be uploaded to CPAN.
111 Upgraded from version 1.11 to 1.12.
115 Upgraded from version 1.16 to 1.18.
117 L<Carp> now detects incomplete L<caller()|perlfunc/"caller EXPR"> overrides and
118 avoids using bogus C<@DB::args>. This fixes certain cases of C<Bizarre copy of
119 ARRAY> caused by modules overriding C<caller()> incorrectly.
121 =item C<Compress::Raw::Bzip2>
123 Upgraded from version 2.027 to 2.030.
125 =item C<Compress::Raw::Zlib>
127 Upgraded from version 2.027 to 2.030.
131 Upgraded from version 3.31 to 3.31_01.
133 Various issues in L<File::Spec::VMS> have been fixed.
135 =item C<IO::Compress>
137 Upgraded from version 2.027 to 2.030.
141 =head2 Removed Modules and Pragmata
153 XXX Changes to files in F<pod/> go here. Consider grouping entries by
154 file and be sure to link to the appropriate page, e.g. L<perlfunc>.
156 =head2 New Documentation
158 XXX Changes which create B<new> files in F<pod/> go here.
162 XXX Description of the purpose of the new file here
164 =head2 Changes to Existing Documentation
166 XXX Changes which significantly change existing files in F<pod/> go here.
167 However, any changes to F<pod/perldiag.pod> should go in the L</Diagnostics>
176 Documented a L<limitation|perlport/alarm> of L<alarm()|perlfunc/"alarm SECONDS">
183 The following additions or changes have been made to diagnostic output,
184 including warnings and fatal error messages. For the complete list of
185 diagnostic messages, see L<perldiag>.
187 XXX New or changed warnings emitted by the core's C<C> code go here. Also
188 include any changes in L<perldiag> that reconcile it to the C<C> code.
190 [ Within each section, list entries as a =item entry ]
192 =head2 New Diagnostics
194 XXX Newly added diagnostic messages go here
204 =head2 Changes to Existing Diagnostics
206 XXX Changes (i.e. rewording) of diagnostic messages go here
216 =head1 Utility Changes
218 XXX Changes to installed programs such as F<perlbug> and F<xsubpp> go
219 here. Most of these are built within the directories F<utils> and F<x2p>.
221 [ List utility changes as a =head3 entry for each utility and =item
222 entries for each change
223 Use L<XXX> with program names to get proper documentation linking. ]
235 =head1 Configuration and Compilation
237 XXX Changes to F<Configure>, F<installperl>, F<installman>, and analogous tools
238 go here. Any other changes to the Perl build process should be listed here.
239 However, any platform-specific changes should be listed in the
240 L</Platform Support> section, instead.
242 [ List changes as a =item entry ].
248 Improve compatibility with C<C++> compilers.
254 XXX Any significant changes to the testing of a freshly built perl should be
255 listed here. Changes which create B<new> files in F<t/> go here as do any
256 large changes to the testing harness (e.g. when parallel testing was added).
257 Changes to existing files in F<t/> aren't worth summarising, although the bugs
258 that they represent may be covered elsewhere.
260 [ List each test improvement as a =item entry ]
266 F<t/op/print.t> has been added to test implicit printing of C<$_>.
270 =head1 Platform Support
272 XXX Any changes to platform support should be listed in the sections below.
274 [ Within the sections, list each platform as a =item entry with specific
275 changes as paragraphs below it. ]
279 XXX List any platforms that this version of perl compiles on, that previous
280 versions did not. These will either be enabled by new files in the F<hints/>
281 directories, or new subdirectories and F<README> files at the top level of the
286 =item XXX-some-platform
292 =head2 Discontinued Platforms
294 XXX List any platforms that this version of perl no longer compiles on.
298 =item XXX-some-platform
304 =head2 Platform-Specific Notes
306 XXX List any changes for specific platforms. This could include configuration
307 and compilation changes or changes in portability/compatibility. However,
308 changes within modules for platforms should generally be listed in the
309 L</Modules and Pragmata> section.
319 Fixed a possible hang in F<t/op/readline.t>.
323 Fixed Makefile for SDK2003SP1 compilers.
329 =head1 Internal Changes
331 XXX Changes which affect the interface available to C<XS> code go here.
332 Other significant internal changes for future core maintainers should
335 [ List each test improvement as a =item entry ]
339 =item Removed C<PERL_POLLUTE>
341 The option to define C<PERL_POLLUTE> to expose older 5.005 symbols for backwards
342 compatibility has been removed. It's use was always discouraged, and MakeMaker
343 contains a more specific escape hatch:
345 perl Makefile.PL POLLUTE=1
347 This can be used for modules that have not been upgraded to 5.6 naming
348 conventions (and really should be completely obsolete by now).
350 =item Declare API incompatibility between blead releases
352 Only stable releases (5.10.x, 5.12.x, 5.14.x, ...) guarantee binary
353 compatibility with each other, while blead releases (5.13.x, 5.15.x, ...) often
354 break this compatibility. However, prior to perl 5.13.4, all blead releases had
355 the same C<PERL_API_REVISION>, C<PERL_API_VERSION>, and C<PERL_API_SUBVERSION>,
356 effectively declaring them as binary compatible, which they weren't. From now
357 on, blead releases will have a C<PERL_API_SUBVERSION> equal to their
358 C<PERL_SUBVERSION>, explicitly marking them as incompatible with each other.
360 Maintainance releases of stable perl's will continue to make no intentionally
361 incompatible changes.
363 =item Make extending the peephole optimizer easier
365 As of version 5.8, extension authors were allowed to replace perl's peephole
366 optimizer function. However, this was B<very> hard to do, as there was no way to
367 add new optimizations without having to copy large parts of perl's original
368 optimizer. This problem is now solved by a rework of the optimizer extension
369 API. See L<perlguts/"Compile pass 3: peephole optimization"> for details.
373 =head1 Selected Bug Fixes
375 XXX Important bug fixes in the core language are summarised here.
376 Bug fixes in files in F<ext/> and F<lib/> are best summarised in
377 L</Modules and Pragmata>.
379 [ List each fix as a =item entry ]
385 Fixed possible memory leak when using L<caller()|perlfunc/"caller EXPR"> to set
390 Several memory leaks when loading XS modules were fixed.
394 A panic in the regular expression optimizer has been fixed (RT#75762).
398 Assignments to lvalue subroutines now honor copy-on-write behavior again, which
399 has been broken since version 5.10.0 (RT#75656).
403 =head1 Known Problems
405 XXX Descriptions of platform agnostic bugs we know we can't fix go here. Any
406 tests that had to be C<TODO>ed for the release would be noted here, unless
407 they were specific to a particular platform (see below).
409 This is a list of some significant unfixed bugs, which are regressions
410 from either 5.XXX.XXX or 5.XXX.XXX.
412 [ List each fix as a =item entry ]
424 XXX If any significant core contributor has died, we've added a short obituary
427 =head1 Acknowledgements
429 XXX The list of people to thank goes here.
431 =head1 Reporting Bugs
433 If you find what you think is a bug, you might check the articles
434 recently posted to the comp.lang.perl.misc newsgroup and the perl
435 bug database at http://rt.perl.org/perlbug/ . There may also be
436 information at http://www.perl.org/ , the Perl Home Page.
438 If you believe you have an unreported bug, please run the B<perlbug>
439 program included with your release. Be sure to trim your bug down
440 to a tiny but sufficient test case. Your bug report, along with the
441 output of C<perl -V>, will be sent off to perlbug@perl.org to be
442 analysed by the Perl porting team.
444 If the bug you are reporting has security implications, which make it
445 inappropriate to send to a publicly archived mailing list, then please send
446 it to perl5-security-report@perl.org. This points to a closed subscription
447 unarchived mailing list, which includes all the core committers, who be able
448 to help assess the impact of issues, figure out a resolution, and help
449 co-ordinate the release of patches to mitigate or fix the problem across all
450 platforms on which Perl is supported. Please only use this address for
451 security issues in the Perl core, not for modules independently
456 The F<Changes> file for an explanation of how to view exhaustive details
459 The F<INSTALL> file for how to build Perl.
461 The F<README> file for general stuff.
463 The F<Artistic> and F<Copying> files for copyright information.