Deprecate use of := to mean an empty attribute list in my $pi := 4;
[p5sagit/p5-mst-13.2.git] / pod / perl5112delta.pod
CommitLineData
d5114285 1=head1 NAME
2
3[ Any text flagged as XXX needs to be processed before release. ]
4
5perldelta - what is new for perl v5.11.2
6
7=head1 DESCRIPTION
8
9This document describes differences between the 5.11.1 release and
10the 5.11.2 release.
11
12=head1 Notice
13
14XXX Unlikely to need this section.
15
16=head1 Incompatible Changes
17
d83f38d8 18=head2 Use of C<:=> to mean an empty attribute list is now deprecated.
d5114285 19
d83f38d8 20An accident of Perl's parser means that these constructions are all equivalent:
d5114285 21
d83f38d8 22 my $pi := 4;
23 my $pi : = 4;
24 my $pi : = 4;
25
26with the C<:> being treated as the start of an attribute list, which ends
27before the C<=>. As whitespace is not significant here, all are parsed as an
28empty attribute list, hence all the above are equivalent to, and better written
29as
30
31 my $pi = 4;
32
33because no attribute processing is done for an empty list.
34
35As is, this means that C<:=> cannot be used as a new token, without silently
36changing the meaning of existing code. Hence that particular form is now
37deprecated, and will become a syntax error. If it is absolutely necessary to
38have empty attribute lists (for example, because of a code generator) the
39avoid the warning by adding a space before the C<=>.
d5114285 40
41=head1 Core Enhancements
42
43XXX New core language features go here. Summarise user-visible core language
44enhancements. Particularly prominent performance optimisations could go
45here, but most should go in the L</Performance Enhancements> section.
46
47=head1 New Platforms
48
49XXX List any platforms that this version of perl compiles on, that previous
50versions did not. These will either be enabled by new files in the F<hints/>
51directories, or new subdirectories and F<README> files at the top level of the
52source tree.
53
54=head1 Modules and Pragmata
55
56XXX All changes to installed files in F<cpan/>, F<dist/>, F<ext/> and F<lib/>
57go here, in a list ordered by distribution name. Minimally it should be the
58module version, but it's more useful to the end user to give a paragraph's
59summary of the module's changes. In an ideal world, dual-life modules would
60have a F<Changes> file that could be cribbed.
61
62=head2 New Modules and Pragmata
63
64=over 4
65
66=item C<XXX>
67
68XXX
69
70=back
71
72=head2 Pragmata Changes
73
74=over 4
75
76=item C<XXX>
77
78XXX
79
80=back
81
82=head2 Updated Modules
83
84=over 4
85
86=item C<XXX>
87
88XXX
89
90=back
91
92=head1 Utility Changes
93
94XXX Changes to installed programs such as F<perlbug> and F<xsubpp> go
95here. Most of these are built within the directories F<utils> and F<x2p>.
96
97=over 4
98
99=item F<XXX>
100
101XXX
102
103=back
104
105=head1 New Documentation
106
107XXX Changes which create B<new> files in F<pod/> go here.
108
109=over 4
110
111=item L<XXX>
112
113XXX
114
115=back
116
117=head1 Changes to Existing Documentation
118
119XXX Changes which significantly change existing files in F<pod/> go here.
120Any changes to F<pod/perldiag.pod> should go in L</New or Changed Diagnostics>.
121
122
123=head1 Performance Enhancements
124
125XXX Changes which enhance performance without changing behaviour go here. There
126may well be none in a stable release.
127
128=over 4
129
130=item *
131
132XXX
133
134=back
135
136=head1 Installation and Configuration Improvements
137
138XXX Changes to F<Configure>, F<installperl>, F<installman>, and analogous tools
139go here.
140
141=head2 Configuration improvements
142
143XXX
144
145=head2 Compilation improvements
146
147XXX
148
149=head2 Platform Specific Changes
150
151=over 4
152
153=item XXX-some-platform
154
155XXX
156
157=back
158
159=head1 Selected Bug Fixes
160
161XXX Important bug fixes in the core language are summarised here.
162Bug fixes in files in F<ext/> and F<lib/> are best summarised in
163L</Modules and Pragmata>.
164
165=over 4
166
167=item *
168
169XXX
170
171=back
172
173=head1 New or Changed Diagnostics
174
175XXX New or changed warnings emitted by the core's C<C> code go here.
176
177=over 4
178
179=item C<XXX>
180
181XXX
182
183=back
184
185=head1 Changed Internals
186
d5114285 187=over 4
188
189=item *
190
879d0c72 191C<Perl_pmflag> has been removed from the public API. Calling it now generates
192a deprecation warning, and it will be removed in a future release. Although
193listed as part of the API, it was never documented, and only ever used in
194F<toke.c>, and prior to 5.10, F<regcomp.c>. In core, it has been replaced by a
195static function.
d5114285 196
197=back
198
199=head1 New Tests
200
201XXX Changes which create B<new> files in F<t/> go here. Changes to
202existing files in F<t/> aren't worth summarising, although the bugs that
203they represent may be.
204
205=over 4
206
207=item F<XXX>
208
209XXX
210
211=back
212
213=head1 Known Problems
214
215XXX Descriptions of platform agnostic bugs we know we can't fix go here. Any
216tests that had to be C<TODO>ed for the release would be noted here, unless
217they were specific to a particular platform (see below).
218
219This is a list of some significant unfixed bugs, which are regressions
220from either 5.10.1 or 5.11.1.
221
222=over 4
223
224=item *
225
226XXX
227
228=back
229
230=head1 Deprecations
231
232XXX Add any new known deprecations here.
233
234The following items are now deprecated.
235
236=over 4
237
238=item *
239
240XXX
241
242=back
243
244=head1 Platform Specific Notes
245
246XXX Any changes specific to a particular platform. VMS and Win32 are the usual
247stars here. It's probably best to group changes under the same section layout
248as the main perldelta
249
250=head1 Obituary
251
252XXX If any significant core contributor has died, we've added a short obituary
253here.
254
255=head1 Acknowledgements
256
257XXX The list of people to thank goes here.
258
259
260=head1 Reporting Bugs
261
262If you find what you think is a bug, you might check the articles
263recently posted to the comp.lang.perl.misc newsgroup and the perl
264bug database at http://rt.perl.org/perlbug/ . There may also be
265information at http://www.perl.org/ , the Perl Home Page.
266
267If you believe you have an unreported bug, please run the B<perlbug>
268program included with your release. Be sure to trim your bug down
269to a tiny but sufficient test case. Your bug report, along with the
270output of C<perl -V>, will be sent off to perlbug@perl.org to be
271analysed by the Perl porting team.
272
273If the bug you are reporting has security implications, which make it
274inappropriate to send to a publicly archived mailing list, then please send
275it to perl5-security-report@perl.org. This points to a closed subscription
276unarchived mailing list, which includes all the core committers, who be able
277to help assess the impact of issues, figure out a resolution, and help
278co-ordinate the release of patches to mitigate or fix the problem across all
279platforms on which Perl is supported. Please only use this address for
280security issues in the Perl core, not for modules independently
281distributed on CPAN.
282
283=head1 SEE ALSO
284
285The F<Changes> file for an explanation of how to view exhaustive details
286on what changed.
287
288The F<INSTALL> file for how to build Perl.
289
290The F<README> file for general stuff.
291
292The F<Artistic> and F<Copying> files for copyright information.
293
294=cut