Commit | Line | Data |
d5114285 |
1 | =head1 NAME |
2 | |
3 | [ Any text flagged as XXX needs to be processed before release. ] |
4 | |
5 | perldelta - what is new for perl v5.11.2 |
6 | |
7 | =head1 DESCRIPTION |
8 | |
9 | This document describes differences between the 5.11.1 release and |
10 | the 5.11.2 release. |
11 | |
12 | =head1 Notice |
13 | |
14 | XXX 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 |
20 | An 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 | |
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 |
29 | as |
30 | |
31 | my $pi = 4; |
32 | |
33 | because no attribute processing is done for an empty list. |
34 | |
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<=>. |
d5114285 |
40 | |
41 | =head1 Core Enhancements |
42 | |
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. |
46 | |
97352077 |
47 | =head2 qr overloading |
48 | |
49 | It is now possible to overload the C<qr//> operator, that is, conversion |
50 | to regexp, like it was already possible to overload conversion to |
51 | boolean, string or number of objects. It is invoked when an object |
52 | appears on the right hand side of the C<=~> operator, or when it is |
53 | interpolated into a regexp. See L<overload>. |
54 | |
88e1f1a2 |
55 | =head2 Pluggable keywords |
56 | |
57 | Extension modules can now cleanly hook into the Perl parser to define new |
58 | kinds of keyword-headed expression and compound statement. The syntax |
59 | following the keyword is defined entirely by the extension. This allow |
60 | a completely non-Perl sublanguage to be parsed inline, with the right |
61 | ops cleanly generated. |
62 | |
63 | This feature is currently considered experimental, and using it to do |
64 | anything interesting is difficult. Many necessary supporting facilities, |
65 | such as the lexer and the pad system, can only be accessed through |
66 | unsupported internal interfaces. It is intended that the Perl 5.13 |
67 | development cycle will see the addition of clean, supported interfaces |
68 | for many of these functions. In Perl 5.12 most uses of pluggable keywords |
69 | will be via L<Devel::Declare>. |
70 | |
71 | See L<perlapi/PL_keyword_plugin> for the mechanism. The Perl core source |
72 | distribution also includes a new module L<XS::APItest::KeywordRPN>, which |
73 | implements reverse Polish notation arithmetic via pluggable keywords. |
74 | This module is mainly used for test purposes, and is not normally |
75 | installed, but also serves as an example of how to use the new mechanism. |
76 | |
d5114285 |
77 | =head1 New Platforms |
78 | |
79 | XXX List any platforms that this version of perl compiles on, that previous |
80 | versions did not. These will either be enabled by new files in the F<hints/> |
81 | directories, or new subdirectories and F<README> files at the top level of the |
82 | source tree. |
83 | |
84 | =head1 Modules and Pragmata |
85 | |
86 | XXX All changes to installed files in F<cpan/>, F<dist/>, F<ext/> and F<lib/> |
87 | go here, in a list ordered by distribution name. Minimally it should be the |
88 | module version, but it's more useful to the end user to give a paragraph's |
89 | summary of the module's changes. In an ideal world, dual-life modules would |
90 | have a F<Changes> file that could be cribbed. |
91 | |
92 | =head2 New Modules and Pragmata |
93 | |
94 | =over 4 |
95 | |
96 | =item C<XXX> |
97 | |
98 | XXX |
99 | |
100 | =back |
101 | |
102 | =head2 Pragmata Changes |
103 | |
104 | =over 4 |
105 | |
106 | =item C<XXX> |
107 | |
108 | XXX |
109 | |
110 | =back |
111 | |
112 | =head2 Updated Modules |
113 | |
114 | =over 4 |
115 | |
116 | =item C<XXX> |
117 | |
118 | XXX |
119 | |
120 | =back |
121 | |
122 | =head1 Utility Changes |
123 | |
124 | XXX Changes to installed programs such as F<perlbug> and F<xsubpp> go |
125 | here. Most of these are built within the directories F<utils> and F<x2p>. |
126 | |
127 | =over 4 |
128 | |
129 | =item F<XXX> |
130 | |
131 | XXX |
132 | |
133 | =back |
134 | |
135 | =head1 New Documentation |
136 | |
137 | XXX Changes which create B<new> files in F<pod/> go here. |
138 | |
139 | =over 4 |
140 | |
141 | =item L<XXX> |
142 | |
143 | XXX |
144 | |
145 | =back |
146 | |
147 | =head1 Changes to Existing Documentation |
148 | |
149 | XXX Changes which significantly change existing files in F<pod/> go here. |
150 | Any changes to F<pod/perldiag.pod> should go in L</New or Changed Diagnostics>. |
151 | |
152 | |
153 | =head1 Performance Enhancements |
154 | |
155 | XXX Changes which enhance performance without changing behaviour go here. There |
156 | may well be none in a stable release. |
157 | |
158 | =over 4 |
159 | |
160 | =item * |
161 | |
162 | XXX |
163 | |
164 | =back |
165 | |
166 | =head1 Installation and Configuration Improvements |
167 | |
168 | XXX Changes to F<Configure>, F<installperl>, F<installman>, and analogous tools |
169 | go here. |
170 | |
171 | =head2 Configuration improvements |
172 | |
173 | XXX |
174 | |
175 | =head2 Compilation improvements |
176 | |
177 | XXX |
178 | |
179 | =head2 Platform Specific Changes |
180 | |
181 | =over 4 |
182 | |
183 | =item XXX-some-platform |
184 | |
185 | XXX |
186 | |
187 | =back |
188 | |
189 | =head1 Selected Bug Fixes |
190 | |
191 | XXX Important bug fixes in the core language are summarised here. |
192 | Bug fixes in files in F<ext/> and F<lib/> are best summarised in |
193 | L</Modules and Pragmata>. |
194 | |
195 | =over 4 |
196 | |
197 | =item * |
198 | |
199 | XXX |
200 | |
201 | =back |
202 | |
203 | =head1 New or Changed Diagnostics |
204 | |
205 | XXX New or changed warnings emitted by the core's C<C> code go here. |
206 | |
207 | =over 4 |
208 | |
209 | =item C<XXX> |
210 | |
211 | XXX |
212 | |
213 | =back |
214 | |
215 | =head1 Changed Internals |
216 | |
d5114285 |
217 | =over 4 |
218 | |
219 | =item * |
220 | |
879d0c72 |
221 | C<Perl_pmflag> has been removed from the public API. Calling it now generates |
222 | a deprecation warning, and it will be removed in a future release. Although |
223 | listed as part of the API, it was never documented, and only ever used in |
224 | F<toke.c>, and prior to 5.10, F<regcomp.c>. In core, it has been replaced by a |
225 | static function. |
d5114285 |
226 | |
227 | =back |
228 | |
229 | =head1 New Tests |
230 | |
231 | XXX Changes which create B<new> files in F<t/> go here. Changes to |
232 | existing files in F<t/> aren't worth summarising, although the bugs that |
233 | they represent may be. |
234 | |
235 | =over 4 |
236 | |
237 | =item F<XXX> |
238 | |
239 | XXX |
240 | |
241 | =back |
242 | |
243 | =head1 Known Problems |
244 | |
245 | XXX Descriptions of platform agnostic bugs we know we can't fix go here. Any |
246 | tests that had to be C<TODO>ed for the release would be noted here, unless |
247 | they were specific to a particular platform (see below). |
248 | |
249 | This is a list of some significant unfixed bugs, which are regressions |
250 | from either 5.10.1 or 5.11.1. |
251 | |
252 | =over 4 |
253 | |
254 | =item * |
255 | |
256 | XXX |
257 | |
258 | =back |
259 | |
260 | =head1 Deprecations |
261 | |
262 | XXX Add any new known deprecations here. |
263 | |
264 | The following items are now deprecated. |
265 | |
266 | =over 4 |
267 | |
268 | =item * |
269 | |
270 | XXX |
271 | |
272 | =back |
273 | |
274 | =head1 Platform Specific Notes |
275 | |
276 | XXX Any changes specific to a particular platform. VMS and Win32 are the usual |
277 | stars here. It's probably best to group changes under the same section layout |
278 | as the main perldelta |
279 | |
280 | =head1 Obituary |
281 | |
282 | XXX If any significant core contributor has died, we've added a short obituary |
283 | here. |
284 | |
285 | =head1 Acknowledgements |
286 | |
287 | XXX The list of people to thank goes here. |
288 | |
289 | |
290 | =head1 Reporting Bugs |
291 | |
292 | If you find what you think is a bug, you might check the articles |
293 | recently posted to the comp.lang.perl.misc newsgroup and the perl |
294 | bug database at http://rt.perl.org/perlbug/ . There may also be |
295 | information at http://www.perl.org/ , the Perl Home Page. |
296 | |
297 | If you believe you have an unreported bug, please run the B<perlbug> |
298 | program included with your release. Be sure to trim your bug down |
299 | to a tiny but sufficient test case. Your bug report, along with the |
300 | output of C<perl -V>, will be sent off to perlbug@perl.org to be |
301 | analysed by the Perl porting team. |
302 | |
303 | If the bug you are reporting has security implications, which make it |
304 | inappropriate to send to a publicly archived mailing list, then please send |
305 | it to perl5-security-report@perl.org. This points to a closed subscription |
306 | unarchived mailing list, which includes all the core committers, who be able |
307 | to help assess the impact of issues, figure out a resolution, and help |
308 | co-ordinate the release of patches to mitigate or fix the problem across all |
309 | platforms on which Perl is supported. Please only use this address for |
310 | security issues in the Perl core, not for modules independently |
311 | distributed on CPAN. |
312 | |
313 | =head1 SEE ALSO |
314 | |
315 | The F<Changes> file for an explanation of how to view exhaustive details |
316 | on what changed. |
317 | |
318 | The F<INSTALL> file for how to build Perl. |
319 | |
320 | The F<README> file for general stuff. |
321 | |
322 | The F<Artistic> and F<Copying> files for copyright information. |
323 | |
324 | =cut |