4 changelogged up to commit d6fa5a34
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 ]
35 =head2 C<\N{I<name>}> and C<charnames> enhancements
37 C<\N{}>, C<charnames::vianame>, C<charnames::viacode> now know about every
38 character in Unicode. Previously, they didn't know about the Hangul syllables
39 nor a number of CJK (Chinese/Japanese/Korean) characters.
41 =head2 C<srand()> now returns the seed
43 This allows programs which need to have repeatable results to not have to come
44 up with their own seed generating mechanism. Instead, they can use C<srand()>
45 and somehow stash the return for future use. Typical is a test program which
46 has too many combinations to test comprehensively in the time available to it
47 each run. It can test a random subset each time, and should there be a
48 failure, log the seed used for that run so that it can later be used to
49 reproduce the exact results.
53 XXX Any security-related notices go here. In particular, any security
54 vulnerabilities closed should be noted here rather than in the
55 L</Selected Bug Fixes> section.
57 [ List each security issue as a =head2 entry ]
59 =head1 Incompatible Changes
61 =head2 Declare API incompatibility between blead releases
63 Only stable releases (5.10.x, 5.12.x, 5.14.x, ...) guarantee binary
64 compatibility with each other, while blead releases (5.13.x, 5.15.x, ...) often
65 break this compatibility. However, prior to perl 5.13.4, all blead releases had
66 the same C<PERL_API_REVISION>, C<PERL_API_VERSION>, and C<PERL_API_SUBVERSION>,
67 effectively declaring them as binary compatible, which they weren't. From now
68 on, blead releases will have a C<PERL_API_SUBVERSION> equal to their
69 C<PERL_SUBVERSION>, explicitly marking them as incompatible with each other.
71 Maintainance releases of stable perl versions will continue to make no
72 intentionally incompatible API changes.
74 =head2 Check API compatibility when loading XS modules
76 When perl's API changes in incompatible ways (which usually happens between
77 every major release), XS modules compiled for previous versions of perl will not
78 work anymore. They will need to be recompiled against the new perl.
80 In order to ensure that modules are recompiled, and to prevent users from
81 accidentally loading modules compiled for old perls into newer ones, the
82 C<XS_APIVERSION_BOOTCHECK> macro has been added. That macro, which is called
83 when loading every newly compiled extension, compares the API version of the
84 running perl with the version a module has been compiled for and raises an
85 exception if they don't match.
87 =head2 Binary Incompatible with all previous Perls
89 Some bit fields have been reordered, hence this release will not be binary
90 comptible with any previous Perl release.
94 XXX Any deprecated features, syntax, modules etc. should be listed here.
95 In particular, deprecated modules should be listed here even if they are
96 listed as an updated module in the L</Modules and Pragmata> section.
98 [ List each deprecation as a =head2 entry ]
100 =head1 Performance Enhancements
102 XXX Changes which enhance performance without changing behaviour go here. There
103 may well be none in a stable release.
105 [ List each enhancement as a =item * entry ]
115 =head1 Modules and Pragmata
117 XXX All changes to installed files in F<cpan/>, F<dist/>, F<ext/> and F<lib/>
118 go here. If Module::CoreList is updated, generate an initial draft of the
119 following sections using F<Porting/corelist-perldelta.pl>, which prints stub
120 entries to STDOUT. Results can be pasted in place of the '=head2' entries
121 below. A paragraph summary for important changes should then be added by hand.
122 In an ideal world, dual-life modules would have a F<Changes> file that could be
125 [ Within each section, list entries as a =item NAME entry ]
127 =head2 New Modules and Pragmata
137 =head2 Updated Modules and Pragmata
141 =item C<Archive::Tar>
143 Upgraded from version 1.64 to 1.66.
145 Among other things, the new version adds a new option to C<ptar> to allow safe
146 creation of tarballs without world-writable files on Windows, allowing those
147 archives to be uploaded to CPAN.
151 Upgraded from version 1.11 to 1.12.
155 Upgraded from version 1.16 to 1.18.
157 L<Carp> now detects incomplete L<caller()|perlfunc/"caller EXPR"> overrides and
158 avoids using bogus C<@DB::args>. This fixes certain cases of C<Bizarre copy of
159 ARRAY> caused by modules overriding C<caller()> incorrectly.
161 =item C<Compress::Raw::Bzip2>
163 Upgraded from version 2.027 to 2.030.
165 =item C<Compress::Raw::Zlib>
167 Upgraded from version 2.027 to 2.030.
171 Upgraded from version 3.31 to 3.31_01.
173 Various issues in L<File::Spec::VMS> have been fixed.
175 =item C<IO::Compress>
177 Upgraded from version 2.027 to 2.030.
181 =head2 Removed Modules and Pragmata
193 XXX Changes to files in F<pod/> go here. Consider grouping entries by
194 file and be sure to link to the appropriate page, e.g. L<perlfunc>.
196 =head2 New Documentation
198 XXX Changes which create B<new> files in F<pod/> go here.
202 XXX Description of the purpose of the new file here
204 =head2 Changes to Existing Documentation
206 XXX Changes which significantly change existing files in F<pod/> go here.
207 However, any changes to F<pod/perldiag.pod> should go in the L</Diagnostics>
216 The following existing diagnostics are now documented:
222 L<Ambiguous use of %c resolved as operator %c|perldiag/"Ambiguous use of %c resolved as operator %c">
226 L<Ambiguous use of %c{%s} resolved to %c%s|perldiag/"Ambiguous use of %c{%s} resolved to %c%s">
230 L<Ambiguous use of %c{%s%s} resolved to %c%s%s|perldiag/"Ambiguous use of %c{%s%s} resolved to %c%s%s">
234 L<Ambiguous use of -%s resolved as -&%s()|perldiag/"Ambiguous use of -%s resolved as -&%s()">
246 Documented a L<limitation|perlport/alarm> of L<alarm()|perlfunc/"alarm SECONDS">
253 The following additions or changes have been made to diagnostic output,
254 including warnings and fatal error messages. For the complete list of
255 diagnostic messages, see L<perldiag>.
257 XXX New or changed warnings emitted by the core's C<C> code go here. Also
258 include any changes in L<perldiag> that reconcile it to the C<C> code.
260 [ Within each section, list entries as a =item entry ]
262 =head2 New Diagnostics
264 XXX Newly added diagnostic messages go here
274 =head2 Changes to Existing Diagnostics
276 XXX Changes (i.e. rewording) of diagnostic messages go here
286 =head1 Utility Changes
288 XXX Changes to installed programs such as F<perlbug> and F<xsubpp> go
289 here. Most of these are built within the directories F<utils> and F<x2p>.
291 [ List utility changes as a =head3 entry for each utility and =item
292 entries for each change
293 Use L<XXX> with program names to get proper documentation linking. ]
305 =head1 Configuration and Compilation
307 XXX Changes to F<Configure>, F<installperl>, F<installman>, and analogous tools
308 go here. Any other changes to the Perl build process should be listed here.
309 However, any platform-specific changes should be listed in the
310 L</Platform Support> section, instead.
312 [ List changes as a =item entry ].
318 Improve compatibility with C<C++> compilers.
324 XXX Any significant changes to the testing of a freshly built perl should be
325 listed here. Changes which create B<new> files in F<t/> go here as do any
326 large changes to the testing harness (e.g. when parallel testing was added).
327 Changes to existing files in F<t/> aren't worth summarising, although the bugs
328 that they represent may be covered elsewhere.
330 [ List each test improvement as a =item entry ]
336 F<t/op/print.t> has been added to test implicit printing of C<$_>.
340 F<t/io/errnosig.t> has been added to test for restoration of of C<$!> when
341 leaving signal handlers.
345 =head1 Platform Support
347 XXX Any changes to platform support should be listed in the sections below.
349 [ Within the sections, list each platform as a =item entry with specific
350 changes as paragraphs below it. ]
354 XXX List any platforms that this version of perl compiles on, that previous
355 versions did not. These will either be enabled by new files in the F<hints/>
356 directories, or new subdirectories and F<README> files at the top level of the
361 =item XXX-some-platform
367 =head2 Discontinued Platforms
369 XXX List any platforms that this version of perl no longer compiles on.
373 =item XXX-some-platform
379 =head2 Platform-Specific Notes
381 XXX List any changes for specific platforms. This could include configuration
382 and compilation changes or changes in portability/compatibility. However,
383 changes within modules for platforms should generally be listed in the
384 L</Modules and Pragmata> section.
394 Fixed a possible hang in F<t/op/readline.t>.
398 Fixed Makefile for SDK2003SP1 compilers.
404 =head1 Internal Changes
406 XXX Changes which affect the interface available to C<XS> code go here.
407 Other significant internal changes for future core maintainers should
410 [ List each test improvement as a =item entry ]
414 =item Removed C<PERL_POLLUTE>
416 The option to define C<PERL_POLLUTE> to expose older 5.005 symbols for backwards
417 compatibility has been removed. It's use was always discouraged, and MakeMaker
418 contains a more specific escape hatch:
420 perl Makefile.PL POLLUTE=1
422 This can be used for modules that have not been upgraded to 5.6 naming
423 conventions (and really should be completely obsolete by now).
425 =item Make extending the peephole optimizer easier
427 As of version 5.8, extension authors were allowed to replace perl's peephole
428 optimizer function. However, this was B<very> hard to do, as there was no way to
429 add new optimizations without having to copy large parts of perl's original
430 optimizer. This problem is now solved by a rework of the optimizer extension
431 API. See L<perlguts/"Compile pass 3: peephole optimization"> for details.
435 =head1 Selected Bug Fixes
437 XXX Important bug fixes in the core language are summarised here.
438 Bug fixes in files in F<ext/> and F<lib/> are best summarised in
439 L</Modules and Pragmata>.
441 [ List each fix as a =item entry ]
447 Fixed possible memory leak when using L<caller()|perlfunc/"caller EXPR"> to set
452 Several memory leaks when loading XS modules were fixed.
456 A panic in the regular expression optimizer has been fixed (RT#75762).
460 Assignments to lvalue subroutines now honor copy-on-write behavior again, which
461 has been broken since version 5.10.0 (RT#75656).
465 Assignments to glob copies now behave just like assignments to regular globs
470 Within signal handlers, C<$!> is now implicitly localized.
474 =head1 Known Problems
476 XXX Descriptions of platform agnostic bugs we know we can't fix go here. Any
477 tests that had to be C<TODO>ed for the release would be noted here, unless
478 they were specific to a particular platform (see below).
480 This is a list of some significant unfixed bugs, which are regressions
481 from either 5.XXX.XXX or 5.XXX.XXX.
483 [ List each fix as a =item entry ]
495 XXX If any significant core contributor has died, we've added a short obituary
498 =head1 Acknowledgements
500 XXX The list of people to thank goes here.
502 =head1 Reporting Bugs
504 If you find what you think is a bug, you might check the articles
505 recently posted to the comp.lang.perl.misc newsgroup and the perl
506 bug database at http://rt.perl.org/perlbug/ . There may also be
507 information at http://www.perl.org/ , the Perl Home Page.
509 If you believe you have an unreported bug, please run the B<perlbug>
510 program included with your release. Be sure to trim your bug down
511 to a tiny but sufficient test case. Your bug report, along with the
512 output of C<perl -V>, will be sent off to perlbug@perl.org to be
513 analysed by the Perl porting team.
515 If the bug you are reporting has security implications, which make it
516 inappropriate to send to a publicly archived mailing list, then please send
517 it to perl5-security-report@perl.org. This points to a closed subscription
518 unarchived mailing list, which includes all the core committers, who be able
519 to help assess the impact of issues, figure out a resolution, and help
520 co-ordinate the release of patches to mitigate or fix the problem across all
521 platforms on which Perl is supported. Please only use this address for
522 security issues in the Perl core, not for modules independently
527 The F<Changes> file for an explanation of how to view exhaustive details
530 The F<INSTALL> file for how to build Perl.
532 The F<README> file for general stuff.
534 The F<Artistic> and F<Copying> files for copyright information.