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.
89 XXX Any deprecated features, syntax, modules etc. should be listed here.
90 In particular, deprecated modules should be listed here even if they are
91 listed as an updated module in the L</Modules and Pragmata> section.
93 [ List each deprecation as a =head2 entry ]
95 =head1 Performance Enhancements
97 XXX Changes which enhance performance without changing behaviour go here. There
98 may well be none in a stable release.
100 [ List each enhancement as a =item * entry ]
110 =head1 Modules and Pragmata
112 XXX All changes to installed files in F<cpan/>, F<dist/>, F<ext/> and F<lib/>
113 go here. If Module::CoreList is updated, generate an initial draft of the
114 following sections using F<Porting/corelist-perldelta.pl>, which prints stub
115 entries to STDOUT. Results can be pasted in place of the '=head2' entries
116 below. A paragraph summary for important changes should then be added by hand.
117 In an ideal world, dual-life modules would have a F<Changes> file that could be
120 [ Within each section, list entries as a =item NAME entry ]
122 =head2 New Modules and Pragmata
132 =head2 Updated Modules and Pragmata
136 =item C<Archive::Tar>
138 Upgraded from version 1.64 to 1.66.
140 Among other things, the new version adds a new option to C<ptar> to allow safe
141 creation of tarballs without world-writable files on Windows, allowing those
142 archives to be uploaded to CPAN.
146 Upgraded from version 1.11 to 1.12.
150 Upgraded from version 1.16 to 1.18.
152 L<Carp> now detects incomplete L<caller()|perlfunc/"caller EXPR"> overrides and
153 avoids using bogus C<@DB::args>. This fixes certain cases of C<Bizarre copy of
154 ARRAY> caused by modules overriding C<caller()> incorrectly.
156 =item C<Compress::Raw::Bzip2>
158 Upgraded from version 2.027 to 2.030.
160 =item C<Compress::Raw::Zlib>
162 Upgraded from version 2.027 to 2.030.
166 Upgraded from version 3.31 to 3.31_01.
168 Various issues in L<File::Spec::VMS> have been fixed.
170 =item C<IO::Compress>
172 Upgraded from version 2.027 to 2.030.
176 =head2 Removed Modules and Pragmata
188 XXX Changes to files in F<pod/> go here. Consider grouping entries by
189 file and be sure to link to the appropriate page, e.g. L<perlfunc>.
191 =head2 New Documentation
193 XXX Changes which create B<new> files in F<pod/> go here.
197 XXX Description of the purpose of the new file here
199 =head2 Changes to Existing Documentation
201 XXX Changes which significantly change existing files in F<pod/> go here.
202 However, any changes to F<pod/perldiag.pod> should go in the L</Diagnostics>
211 The following existing diagnostics are now documented:
217 L<Ambiguous use of %c resolved as operator %c|perldiag/"Ambiguous use of %c resolved as operator %c">
221 L<Ambiguous use of %c{%s} resolved to %c%s|perldiag/"Ambiguous use of %c{%s} resolved to %c%s">
225 L<Ambiguous use of %c{%s%s} resolved to %c%s%s|perldiag/"Ambiguous use of %c{%s%s} resolved to %c%s%s">
229 L<Ambiguous use of -%s resolved as -&%s()|perldiag/"Ambiguous use of -%s resolved as -&%s()">
241 Documented a L<limitation|perlport/alarm> of L<alarm()|perlfunc/"alarm SECONDS">
248 The following additions or changes have been made to diagnostic output,
249 including warnings and fatal error messages. For the complete list of
250 diagnostic messages, see L<perldiag>.
252 XXX New or changed warnings emitted by the core's C<C> code go here. Also
253 include any changes in L<perldiag> that reconcile it to the C<C> code.
255 [ Within each section, list entries as a =item entry ]
257 =head2 New Diagnostics
259 XXX Newly added diagnostic messages go here
269 =head2 Changes to Existing Diagnostics
271 XXX Changes (i.e. rewording) of diagnostic messages go here
281 =head1 Utility Changes
283 XXX Changes to installed programs such as F<perlbug> and F<xsubpp> go
284 here. Most of these are built within the directories F<utils> and F<x2p>.
286 [ List utility changes as a =head3 entry for each utility and =item
287 entries for each change
288 Use L<XXX> with program names to get proper documentation linking. ]
300 =head1 Configuration and Compilation
302 XXX Changes to F<Configure>, F<installperl>, F<installman>, and analogous tools
303 go here. Any other changes to the Perl build process should be listed here.
304 However, any platform-specific changes should be listed in the
305 L</Platform Support> section, instead.
307 [ List changes as a =item entry ].
313 Improve compatibility with C<C++> compilers.
319 XXX Any significant changes to the testing of a freshly built perl should be
320 listed here. Changes which create B<new> files in F<t/> go here as do any
321 large changes to the testing harness (e.g. when parallel testing was added).
322 Changes to existing files in F<t/> aren't worth summarising, although the bugs
323 that they represent may be covered elsewhere.
325 [ List each test improvement as a =item entry ]
331 F<t/op/print.t> has been added to test implicit printing of C<$_>.
335 F<t/io/errnosig.t> has been added to test for restoration of of C<$!> when
336 leaving signal handlers.
340 =head1 Platform Support
342 XXX Any changes to platform support should be listed in the sections below.
344 [ Within the sections, list each platform as a =item entry with specific
345 changes as paragraphs below it. ]
349 XXX List any platforms that this version of perl compiles on, that previous
350 versions did not. These will either be enabled by new files in the F<hints/>
351 directories, or new subdirectories and F<README> files at the top level of the
356 =item XXX-some-platform
362 =head2 Discontinued Platforms
364 XXX List any platforms that this version of perl no longer compiles on.
368 =item XXX-some-platform
374 =head2 Platform-Specific Notes
376 XXX List any changes for specific platforms. This could include configuration
377 and compilation changes or changes in portability/compatibility. However,
378 changes within modules for platforms should generally be listed in the
379 L</Modules and Pragmata> section.
389 Fixed a possible hang in F<t/op/readline.t>.
393 Fixed Makefile for SDK2003SP1 compilers.
399 =head1 Internal Changes
401 XXX Changes which affect the interface available to C<XS> code go here.
402 Other significant internal changes for future core maintainers should
405 [ List each test improvement as a =item entry ]
409 =item Removed C<PERL_POLLUTE>
411 The option to define C<PERL_POLLUTE> to expose older 5.005 symbols for backwards
412 compatibility has been removed. It's use was always discouraged, and MakeMaker
413 contains a more specific escape hatch:
415 perl Makefile.PL POLLUTE=1
417 This can be used for modules that have not been upgraded to 5.6 naming
418 conventions (and really should be completely obsolete by now).
420 =item Make extending the peephole optimizer easier
422 As of version 5.8, extension authors were allowed to replace perl's peephole
423 optimizer function. However, this was B<very> hard to do, as there was no way to
424 add new optimizations without having to copy large parts of perl's original
425 optimizer. This problem is now solved by a rework of the optimizer extension
426 API. See L<perlguts/"Compile pass 3: peephole optimization"> for details.
430 =head1 Selected Bug Fixes
432 XXX Important bug fixes in the core language are summarised here.
433 Bug fixes in files in F<ext/> and F<lib/> are best summarised in
434 L</Modules and Pragmata>.
436 [ List each fix as a =item entry ]
442 Fixed possible memory leak when using L<caller()|perlfunc/"caller EXPR"> to set
447 Several memory leaks when loading XS modules were fixed.
451 A panic in the regular expression optimizer has been fixed (RT#75762).
455 Assignments to lvalue subroutines now honor copy-on-write behavior again, which
456 has been broken since version 5.10.0 (RT#75656).
460 Assignments to glob copies now behave just like assignments to regular globs
465 Within signal handlers, C<$!> is now implicitly localized.
469 =head1 Known Problems
471 XXX Descriptions of platform agnostic bugs we know we can't fix go here. Any
472 tests that had to be C<TODO>ed for the release would be noted here, unless
473 they were specific to a particular platform (see below).
475 This is a list of some significant unfixed bugs, which are regressions
476 from either 5.XXX.XXX or 5.XXX.XXX.
478 [ List each fix as a =item entry ]
490 XXX If any significant core contributor has died, we've added a short obituary
493 =head1 Acknowledgements
495 XXX The list of people to thank goes here.
497 =head1 Reporting Bugs
499 If you find what you think is a bug, you might check the articles
500 recently posted to the comp.lang.perl.misc newsgroup and the perl
501 bug database at http://rt.perl.org/perlbug/ . There may also be
502 information at http://www.perl.org/ , the Perl Home Page.
504 If you believe you have an unreported bug, please run the B<perlbug>
505 program included with your release. Be sure to trim your bug down
506 to a tiny but sufficient test case. Your bug report, along with the
507 output of C<perl -V>, will be sent off to perlbug@perl.org to be
508 analysed by the Perl porting team.
510 If the bug you are reporting has security implications, which make it
511 inappropriate to send to a publicly archived mailing list, then please send
512 it to perl5-security-report@perl.org. This points to a closed subscription
513 unarchived mailing list, which includes all the core committers, who be able
514 to help assess the impact of issues, figure out a resolution, and help
515 co-ordinate the release of patches to mitigate or fix the problem across all
516 platforms on which Perl is supported. Please only use this address for
517 security issues in the Perl core, not for modules independently
522 The F<Changes> file for an explanation of how to view exhaustive details
525 The F<INSTALL> file for how to build Perl.
527 The F<README> file for general stuff.
529 The F<Artistic> and F<Copying> files for copyright information.