5 [ this is a template for a new perldelta file. Any text flagged as XXX needs
6 to be processed before release. ]
8 perldelta - what is new for perl v5.19.1
12 This document describes differences between the 5.19.0 release and the 5.19.1
17 XXX Any important notices here
19 =head1 Core Enhancements
21 XXX New core language features go here. Summarize user-visible core language
22 enhancements. Particularly prominent performance optimisations could go
23 here, but most should go in the L</Performance Enhancements> section.
25 [ List each enhancement as a =head2 entry ]
29 XXX Any security-related notices go here. In particular, any security
30 vulnerabilities closed should be noted here rather than in the
31 L</Selected Bug Fixes> section.
33 [ List each security issue as a =head2 entry ]
35 =head1 Incompatible Changes
37 XXX For a release on a stable branch, this section aspires to be:
39 There are no changes intentionally incompatible with 5.XXX.XXX
40 If any exist, they are bugs, and we request that you submit a
41 report. See L</Reporting Bugs> below.
43 [ List each incompatible change as a =head2 entry ]
47 XXX Any deprecated features, syntax, modules etc. should be listed here.
49 =head2 Module removals
51 XXX Remove this section if inapplicable.
53 The following modules will be removed from the core distribution in a future
54 release, and will at that time need to be installed from CPAN. Distributions
55 on CPAN which require these modules will need to list them as prerequisites.
57 The core versions of these modules will now issue C<"deprecated">-category
58 warnings to alert you to this fact. To silence these deprecation warnings,
59 install the modules in question from CPAN.
61 Note that these are (with rare exceptions) fine modules that you are encouraged
62 to continue to use. Their disinclusion from core primarily hinges on their
63 necessity to bootstrapping a fully functional, CPAN-capable Perl installation,
64 not usually on concerns over their design.
66 XXX Note that deprecated modules should be listed here even if they are listed
67 as an updated module in the L</Modules and Pragmata> section.
77 [ List each other deprecation as a =head2 entry ]
79 =head1 Performance Enhancements
81 XXX Changes which enhance performance without changing behaviour go here.
82 There may well be none in a stable release.
84 [ List each enhancement as a =item entry ]
94 =head1 Modules and Pragmata
96 XXX All changes to installed files in F<cpan/>, F<dist/>, F<ext/> and F<lib/>
97 go here. If Module::CoreList is updated, generate an initial draft of the
98 following sections using F<Porting/corelist-perldelta.pl>, which prints stub
99 entries to STDOUT. Results can be pasted in place of the '=head2' entries
100 below. A paragraph summary for important changes should then be added by hand.
101 In an ideal world, dual-life modules would have a F<Changes> file that could be
104 [ Within each section, list entries as a =item entry ]
106 =head2 New Modules and Pragmata
116 =head2 Updated Modules and Pragmata
122 Test::Harness has been upgraded from version 3.26 to 3.28
124 Memory usage is dramatically reduced. t/harness now uses about 10% of the
125 memory used by 3.26 and earlier.
127 C<PERL5LIB> is always propagated to a test's C<@INC>, even under C<-T>.
131 Unicode::UCD has been upgraded from version 0.51 to 0.52.
133 A function, L<Unicode::UCD/search_invlist()> is now available to do
134 search an inversion list or map for a code point.
138 =head2 Removed Modules and Pragmata
150 XXX Changes to files in F<pod/> go here. Consider grouping entries by
151 file and be sure to link to the appropriate page, e.g. L<perlfunc>.
153 =head2 New Documentation
155 XXX Changes which create B<new> files in F<pod/> go here.
159 XXX Description of the purpose of the new file here
161 =head2 Changes to Existing Documentation
163 XXX Changes which significantly change existing files in F<pod/> go here.
164 However, any changes to F<pod/perldiag.pod> should go in the L</Diagnostics>
173 XXX Description of the change here
179 The following additions or changes have been made to diagnostic output,
180 including warnings and fatal error messages. For the complete list of
181 diagnostic messages, see L<perldiag>.
183 XXX New or changed warnings emitted by the core's C<C> code go here. Also
184 include any changes in L<perldiag> that reconcile it to the C<C> code.
186 =head2 New Diagnostics
188 XXX Newly added diagnostic messages go under here, separated into New Errors
197 XXX L<message|perldiag/"message">
207 XXX L<message|perldiag/"message">
211 =head2 Changes to Existing Diagnostics
213 XXX Changes (i.e. rewording) of diagnostic messages go here
219 XXX Describe change here
223 =head1 Utility Changes
225 XXX Changes to installed programs such as F<perlbug> and F<xsubpp> go here.
226 Most of these are built within the directories F<utils> and F<x2p>.
228 [ List utility changes as a =head3 entry for each utility and =item
229 entries for each change
230 Use L<XXX> with program names to get proper documentation linking. ]
242 =head1 Configuration and Compilation
244 XXX Changes to F<Configure>, F<installperl>, F<installman>, and analogous tools
245 go here. Any other changes to the Perl build process should be listed here.
246 However, any platform-specific changes should be listed in the
247 L</Platform Support> section, instead.
249 [ List changes as a =item entry ].
261 XXX Any significant changes to the testing of a freshly built perl should be
262 listed here. Changes which create B<new> files in F<t/> go here as do any
263 large changes to the testing harness (e.g. when parallel testing was added).
264 Changes to existing files in F<t/> aren't worth summarizing, although the bugs
265 that they represent may be covered elsewhere.
267 [ List each test improvement as a =item entry ]
277 =head1 Platform Support
279 XXX Any changes to platform support should be listed in the sections below.
281 [ Within the sections, list each platform as a =item entry with specific
282 changes as paragraphs below it. ]
286 XXX List any platforms that this version of perl compiles on, that previous
287 versions did not. These will either be enabled by new files in the F<hints/>
288 directories, or new subdirectories and F<README> files at the top level of the
293 =item XXX-some-platform
299 =head2 Discontinued Platforms
301 XXX List any platforms that this version of perl no longer compiles on.
305 =item XXX-some-platform
311 =head2 Platform-Specific Notes
313 XXX List any changes for specific platforms. This could include configuration
314 and compilation changes or changes in portability/compatibility. However,
315 changes within modules for platforms should generally be listed in the
316 L</Modules and Pragmata> section.
320 =item Mixed-endian platforms
322 The code supporting C<pack> and C<unpack> operations on mixed endian
323 platforms has been removed. We believe that Perl has long been unable to
324 build on mixed endian architectures (such as PDP-11s), so we don't think
325 that this change will affect any platforms which are able to build v5.18.0.
329 =head1 Internal Changes
331 XXX Changes which affect the interface available to C<XS> code go here. Other
332 significant internal changes for future core maintainers should be noted as
335 [ List each change as a =item entry ]
341 The functions C<my_swap>, C<my_htonl> and C<my_ntohl> have been removed.
342 It is unclear why these functions were ever marked as I<A>, part of the
343 API. XS code can't call them directly, as it can't rely on them being
344 compiled. Unsurprisingly, no code on CPAN references them.
348 =head1 Selected Bug Fixes
350 XXX Important bug fixes in the core language are summarized here. Bug fixes in
351 files in F<ext/> and F<lib/> are best summarized in L</Modules and Pragmata>.
353 [ List each fix as a =item entry ]
359 The OP allocation code now returns correctly aligned memory in all cases
360 for C<struct pmop>. Previously it could return memory only aligned to a
361 4-byte boundary, which is not correct for an ithreads build with 64 bit IVs
362 on some 32 bit platforms. Notably, this caused the build to fail completely
363 on sparc GNU/Linux. [RT #118055]
367 =head1 Known Problems
369 XXX Descriptions of platform agnostic bugs we know we can't fix go here. Any
370 tests that had to be C<TODO>ed for the release would be noted here. Unfixed
371 platform specific bugs also go here.
373 [ List each fix as a =item entry ]
385 XXX If any significant core contributor has died, we've added a short obituary
388 =head1 Acknowledgements
390 XXX Generate this with:
392 perl Porting/acknowledgements.pl v5.19.1..HEAD
394 =head1 Reporting Bugs
396 If you find what you think is a bug, you might check the articles recently
397 posted to the comp.lang.perl.misc newsgroup and the perl bug database at
398 http://rt.perl.org/perlbug/ . There may also be information at
399 http://www.perl.org/ , the Perl Home Page.
401 If you believe you have an unreported bug, please run the L<perlbug> program
402 included with your release. Be sure to trim your bug down to a tiny but
403 sufficient test case. Your bug report, along with the output of C<perl -V>,
404 will be sent off to perlbug@perl.org to be 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 it
408 to perl5-security-report@perl.org. This points to a closed subscription
409 unarchived mailing list, which includes all the core committers, who will be
410 able 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 distributed on
418 The F<Changes> file for an explanation of how to view exhaustive details on
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.