5 [ this is a template for a new perldelta file. Any text flagged as
6 XXX needs to be processed before release. ]
8 perldelta - what is new for perl v5.13.10
12 This document describes differences between the 5.XXX.XXX release and
13 the 5.XXX.XXX release.
15 If you are upgrading from an earlier release such as 5.YYY.YYY, first read
16 L<perl5YYYdelta>, which describes differences between 5.ZZZ.ZZZ and
21 XXX Any important notices here
23 =head1 Core Enhancements
25 XXX New core language features go here. Summarise user-visible core language
26 enhancements. Particularly prominent performance optimisations could go
27 here, but most should go in the L</Performance Enhancements> section.
29 [ List each enhancement as a =head2 entry ]
31 =head2 Add C<\p{Titlecase}> as a synonym for C<\p{Title}>
33 This synyom is added for symmetry with the Unicode property names
34 C<\p{Uppercase}> and C<\p{Lowercase}>.
36 =head2 New regular expression modifier option C</aa>
38 Doubling the C</a> regular expression modifier increases its effect,
39 so that in case-insensitive matching, no ASCII character will match a
40 non-ASCII character. For example, normally,
42 'k' =~ /\N{KELVIN SIGN}/
44 will match; it won't under C</aa>. Note that like C</a>, C</aa>
45 in 5.14 will not actually be able to be used as a suffix at the end of a
50 XXX Any security-related notices go here. In particular, any security
51 vulnerabilities closed should be noted here rather than in the
52 L</Selected Bug Fixes> section.
54 [ List each security issue as a =head2 entry ]
56 =head1 Incompatible Changes
58 XXX For a release on a stable branch, this section aspires to be:
60 There are no changes intentionally incompatible with 5.XXX.XXX. If any
61 exist, they are bugs and reports are welcome.
63 [ List each incompatible change as a =head2 entry ]
65 =head2 Most C<\p{}> properties are now immune from case-insensitive matching
67 For most Unicode properties, it doesn't make sense to have them match
68 differently under C</i> case-insensitive matching than not. And doing
69 so leads to unexpected results and potential security holes. For
72 m/\p{ASCII_Hex_Digit}+/i
74 could previously match non-ASCII characters because of the Unicode
75 matching rules. There were a number of bugs in this feature until an
76 earlier release in the 5.13 series. Now this release reverts, and
77 removes the feature completely except for the few properties where
78 people have come to expect it, namely the ones where casing is an
79 integral part of their functionality, such as C<m/\p{Uppercase}/i> and
80 C<m/\p{Lowercase}/i>, both of which match the exact same code points,
81 namely those matched by C<m/\p{Cased}/i>. Details are in
82 L<perlrecharclass/Unicode Properties>.
84 User-defined property handlers that need to match differently under
85 C</i> must change to read the new boolean parameter passed it which is
86 non-zero if case-insensitive matching is in effect; 0 if not. See
87 L<perluniprops/User-Defined Character Properties>.
91 XXX Any deprecated features, syntax, modules etc. should be listed here.
92 In particular, deprecated modules should be listed here even if they are
93 listed as an updated module in the L</Modules and Pragmata> section.
95 [ List each deprecation as a =head2 entry ]
97 =head1 Performance Enhancements
99 XXX Changes which enhance performance without changing behaviour go here. There
100 may well be none in a stable release.
102 [ List each enhancement as a =item entry ]
112 =head1 Modules and Pragmata
114 XXX All changes to installed files in F<cpan/>, F<dist/>, F<ext/> and F<lib/>
115 go here. If Module::CoreList is updated, generate an initial draft of the
116 following sections using F<Porting/corelist-perldelta.pl>, which prints stub
117 entries to STDOUT. Results can be pasted in place of the '=head2' entries
118 below. A paragraph summary for important changes should then be added by hand.
119 In an ideal world, dual-life modules would have a F<Changes> file that could be
122 [ Within each section, list entries as a =item entry ]
124 =head2 New Modules and Pragmata
130 C<Version::Requirements> version 0.101020 has been added as a dual-life
131 module. It provides a standard library to model and manipulates module
132 prerequisites and version constraints as defined in the L<CPAN::Meta::Spec>.
136 =head2 Updated Modules and Pragmata
142 C<CGI> has been upgraded from version 3.51 to 3.52
146 C<CPANPLUS> has been upgraded from version 0.9011 to 0.9101
148 Includes support for META.json and MYMETA.json and a change to
149 using Digest::SHA for CPAN checksums.
153 C<IPC::Cmd> has been upgraded from version 0.68 to 0.70
157 C<HTTP::Tiny> has been upgraded from version 0.009 to 0.010
161 C<Module::Build> has been upgraded from version 0.3607 to 0.3622.
163 A notable change is the deprecation of several modules.
164 Module::Build::Version has been deprecated and Module::Build now relies
165 directly upon L<version>. Module::Build::ModuleInfo has been deprecated in
166 favor of a standalone copy of it called L<Module::Metadata>.
167 Module::Build::YAML has been deprecated in favor of L<CPAN::Meta::YAML>.
171 C<Module::Load::Conditional> has been upgraded from version 0.40 to 0.44
175 C<Module::Metadata> has been upgraded from version 1.000003 to 1.000004.
179 C<Parse::CPAN::Meta> has been upgraded from version 1.40 to 1.4401.
181 The latest Parse::CPAN::Meta can now read YAML or JSON files using
182 L<CPAN::Meta::YAML> and L<JSON::PP>, which are now part of the Perl core.
186 C<Term::UI> has been upgraded from version 0.24 to 0.26
190 C<Unicode::Collate> has been upgraded from version 0.68 to 0.72
192 This also sees the switch from using the pure-perl version of this
193 module to the XS version.`
197 Added new function C<Unicode::UCD::num(). This function will return the
198 numeric value of the string passed it; C<undef> if the string in its
199 entirety has no safe numeric value.
201 To be safe, a string must be a single character which has a numeric
202 value, or consist entirely of characters that match \d, coming from the
203 same Unicode block of digits. Thus, a mix of Bengali and Western
204 digits would be considered unsafe, as well as a mix of half- and
205 full-width digits, but strings consisting entirely of Devanagari digits
206 or of "Mathematical Bold" digits would would be safe.
214 =head2 Removed Modules and Pragmata
226 XXX Changes to files in F<pod/> go here. Consider grouping entries by
227 file and be sure to link to the appropriate page, e.g. L<perlfunc>.
229 =head2 New Documentation
231 XXX Changes which create B<new> files in F<pod/> go here.
235 XXX Description of the purpose of the new file here
237 =head2 Changes to Existing Documentation
239 XXX Changes which significantly change existing files in F<pod/> go here.
240 However, any changes to F<pod/perldiag.pod> should go in the L</Diagnostics>
243 =head3 L<perlhack> and perlrepository
249 The L<perlhack> and perlrepository documents have been heavily edited and
250 split up into several new documents.
252 The L<perlhack> document is now much shorter, and focuses on the Perl 5
253 development process and submitting patches to Perl. The technical content has
254 been moved to several new documents, L<perlsource>, L<perlinterp>,
255 L<perlhacktut>, and L<perlhacktips>. This technical content has only been
258 The perlrepository document has been renamed to L<perlgit>. This new document
259 is just a how-to on using git with the Perl source code. Any other content
260 that used to be in perlrepository has been moved to perlhack.
266 The following additions or changes have been made to diagnostic output,
267 including warnings and fatal error messages. For the complete list of
268 diagnostic messages, see L<perldiag>.
270 XXX New or changed warnings emitted by the core's C<C> code go here. Also
271 include any changes in L<perldiag> that reconcile it to the C<C> code.
273 [ Within each section, list entries as a =item entry ]
275 =head2 New Diagnostics
277 XXX Newly added diagnostic messages go here
281 =item "\b{" is deprecated; use "\b\{" instead
283 =item "\B{" is deprecated; use "\B\{" instead
285 Use of an unescaped "{" immediately following a C<\b> or C<\B> is now
286 deprecated so as to reserve its use for Perl itself in a future release.
291 =head2 Changes to Existing Diagnostics
293 XXX Changes (i.e. rewording) of diagnostic messages go here
303 =head1 Utility Changes
305 XXX Changes to installed programs such as F<perlbug> and F<xsubpp> go
306 here. Most of these are built within the directories F<utils> and F<x2p>.
308 [ List utility changes as a =head3 entry for each utility and =item
309 entries for each change
310 Use L<XXX> with program names to get proper documentation linking. ]
322 =head1 Configuration and Compilation
324 XXX Changes to F<Configure>, F<installperl>, F<installman>, and analogous tools
325 go here. Any other changes to the Perl build process should be listed here.
326 However, any platform-specific changes should be listed in the
327 L</Platform Support> section, instead.
329 [ List changes as a =item entry ].
341 XXX Any significant changes to the testing of a freshly built perl should be
342 listed here. Changes which create B<new> files in F<t/> go here as do any
343 large changes to the testing harness (e.g. when parallel testing was added).
344 Changes to existing files in F<t/> aren't worth summarising, although the bugs
345 that they represent may be covered elsewhere.
347 [ List each test improvement as a =item entry ]
353 F<porting/FindExt.t> now skips all tests on a static (-Uusedl) build
358 F<porting/FindExt.t> now passes on non-Win32 platforms when some
359 extensions are built statically.
363 =head1 Platform Support
365 XXX Any changes to platform support should be listed in the sections below.
367 [ Within the sections, list each platform as a =item entry with specific
368 changes as paragraphs below it. ]
372 XXX List any platforms that this version of perl compiles on, that previous
373 versions did not. These will either be enabled by new files in the F<hints/>
374 directories, or new subdirectories and F<README> files at the top level of the
379 =item XXX-some-platform
385 =head2 Discontinued Platforms
387 XXX List any platforms that this version of perl no longer compiles on.
391 =item XXX-some-platform
397 =head2 Platform-Specific Notes
399 XXX List any changes for specific platforms. This could include configuration
400 and compilation changes or changes in portability/compatibility. However,
401 changes within modules for platforms should generally be listed in the
402 L</Modules and Pragmata> section.
412 The C<test-prep> build target now depends on F<pod/perltoc.pod> to allow the
413 F<t/porting/buildtoc.t> test to run successfully.
419 =head1 Internal Changes
421 XXX Changes which affect the interface available to C<XS> code go here.
422 Other significant internal changes for future core maintainers should
425 [ List each test improvement as a =item entry ]
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 A Unicode C<\p{}> property match in a regular rexpression pattern will
448 now force Unicode rules for the rest of the regular expression
452 =head1 Known Problems
454 XXX Descriptions of platform agnostic bugs we know we can't fix go here. Any
455 tests that had to be C<TODO>ed for the release would be noted here, unless
456 they were specific to a particular platform (see below).
458 This is a list of some significant unfixed bugs, which are regressions
459 from either 5.XXX.XXX or 5.XXX.XXX.
461 [ List each fix as a =item entry ]
473 XXX If any significant core contributor has died, we've added a short obituary
476 =head1 Acknowledgements
478 XXX The list of people to thank goes here.
480 =head1 Reporting Bugs
482 If you find what you think is a bug, you might check the articles
483 recently posted to the comp.lang.perl.misc newsgroup and the perl
484 bug database at http://rt.perl.org/perlbug/ . There may also be
485 information at http://www.perl.org/ , the Perl Home Page.
487 If you believe you have an unreported bug, please run the L<perlbug>
488 program included with your release. Be sure to trim your bug down
489 to a tiny but sufficient test case. Your bug report, along with the
490 output of C<perl -V>, will be sent off to perlbug@perl.org to be
491 analysed by the Perl porting team.
493 If the bug you are reporting has security implications, which make it
494 inappropriate to send to a publicly archived mailing list, then please send
495 it to perl5-security-report@perl.org. This points to a closed subscription
496 unarchived mailing list, which includes all the core committers, who be able
497 to help assess the impact of issues, figure out a resolution, and help
498 co-ordinate the release of patches to mitigate or fix the problem across all
499 platforms on which Perl is supported. Please only use this address for
500 security issues in the Perl core, not for modules independently
505 The F<Changes> file for an explanation of how to view exhaustive details
508 The F<INSTALL> file for how to build Perl.
510 The F<README> file for general stuff.
512 The F<Artistic> and F<Copying> files for copyright information.