3 perldelta - what is new for perl v5.11.4
7 This document describes differences between the 5.11.3 release and
10 If you are upgrading from an earlier release such as 5.11.2, first read
11 L<perl5113delta>, which describes differences between 5.11.2 and
16 XXX Any important notices here
18 =head1 Incompatible Changes
20 XXX For a release on a stable branch, this section aspires to be:
22 There are no changes intentionally incompatible with 5.XXX.XXX. If any
23 exist, they are bugs and reports are welcome.
26 =head1 Core Enhancements
28 XXX New core language features go here. Summarise user-visible core language
29 enhancements. Particularly prominent performance optimisations could go
30 here, but most should go in the L</Performance Enhancements> section.
32 =head2 Unicode properties
34 C<\p{XDigit}> now matches the same characters as C<\p{Hex_Digit}>. This
35 means that in addition to the characters it currently matches,
36 C<[A-Fa-f0-9]>, it will also match their fullwidth equivalent forms, for
37 example U+FF10: FULLWIDTH DIGIT ZERO.
41 XXX List any platforms that this version of perl compiles on, that previous
42 versions did not. These will either be enabled by new files in the F<hints/>
43 directories, or new subdirectories and F<README> files at the top level of the
46 =head1 Modules and Pragmata
48 XXX All changes to installed files in F<cpan/>, F<dist/>, F<ext/> and F<lib/>
49 go here. If Module::CoreList is updated, generate an initial draft of the
50 following sections using F<Porting/corelist-perldelta.pl>, which prints stub
51 entries to STDOUT. Results can be pasted in place of the '=head2' entries
52 below. A paragraph summary for important changes should then be added by hand.
53 In an ideal world, dual-life modules would have a F<Changes> file that could be
56 =head2 New Modules and Pragmata
58 =head2 Pragmata Changes
60 =head2 Updated Modules
62 =head2 Removed Modules and Pragmata
64 =head1 Utility Changes
66 XXX Changes to installed programs such as F<perlbug> and F<xsubpp> go
67 here. Most of these are built within the directories F<utils> and F<x2p>.
77 =head1 New Documentation
79 XXX Changes which create B<new> files in F<pod/> go here.
89 =head1 Changes to Existing Documentation
91 XXX Changes which significantly change existing files in F<pod/> go here.
92 Any changes to F<pod/perldiag.pod> should go in L</New or Changed Diagnostics>.
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.
108 =head1 Installation and Configuration Improvements
110 XXX Changes to F<Configure>, F<installperl>, F<installman>, and analogous tools
113 =head2 Configuration improvements
117 =head2 Compilation improvements
121 =head2 Platform Specific Changes
125 =item XXX-some-platform
131 =head1 Selected Bug Fixes
133 XXX Important bug fixes in the core language are summarised here.
134 Bug fixes in files in F<ext/> and F<lib/> are best summarised in
135 L</Modules and Pragmata>.
145 =head1 New or Changed Diagnostics
149 =item New warning category C<illegalproto>
153 Illegal character in prototype for %s : %s
154 Prototype after '%c' for %s : %s
156 have been moved from the C<syntax> top-level warnings category into a new
157 first-level category, C<illegalproto>. These two warnings are currently the
158 only ones emitted during parsing of an invalid/illegal prototype, so one
161 no warnings 'illegalproto';
163 to suppress only those, but not other syntax-related warnings. Warnings where
164 prototypes are changed, ignored, or not met are still in the C<prototype>
165 category as before. (Matt S. Trout)
167 =item lvalue attribute ignored after the subroutine has been defined
169 This new warning is issued when one attempts to mark a subroutine as
170 lvalue after it has been defined.
174 =head1 Changed Internals
176 XXX Changes which affect the interface available to C<XS> code go here.
188 XXX Changes which create B<new> files in F<t/> go here. Changes to
189 existing files in F<t/> aren't worth summarising, although the bugs that
190 they represent may be.
200 =head1 Known Problems
202 XXX Descriptions of platform agnostic bugs we know we can't fix go here. Any
203 tests that had to be C<TODO>ed for the release would be noted here, unless
204 they were specific to a particular platform (see below).
206 This is a list of some significant unfixed bugs, which are regressions
207 from either 5.XXX.XXX or 5.XXX.XXX.
219 The following items are now deprecated.
223 =item C<< UNIVERSAL-E<gt>import() >>
225 The method C<< UNIVERSAL-E<gt>import() >> is now deprecated.
226 Attempting to pass import arguments to a C<use UNIVERSAL>
227 statement will result in a deprecation warning. (This is
228 a less noisy version of the full deprecation warning
233 =head1 Platform Specific Notes
235 XXX Any changes specific to a particular platform. VMS and Win32 are the usual
236 stars here. It's probably best to group changes under the same section layout
237 as the main perldelta
241 XXX If any significant core contributor has died, we've added a short obituary
244 =head1 Acknowledgements
246 XXX The list of people to thank goes here.
249 =head1 Reporting Bugs
251 If you find what you think is a bug, you might check the articles
252 recently posted to the comp.lang.perl.misc newsgroup and the perl
253 bug database at http://rt.perl.org/perlbug/ . There may also be
254 information at http://www.perl.org/ , the Perl Home Page.
256 If you believe you have an unreported bug, please run the B<perlbug>
257 program included with your release. Be sure to trim your bug down
258 to a tiny but sufficient test case. Your bug report, along with the
259 output of C<perl -V>, will be sent off to perlbug@perl.org to be
260 analysed by the Perl porting team.
262 If the bug you are reporting has security implications, which make it
263 inappropriate to send to a publicly archived mailing list, then please send
264 it to perl5-security-report@perl.org. This points to a closed subscription
265 unarchived mailing list, which includes all the core committers, who be able
266 to help assess the impact of issues, figure out a resolution, and help
267 co-ordinate the release of patches to mitigate or fix the problem across all
268 platforms on which Perl is supported. Please only use this address for
269 security issues in the Perl core, not for modules independently
274 The F<Changes> file for an explanation of how to view exhaustive details
277 The F<INSTALL> file for how to build Perl.
279 The F<README> file for general stuff.
281 The F<Artistic> and F<Copying> files for copyright information.