3 [ Any text flagged as XXX needs to be processed before release. ]
5 perldelta - what is new for perl v5.11.2
9 This document describes differences between the 5.11.1 release and
14 XXX Unlikely to need this section.
16 =head1 Incompatible Changes
18 =head2 Use of C<:=> to mean an empty attribute list is now deprecated.
20 An accident of Perl's parser means that these constructions are all equivalent:
26 with the C<:> being treated as the start of an attribute list, which ends
27 before the C<=>. As whitespace is not significant here, all are parsed as an
28 empty attribute list, hence all the above are equivalent to, and better written
33 because no attribute processing is done for an empty list.
35 As is, this means that C<:=> cannot be used as a new token, without silently
36 changing the meaning of existing code. Hence that particular form is now
37 deprecated, and will become a syntax error. If it is absolutely necessary to
38 have empty attribute lists (for example, because of a code generator) the
39 avoid the warning by adding a space before the C<=>.
41 =head1 Core Enhancements
43 XXX New core language features go here. Summarise user-visible core language
44 enhancements. Particularly prominent performance optimisations could go
45 here, but most should go in the L</Performance Enhancements> section.
49 XXX List any platforms that this version of perl compiles on, that previous
50 versions did not. These will either be enabled by new files in the F<hints/>
51 directories, or new subdirectories and F<README> files at the top level of the
54 =head1 Modules and Pragmata
56 XXX All changes to installed files in F<cpan/>, F<dist/>, F<ext/> and F<lib/>
57 go here, in a list ordered by distribution name. Minimally it should be the
58 module version, but it's more useful to the end user to give a paragraph's
59 summary of the module's changes. In an ideal world, dual-life modules would
60 have a F<Changes> file that could be cribbed.
62 =head2 New Modules and Pragmata
72 =head2 Pragmata Changes
82 =head2 Updated Modules
92 =head1 Utility Changes
94 XXX Changes to installed programs such as F<perlbug> and F<xsubpp> go
95 here. Most of these are built within the directories F<utils> and F<x2p>.
105 =head1 New Documentation
107 XXX Changes which create B<new> files in F<pod/> go here.
117 =head1 Changes to Existing Documentation
119 XXX Changes which significantly change existing files in F<pod/> go here.
120 Any changes to F<pod/perldiag.pod> should go in L</New or Changed Diagnostics>.
123 =head1 Performance Enhancements
125 XXX Changes which enhance performance without changing behaviour go here. There
126 may well be none in a stable release.
136 =head1 Installation and Configuration Improvements
138 XXX Changes to F<Configure>, F<installperl>, F<installman>, and analogous tools
141 =head2 Configuration improvements
145 =head2 Compilation improvements
149 =head2 Platform Specific Changes
153 =item XXX-some-platform
159 =head1 Selected Bug Fixes
161 XXX Important bug fixes in the core language are summarised here.
162 Bug fixes in files in F<ext/> and F<lib/> are best summarised in
163 L</Modules and Pragmata>.
173 =head1 New or Changed Diagnostics
175 XXX New or changed warnings emitted by the core's C<C> code go here.
185 =head1 Changed Internals
191 C<Perl_pmflag> has been removed from the public API. Calling it now generates
192 a deprecation warning, and it will be removed in a future release. Although
193 listed as part of the API, it was never documented, and only ever used in
194 F<toke.c>, and prior to 5.10, F<regcomp.c>. In core, it has been replaced by a
201 XXX Changes which create B<new> files in F<t/> go here. Changes to
202 existing files in F<t/> aren't worth summarising, although the bugs that
203 they represent may be.
213 =head1 Known Problems
215 XXX Descriptions of platform agnostic bugs we know we can't fix go here. Any
216 tests that had to be C<TODO>ed for the release would be noted here, unless
217 they were specific to a particular platform (see below).
219 This is a list of some significant unfixed bugs, which are regressions
220 from either 5.10.1 or 5.11.1.
232 XXX Add any new known deprecations here.
234 The following items are now deprecated.
244 =head1 Platform Specific Notes
246 XXX Any changes specific to a particular platform. VMS and Win32 are the usual
247 stars here. It's probably best to group changes under the same section layout
248 as the main perldelta
252 XXX If any significant core contributor has died, we've added a short obituary
255 =head1 Acknowledgements
257 XXX The list of people to thank goes here.
260 =head1 Reporting Bugs
262 If you find what you think is a bug, you might check the articles
263 recently posted to the comp.lang.perl.misc newsgroup and the perl
264 bug database at http://rt.perl.org/perlbug/ . There may also be
265 information at http://www.perl.org/ , the Perl Home Page.
267 If you believe you have an unreported bug, please run the B<perlbug>
268 program included with your release. Be sure to trim your bug down
269 to a tiny but sufficient test case. Your bug report, along with the
270 output of C<perl -V>, will be sent off to perlbug@perl.org to be
271 analysed by the Perl porting team.
273 If the bug you are reporting has security implications, which make it
274 inappropriate to send to a publicly archived mailing list, then please send
275 it to perl5-security-report@perl.org. This points to a closed subscription
276 unarchived mailing list, which includes all the core committers, who be able
277 to help assess the impact of issues, figure out a resolution, and help
278 co-ordinate the release of patches to mitigate or fix the problem across all
279 platforms on which Perl is supported. Please only use this address for
280 security issues in the Perl core, not for modules independently
285 The F<Changes> file for an explanation of how to view exhaustive details
288 The F<INSTALL> file for how to build Perl.
290 The F<README> file for general stuff.
292 The F<Artistic> and F<Copying> files for copyright information.