4 changelogged up to commit 2ea2ea91
5 * PERL_STATIC_INLINE might want to be mentioned
7 ** what's with the one change but many changelog entries?
8 ** why a new version in the changelog but no version bump?
12 [ this is a template for a new perldelta file. Any text flagged as
13 XXX needs to be processed before release. ]
15 perldelta - what is new for perl v5.13.4
19 This document describes differences between the 5.13.4 release and
22 If you are upgrading from an earlier release such as 5.13.2, first read
23 L<perl5133delta>, which describes differences between 5.13.2 and
28 XXX Any important notices here
30 =head1 Core Enhancements
32 XXX New core language features go here. Summarise user-visible core language
33 enhancements. Particularly prominent performance optimisations could go
34 here, but most should go in the L</Performance Enhancements> section.
36 [ List each enhancement as a =head2 entry ]
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. If any
51 exist, they are bugs and reports are welcome.
53 [ List each incompatible change as a =head2 entry ]
57 XXX Any deprecated features, syntax, modules etc. should be listed here.
58 In particular, deprecated modules should be listed here even if they are
59 listed as an updated module in the L</Modules and Pragmata> section.
61 [ List each deprecation as a =head2 entry ]
63 =head1 Performance Enhancements
65 XXX Changes which enhance performance without changing behaviour go here. There
66 may well be none in a stable release.
68 [ List each enhancement as a =item * entry ]
78 =head1 Modules and Pragmata
80 XXX All changes to installed files in F<cpan/>, F<dist/>, F<ext/> and F<lib/>
81 go here. If Module::CoreList is updated, generate an initial draft of the
82 following sections using F<Porting/corelist-perldelta.pl>, which prints stub
83 entries to STDOUT. Results can be pasted in place of the '=head2' entries
84 below. A paragraph summary for important changes should then be added by hand.
85 In an ideal world, dual-life modules would have a F<Changes> file that could be
88 [ Within each section, list entries as a =item NAME entry ]
90 =head2 New Modules and Pragmata
100 =head2 Updated Modules and Pragmata
106 Upgraded from version 1.16 to 1.18.
108 L<Carp> now detects incomplete L<caller()|perlfunc/"caller EXPR"> overrides and
109 avoids using bogus C<@DB::args>. This fixes certain cases of C<Bizarre copy of
110 ARRAY> caused by modules overriding C<caller()> incorrectly.
114 Upgraded from version 3.31 to 3.31_01.
116 Various issues in L<File::Spec::VMS> have been fixed.
120 =head2 Removed Modules and Pragmata
132 XXX Changes to files in F<pod/> go here. Consider grouping entries by
133 file and be sure to link to the appropriate page, e.g. L<perlfunc>.
135 =head2 New Documentation
137 XXX Changes which create B<new> files in F<pod/> go here.
141 XXX Description of the purpose of the new file here
143 =head2 Changes to Existing Documentation
145 XXX Changes which significantly change existing files in F<pod/> go here.
146 However, any changes to F<pod/perldiag.pod> should go in the L</Diagnostics>
155 Documented a L<limitation|perlport/alarm> of L<alarm()|perlfunc/"alarm SECONDS">
162 The following additions or changes have been made to diagnostic output,
163 including warnings and fatal error messages. For the complete list of
164 diagnostic messages, see L<perldiag>.
166 XXX New or changed warnings emitted by the core's C<C> code go here. Also
167 include any changes in L<perldiag> that reconcile it to the C<C> code.
169 [ Within each section, list entries as a =item entry ]
171 =head2 New Diagnostics
173 XXX Newly added diagnostic messages go here
183 =head2 Changes to Existing Diagnostics
185 XXX Changes (i.e. rewording) of diagnostic messages go here
195 =head1 Utility Changes
197 XXX Changes to installed programs such as F<perlbug> and F<xsubpp> go
198 here. Most of these are built within the directories F<utils> and F<x2p>.
200 [ List utility changes as a =head3 entry for each utility and =item
201 entries for each change
202 Use L<XXX> with program names to get proper documentation linking. ]
214 =head1 Configuration and Compilation
216 XXX Changes to F<Configure>, F<installperl>, F<installman>, and analogous tools
217 go here. Any other changes to the Perl build process should be listed here.
218 However, any platform-specific changes should be listed in the
219 L</Platform Support> section, instead.
221 [ List changes as a =item entry ].
227 Improve compatibility with C<C++> compilers.
233 XXX Any significant changes to the testing of a freshly built perl should be
234 listed here. Changes which create B<new> files in F<t/> go here as do any
235 large changes to the testing harness (e.g. when parallel testing was added).
236 Changes to existing files in F<t/> aren't worth summarising, although the bugs
237 that they represent may be covered elsewhere.
239 [ List each test improvement as a =item entry ]
249 =head1 Platform Support
251 XXX Any changes to platform support should be listed in the sections below.
253 [ Within the sections, list each platform as a =item entry with specific
254 changes as paragraphs below it. ]
258 XXX List any platforms that this version of perl compiles on, that previous
259 versions did not. These will either be enabled by new files in the F<hints/>
260 directories, or new subdirectories and F<README> files at the top level of the
265 =item XXX-some-platform
271 =head2 Discontinued Platforms
273 XXX List any platforms that this version of perl no longer compiles on.
277 =item XXX-some-platform
283 =head2 Platform-Specific Notes
285 XXX List any changes for specific platforms. This could include configuration
286 and compilation changes or changes in portability/compatibility. However,
287 changes within modules for platforms should generally be listed in the
288 L</Modules and Pragmata> section.
298 Fixed a possible hang in F<t/op/readline.t>.
302 Fixed Makefile for SDK2003SP1 compilers.
308 =head1 Internal Changes
310 XXX Changes which affect the interface available to C<XS> code go here.
311 Other significant internal changes for future core maintainers should
314 [ List each test improvement as a =item entry ]
318 =item Removed C<PERL_POLLUTE>
320 The option to define C<PERL_POLLUTE> to expose older 5.005 symbols for backwards
321 compatibility has been removed. It's use was always discouraged, and MakeMaker
322 contains a more specific escape hatch:
324 perl Makefile.PL POLLUTE=1
326 This can be used for modules that have not been upgraded to 5.6 naming
327 conventions (and really should be completely obsolete by now).
329 =item Declare API incompatibility between blead releases
331 Only stable releases (5.10.x, 5.12.x, 5.14.x, ...) guarantee binary
332 compatibility with each other, while blead releases (5.13.x, 5.15.x, ...) often
333 break this compatibility. However, prior to perl 5.13.4, all blead releases had
334 the same C<PERL_API_REVISION>, C<PERL_API_VERSION>, and C<PERL_API_SUBVERSION>,
335 effectively declaring them as binary compatible, which they weren't. From now
336 on, blead releases will have a C<PERL_API_SUBVERSION> equal to their
337 C<PERL_SUBVERSION>, explicitly marking them as incompatible with each other.
339 Maintainance releases of stable perl's will continue to make no intentionally
340 incompatible changes.
344 =head1 Selected Bug Fixes
346 XXX Important bug fixes in the core language are summarised here.
347 Bug fixes in files in F<ext/> and F<lib/> are best summarised in
348 L</Modules and Pragmata>.
350 [ List each fix as a =item entry ]
356 Fixed possible memory leak when using L<caller()|perlfunc/"caller EXPR"> to set
361 Several memory leaks when loading XS modules were fixed.
365 =head1 Known Problems
367 XXX Descriptions of platform agnostic bugs we know we can't fix go here. Any
368 tests that had to be C<TODO>ed for the release would be noted here, unless
369 they were specific to a particular platform (see below).
371 This is a list of some significant unfixed bugs, which are regressions
372 from either 5.XXX.XXX or 5.XXX.XXX.
374 [ List each fix as a =item entry ]
386 XXX If any significant core contributor has died, we've added a short obituary
389 =head1 Acknowledgements
391 XXX The list of people to thank goes here.
393 =head1 Reporting Bugs
395 If you find what you think is a bug, you might check the articles
396 recently posted to the comp.lang.perl.misc newsgroup and the perl
397 bug database at http://rt.perl.org/perlbug/ . There may also be
398 information at http://www.perl.org/ , the Perl Home Page.
400 If you believe you have an unreported bug, please run the B<perlbug>
401 program included with your release. Be sure to trim your bug down
402 to a tiny but sufficient test case. Your bug report, along with the
403 output of C<perl -V>, will be sent off to perlbug@perl.org to be
404 analysed by the Perl porting team.
406 If the bug you are reporting has security implications, which make it
407 inappropriate to send to a publicly archived mailing list, then please send
408 it to perl5-security-report@perl.org. This points to a closed subscription
409 unarchived mailing list, which includes all the core committers, who be able
410 to help assess the impact of issues, figure out a resolution, and help
411 co-ordinate the release of patches to mitigate or fix the problem across all
412 platforms on which Perl is supported. Please only use this address for
413 security issues in the Perl core, not for modules independently
418 The F<Changes> file for an explanation of how to view exhaustive details
421 The F<INSTALL> file for how to build Perl.
423 The F<README> file for general stuff.
425 The F<Artistic> and F<Copying> files for copyright information.