Commit | Line | Data |
---|---|---|
44691e6f AB |
1 | =encoding utf8 |
2 | ||
3 | =head1 NAME | |
4 | ||
5076a392 | 5 | perldelta - what is new for perl v5.14.0 |
c71a852f | 6 | |
5076a392 FC |
7 | =head1 DESCRIPTION |
8 | ||
9 | This document describes differences between the 5.12.0 release and | |
10 | the 5.14.0 release. | |
11 | ||
0980abf1 FC |
12 | If you are upgrading from an earlier release such as 5.10.0, first read |
13 | L<perl5120delta>, which describes differences between 5.10.0 and | |
14 | 5.12.0. | |
15 | ||
5076a392 FC |
16 | Some of the bug fixes in this release have been backported to subsequent |
17 | releases of 5.12.x. Those are indicated with the 5.12.x version in | |
18 | parentheses. | |
19 | ||
5076a392 FC |
20 | =head1 Notice |
21 | ||
22 | XXX Any important notices here | |
23 | ||
24 | =head1 Core Enhancements | |
25 | ||
1f539a1a | 26 | =head2 Unicode |
5076a392 | 27 | |
1f539a1a | 28 | =head3 Unicode Version 6.0 is now supported (mostly) |
5076a392 | 29 | |
1f539a1a FC |
30 | Perl comes with the Unicode 6.0 data base updated with |
31 | L<Corrigendum #8|http://www.unicode.org/versions/corrigendum8.html>, | |
32 | with one exception noted below. | |
33 | See L<http://unicode.org/versions/Unicode6.0.0> for details on the new | |
34 | release. Perl does not support any Unicode provisional properties, | |
a3c24add | 35 | including the new ones for this release. |
5076a392 | 36 | |
1f539a1a | 37 | Unicode 6.0 has chosen to use the name C<BELL> for the character at U+1F514, |
e1b1739f | 38 | which is a symbol that looks like a bell, and is used in Japanese cell |
1f539a1a FC |
39 | phones. This conflicts with the long-standing Perl usage of having |
40 | C<BELL> mean the ASCII C<BEL> character, U+0007. In Perl 5.14, | |
41 | C<\N{BELL}> will continue to mean U+0007, but its use will generate a | |
42 | deprecated warning message, unless such warnings are turned off. The | |
43 | new name for U+0007 in Perl will be C<ALERT>, which corresponds nicely | |
44 | with the existing shorthand sequence for it, C<"\a">. C<\N{BEL}> will | |
45 | mean U+0007, with no warning given. The character at U+1F514 will not | |
46 | have a name in 5.14, but can be referred to by C<\N{U+1F514}>. The plan | |
47 | is that in Perl 5.16, C<\N{BELL}> will refer to U+1F514, and so all code | |
48 | that uses C<\N{BELL}> should convert by then to using C<\N{ALERT}>, | |
49 | C<\N{BEL}>, or C<"\a"> instead. | |
5076a392 | 50 | |
1f539a1a | 51 | =head3 Full functionality for C<use feature 'unicode_strings'> |
5076a392 | 52 | |
1f539a1a FC |
53 | This release provides full functionality for C<use feature |
54 | 'unicode_strings'>. Under its scope, all string operations executed and | |
55 | regular expressions compiled (even if executed outside its scope) have | |
56 | Unicode semantics. See L<feature>. | |
5076a392 | 57 | |
1f539a1a FC |
58 | This feature avoids most forms of the "Unicode Bug" (See |
59 | L<perlunicode/The "Unicode Bug"> for details.) If there is a | |
60 | possibility that your code will process Unicode strings, you are | |
61 | B<strongly> encouraged to use this subpragma to avoid nasty surprises. | |
5076a392 | 62 | |
1f539a1a | 63 | =head3 C<\N{I<name>}> and C<charnames> enhancements |
5076a392 | 64 | |
1f539a1a | 65 | =over |
5076a392 | 66 | |
1f539a1a | 67 | =item * |
5076a392 FC |
68 | |
69 | C<\N{}> and C<charnames::vianame> now know about the abbreviated | |
e1b1739f FC |
70 | character names listed by Unicode, such as NBSP, SHY, LRO, ZWJ, etc., all |
71 | the customary abbreviations for the C0 and C1 control characters (such as | |
72 | ACK, BEL, CAN, etc.), and a few new variants of some C1 full names that | |
73 | are in common usage. | |
5076a392 | 74 | |
1f539a1a FC |
75 | =item * |
76 | ||
959ad7d5 FC |
77 | Unicode has a number of named character sequences, in which particular sequences |
78 | of code points are given names. C<\N{...}> now recognizes these. | |
79 | ||
1f539a1a FC |
80 | =item * |
81 | ||
959ad7d5 FC |
82 | C<\N{}>, C<charnames::vianame>, C<charnames::viacode> now know about every |
83 | character in Unicode. Previously, they didn't know about the Hangul syllables | |
84 | nor a number of CJK (Chinese/Japanese/Korean) characters. | |
85 | ||
1f539a1a FC |
86 | =item * |
87 | ||
5076a392 FC |
88 | In the past, it was ineffective to override one of Perl's abbreviations |
89 | with your own custom alias. Now it works. | |
90 | ||
1f539a1a FC |
91 | =item * |
92 | ||
e1b1739f | 93 | You can also create a custom alias of the ordinal of a |
5076a392 FC |
94 | character, known by C<\N{...}>, C<charnames::vianame()>, and |
95 | C<charnames::viacode()>. Previously, an alias had to be to an official | |
96 | Unicode character name. This made it impossible to create an alias for | |
e1b1739f FC |
97 | a code point that had no name, such as those reserved for private |
98 | use. | |
5076a392 | 99 | |
1f539a1a FC |
100 | =item * |
101 | ||
959ad7d5 FC |
102 | A new function, C<charnames::string_vianame()>, has been added. |
103 | This function is a run-time version of C<\N{...}>, returning the string | |
104 | of characters whose Unicode name is its parameter. It can handle | |
105 | Unicode named character sequences, whereas the pre-existing | |
106 | C<charnames::vianame()> cannot, as the latter returns a single code | |
107 | point. | |
108 | ||
1f539a1a FC |
109 | =back |
110 | ||
5076a392 FC |
111 | See L<charnames> for details on all these changes. |
112 | ||
22349846 KW |
113 | =head3 New warnings categories for problematic (non-)Unicode code points. |
114 | ||
115 | Three new warnings subcategories of "utf8" have been added. These | |
116 | allow you to turn off some "utf8" warnings, while allowing | |
117 | others warnings to remain on. The three categories are: | |
118 | C<surrogate> when UTF-16 surrogates are encountered; | |
119 | C<nonchar> when Unicode non-character code points are encountered; | |
120 | and C<non_unicode> when code points that are above the legal Unicode | |
121 | maximum of 0x10FFFF are encountered. | |
122 | ||
1f539a1a | 123 | =head3 Any unsigned value can be encoded as a character |
5076a392 | 124 | |
1f539a1a FC |
125 | With this release, Perl is adopting a model that any unsigned value can |
126 | be treated as a code point and encoded internally (as utf8) without | |
54c7bb16 | 127 | warnings - not just the code points that are legal in Unicode. |
22349846 KW |
128 | However, unless utf8 or the corresponding sub-category (see previous |
129 | item) warnings have been | |
1f539a1a FC |
130 | explicitly lexically turned off, outputting or performing a |
131 | Unicode-defined operation (such as upper-casing) on such a code point | |
132 | will generate a warning. Attempting to input these using strict rules | |
133 | (such as with the C<:encoding('UTF-8')> layer) will continue to fail. | |
134 | Prior to this release the handling was very inconsistent, and incorrect | |
135 | in places. Also, the Unicode non-characters, some of which previously were | |
136 | erroneously considered illegal in places by Perl, contrary to the Unicode | |
137 | standard, are now always legal internally. But inputting or outputting | |
138 | them will work the same as for the non-legal Unicode code points, as the | |
139 | Unicode standard says they are illegal for "open interchange". | |
5076a392 | 140 | |
1f539a1a | 141 | =head2 Regular Expressions |
5076a392 | 142 | |
1f539a1a | 143 | =head3 C<(?^...)> construct to signify default modifiers |
5076a392 | 144 | |
e1b1739f FC |
145 | An ASCII caret (also called a "circumflex accent") C<"^"> |
146 | immediately following a C<"(?"> in a regular expression | |
147 | now means that the subexpression does not inherit the | |
148 | surrounding modifiers such as C</i>, but reverts to the | |
5076a392 FC |
149 | Perl defaults. Any modifiers following the caret override the defaults. |
150 | ||
151 | The stringification of regular expressions now uses this | |
152 | notation. E.g., before, C<qr/hlagh/i> would be stringified as | |
153 | C<(?i-xsm:hlagh)>, but now it's stringified as C<(?^i:hlagh)>. | |
154 | ||
155 | The main purpose of this is to allow tests that rely on the | |
e1b1739f | 156 | stringification not to have to change when new modifiers are added. |
5076a392 FC |
157 | See L<perlre/Extended Patterns>. |
158 | ||
1f539a1a | 159 | =head3 C</d>, C</l>, C</u>, C</a>, and C</aa> modifiers |
5076a392 | 160 | |
959ad7d5 FC |
161 | Four new regular expression modifiers have been added. These are mutually |
162 | exclusive; one only can be turned on at a time. | |
5076a392 | 163 | |
959ad7d5 | 164 | The C</l> modifier says to compile the regular expression as if it were |
5076a392 FC |
165 | in the scope of C<use locale>, even if it is not. |
166 | ||
959ad7d5 | 167 | The C</u> modifier says to compile the regular expression as if it were |
5076a392 FC |
168 | in the scope of a C<use feature "unicode_strings"> pragma. |
169 | ||
e1b1739f | 170 | The C</d> (default) modifier is used to override any C<use locale> and |
5076a392 FC |
171 | C<use feature "unicode_strings"> pragmas that are in effect at the time |
172 | of compiling the regular expression. | |
173 | ||
959ad7d5 | 174 | The C</a> regular expression modifier restricts C<\s>, C<\d> and C<\w> and |
7baaf023 | 175 | the Posix (C<[[:posix:]]>) character classes to the ASCII range. Their |
959ad7d5 FC |
176 | complements and C<\b> and C<\B> are correspondingly |
177 | affected. Otherwise, C</a> behaves like the C</u> modifier, in that | |
e1b1739f | 178 | case-insensitive matching uses Unicode semantics. |
5076a392 | 179 | |
959ad7d5 FC |
180 | The C</aa> modifier is like C</a>, except that, in case-insensitive matching, no ASCII character will match a |
181 | non-ASCII character. For example, | |
5076a392 | 182 | |
959ad7d5 | 183 | 'k' =~ /\N{KELVIN SIGN}/ai |
5076a392 | 184 | |
959ad7d5 | 185 | will match; it won't under C</aa>. |
5076a392 | 186 | |
959ad7d5 | 187 | See L<perlre/Modifiers> for more detail. |
5076a392 | 188 | |
1f539a1a | 189 | =head3 Non-destructive substitution |
5076a392 | 190 | |
1f539a1a FC |
191 | The substitution (C<s///>) and transliteration |
192 | (C<y///>) operators now support an C</r> option that | |
193 | copies the input variable, carries out the substitution on | |
194 | the copy and returns the result. The original remains unmodified. | |
5076a392 | 195 | |
1f539a1a FC |
196 | my $old = 'cat'; |
197 | my $new = $old =~ s/cat/dog/r; | |
198 | # $old is 'cat' and $new is 'dog' | |
5076a392 | 199 | |
1f539a1a | 200 | This is particularly useful with C<map>. See L<perlop> for more examples. |
5076a392 | 201 | |
1f539a1a | 202 | =head3 Reentrant regular expression engine |
5076a392 | 203 | |
1f539a1a FC |
204 | It is now safe to use regular expressions within C<(?{...})> and |
205 | C<(??{...})> code blocks inside regular expressions. | |
5076a392 | 206 | |
1f539a1a | 207 | These block are still experimental, however, and still have problems with |
e1b1739f | 208 | lexical (C<my>) variables and abnormal exiting. |
5076a392 | 209 | |
1f539a1a | 210 | =head3 C<use re '/flags';> |
5076a392 FC |
211 | |
212 | The C<re> pragma now has the ability to turn on regular expression flags | |
213 | till the end of the lexical scope: | |
214 | ||
215 | use re '/x'; | |
216 | "foo" =~ / (.+) /; # /x implied | |
217 | ||
218 | See L<re/"'/flags' mode"> for details. | |
219 | ||
1f539a1a | 220 | =head3 \o{...} for octals |
5076a392 | 221 | |
e1b1739f FC |
222 | There is a new octal escape sequence, C<"\o">, in double-quote-like |
223 | contexts. This construct allows large octal ordinals beyond the | |
1f539a1a FC |
224 | current max of 0777 to be represented. It also allows you to specify a |
225 | character in octal which can safely be concatenated with other regex | |
226 | snippets and which won't be confused with being a backreference to | |
227 | a regex capture group. See L<perlre/Capture groups>. | |
228 | ||
229 | =head3 Add C<\p{Titlecase}> as a synonym for C<\p{Title}> | |
230 | ||
231 | This synonym is added for symmetry with the Unicode property names | |
232 | C<\p{Uppercase}> and C<\p{Lowercase}>. | |
5076a392 | 233 | |
1f539a1a FC |
234 | =head3 Regular expression debugging output improvement |
235 | ||
236 | Regular expression debugging output (turned on by C<use re 'debug';>) now | |
237 | uses hexadecimal when escaping non-ASCII characters, instead of octal. | |
238 | ||
1e463951 FC |
239 | =head3 Return value of C<delete $+{...}> |
240 | ||
241 | Custom regular expression engines can now determine the return value of | |
242 | C<delete> on an entry of C<%+> or C<%->. | |
243 | ||
1f539a1a FC |
244 | =head2 Syntactical Enhancements |
245 | ||
246 | =head3 Array and hash container functions accept references | |
5076a392 FC |
247 | |
248 | All built-in functions that operate directly on array or hash | |
249 | containers now also accept hard references to arrays or hashes: | |
250 | ||
251 | |----------------------------+---------------------------| | |
252 | | Traditional syntax | Terse syntax | | |
253 | |----------------------------+---------------------------| | |
254 | | push @$arrayref, @stuff | push $arrayref, @stuff | | |
255 | | unshift @$arrayref, @stuff | unshift $arrayref, @stuff | | |
256 | | pop @$arrayref | pop $arrayref | | |
257 | | shift @$arrayref | shift $arrayref | | |
258 | | splice @$arrayref, 0, 2 | splice $arrayref, 0, 2 | | |
259 | | keys %$hashref | keys $hashref | | |
260 | | keys @$arrayref | keys $arrayref | | |
261 | | values %$hashref | values $hashref | | |
262 | | values @$arrayref | values $arrayref | | |
263 | | ($k,$v) = each %$hashref | ($k,$v) = each $hashref | | |
264 | | ($k,$v) = each @$arrayref | ($k,$v) = each $arrayref | | |
265 | |----------------------------+---------------------------| | |
266 | ||
267 | This allows these built-in functions to act on long dereferencing chains | |
268 | or on the return value of subroutines without needing to wrap them in | |
269 | C<@{}> or C<%{}>: | |
270 | ||
271 | push @{$obj->tags}, $new_tag; # old way | |
272 | push $obj->tags, $new_tag; # new way | |
273 | ||
274 | for ( keys %{$hoh->{genres}{artists}} ) {...} # old way | |
275 | for ( keys $hoh->{genres}{artists} ) {...} # new way | |
276 | ||
277 | For C<push>, C<unshift> and C<splice>, the reference will auto-vivify | |
278 | if it is not defined, just as if it were wrapped with C<@{}>. | |
279 | ||
5076a392 FC |
280 | For C<keys>, C<values>, C<each>, when overloaded dereferencing is |
281 | present, the overloaded dereference is used instead of dereferencing the | |
e1b1739f FC |
282 | underlying reftype. Warnings are issued about assumptions made in |
283 | ambiguous cases. | |
5076a392 | 284 | |
1f539a1a FC |
285 | =head3 Single term prototype |
286 | ||
287 | The C<+> prototype is a special alternative to C<$> that will act like | |
288 | C<\[@%]> when given a literal array or hash variable, but will otherwise | |
e1b1739f | 289 | force scalar context on the argument. See L<perlsub/Prototypes>. |
1f539a1a FC |
290 | |
291 | =head3 C<package> block syntax | |
292 | ||
293 | A package declaration can now contain a code block, in which case the | |
294 | declaration is in scope only inside that block. So C<package Foo { ... }> | |
295 | is precisely equivalent to C<{ package Foo; ... }>. It also works with | |
296 | a version number in the declaration, as in C<package Foo 1.2 { ... }>. | |
e1b1739f | 297 | See L<perlfunc>. |
1f539a1a FC |
298 | |
299 | =head3 Statement labels can appear in more places | |
300 | ||
301 | Statement labels can now occur before any type of statement or declaration, | |
302 | such as C<package>. | |
303 | ||
304 | =head3 Stacked labels | |
305 | ||
306 | Multiple statement labels can now appear before a single statement. | |
307 | ||
308 | =head3 Uppercase X/B allowed in hexadecimal/binary literals | |
309 | ||
310 | Literals may now use either upper case C<0X...> or C<0B...> prefixes, | |
311 | in addition to the already supported C<0x...> and C<0b...> | |
e1b1739f | 312 | syntax [perl #76296]. |
1f539a1a FC |
313 | |
314 | C, Ruby, Python and PHP already supported this syntax, and it makes | |
315 | Perl more internally consistent. A round-trip with C<eval sprintf | |
e1b1739f | 316 | "%#X", 0x10> now returns C<16>, the way C<eval sprintf "%#x", 0x10> does. |
1f539a1a | 317 | |
1e463951 FC |
318 | =head3 Overridable tie functions |
319 | ||
320 | C<tie>, C<tied> and C<untie> can now be overridden [perl #75902]. | |
321 | ||
1f539a1a FC |
322 | =head2 Exception Handling |
323 | ||
324 | Several changes have been made to the way C<die>, C<warn>, and C<$@> | |
325 | behave, in order to make them more reliable and consistent. | |
326 | ||
327 | When an exception is thrown inside an C<eval>, the exception is no | |
328 | longer at risk of being clobbered by code running during unwinding | |
329 | (e.g., destructors). Previously, the exception was written into C<$@> | |
330 | early in the throwing process, and would be overwritten if C<eval> was | |
331 | used internally in the destructor for an object that had to be freed | |
332 | while exiting from the outer C<eval>. Now the exception is written | |
333 | into C<$@> last thing before exiting the outer C<eval>, so the code | |
334 | running immediately thereafter can rely on the value in C<$@> correctly | |
335 | corresponding to that C<eval>. (C<$@> is still also set before exiting the | |
336 | C<eval>, for the sake of destructors that rely on this.) | |
337 | ||
338 | Likewise, a C<local $@> inside an C<eval> will no longer clobber any | |
339 | exception thrown in its scope. Previously, the restoration of C<$@> upon | |
340 | unwinding would overwrite any exception being thrown. Now the exception | |
341 | gets to the C<eval> anyway. So C<local $@> is safe before a C<die>. | |
342 | ||
343 | Exceptions thrown from object destructors no longer modify the C<$@> | |
344 | of the surrounding context. (If the surrounding context was exception | |
345 | unwinding, this used to be another way to clobber the exception being | |
346 | thrown.) Previously such an exception was | |
347 | sometimes emitted as a warning, and then either was | |
348 | string-appended to the surrounding C<$@> or completely replaced the | |
349 | surrounding C<$@>, depending on whether that exception and the surrounding | |
350 | C<$@> were strings or objects. Now, an exception in this situation is | |
351 | always emitted as a warning, leaving the surrounding C<$@> untouched. | |
352 | In addition to object destructors, this also affects any function call | |
353 | performed by XS code using the C<G_KEEPERR> flag. | |
354 | ||
355 | Warnings for C<warn> can now be objects, in the same way as exceptions | |
356 | for C<die>. If an object-based warning gets the default handling, | |
357 | of writing to standard error, it is stringified as | |
358 | before, with the file and line number appended. But | |
359 | a C<$SIG{__WARN__}> handler will now receive an | |
360 | object-based warning as an object, where previously it was passed the | |
361 | result of stringifying the object. | |
362 | ||
363 | =head2 Other Enhancements | |
364 | ||
365 | =head3 Assignment to C<$0> sets the legacy process name with C<prctl()> on Linux | |
366 | ||
367 | On Linux the legacy process name will be set with L<prctl(2)>, in | |
368 | addition to altering the POSIX name via C<argv[0]> as perl has done | |
369 | since version 4.000. Now system utilities that read the legacy process | |
370 | name such as ps, top and killall will recognize the name you set when | |
371 | assigning to C<$0>. The string you supply will be cut off at 16 bytes, | |
372 | this is a limitation imposed by Linux. | |
373 | ||
374 | =head3 C<srand()> now returns the seed | |
375 | ||
e1b1739f FC |
376 | This allows programs that need to have repeatable results not to have to come |
377 | up with their own seed-generating mechanism. Instead, they can use C<srand()> | |
378 | and stash the return value for future use. Typical is a test program which | |
1f539a1a | 379 | has too many combinations to test comprehensively in the time available to it |
e1b1739f | 380 | each run. It can test a random subset each time and, should there be a failure, |
1f539a1a | 381 | log the seed used for that run so that it can later be used to reproduce the |
e1b1739f | 382 | same results. |
1f539a1a FC |
383 | |
384 | =head3 printf-like functions understand post-1980 size modifiers | |
385 | ||
386 | Perl's printf and sprintf operators, and Perl's internal printf replacement | |
387 | function, now understand the C90 size modifiers "hh" (C<char>), "z" | |
388 | (C<size_t>), and "t" (C<ptrdiff_t>). Also, when compiled with a C99 | |
389 | compiler, Perl now understands the size modifier "j" (C<intmax_t>). | |
390 | ||
391 | So, for example, on any modern machine, C<sprintf('%hhd', 257)> returns '1'. | |
392 | ||
393 | =head3 New global variable C<${^GLOBAL_PHASE}> | |
5076a392 FC |
394 | |
395 | A new global variable, C<${^GLOBAL_PHASE}>, has been added to allow | |
396 | introspection of the current phase of the perl interpreter. It's explained in | |
397 | detail in L<perlvar/"${^GLOBAL_PHASE}"> and | |
398 | L<perlmod/"BEGIN, UNITCHECK, CHECK, INIT and END">. | |
399 | ||
1f539a1a | 400 | =head3 C<-d:-foo> calls C<Devel::foo::unimport> |
5076a392 FC |
401 | |
402 | The syntax C<-dI<B<:>foo>> was extended in 5.6.1 to make C<-dI<:fooB<=bar>>> | |
403 | equivalent to C<-MDevel::foo=bar>, which expands | |
404 | internally to C<use Devel::foo 'bar';>. | |
405 | F<perl> now allows prefixing the module name with C<->, with the same | |
406 | semantics as C<-M>, I<i.e.> | |
407 | ||
408 | =over 4 | |
409 | ||
410 | =item C<-d:-foo> | |
411 | ||
412 | Equivalent to C<-M-Devel::foo>, expands to | |
413 | C<no Devel::foo;>, calls C<< Devel::foo->unimport() >> | |
414 | if the method exists. | |
415 | ||
416 | =item C<-d:-foo=bar> | |
417 | ||
418 | Equivalent to C<-M-Devel::foo=bar>, expands to C<no Devel::foo 'bar';>, | |
419 | calls C<< Devel::foo->unimport('bar') >> if the method exists. | |
420 | ||
421 | =back | |
422 | ||
e1b1739f | 423 | This is particularly useful for suppressing the default actions of a |
5076a392 FC |
424 | C<Devel::*> module's C<import> method whilst still loading it for debugging. |
425 | ||
1f539a1a | 426 | =head3 Filehandle method calls load L<IO::File> on demand |
5076a392 FC |
427 | |
428 | When a method call on a filehandle would die because the method cannot | |
429 | be resolved, and L<IO::File> has not been loaded, Perl now loads L<IO::File> | |
430 | via C<require> and attempts method resolution again: | |
431 | ||
432 | open my $fh, ">", $file; | |
433 | $fh->binmode(":raw"); # loads IO::File and succeeds | |
434 | ||
435 | This also works for globs like STDOUT, STDERR and STDIN: | |
436 | ||
437 | STDOUT->autoflush(1); | |
438 | ||
439 | Because this on-demand load only happens if method resolution fails, the | |
440 | legacy approach of manually loading an L<IO::File> parent class for partial | |
441 | method support still works as expected: | |
442 | ||
443 | use IO::Handle; | |
444 | open my $fh, ">", $file; | |
445 | $fh->autoflush(1); # IO::File not loaded | |
446 | ||
1984204c FC |
447 | =head3 IPv6 support |
448 | ||
449 | The C<Socket> module provides new affordances for IPv6, | |
450 | including implementations of the C<Socket::getaddrinfo()> and | |
451 | C<Socket::getnameinfo()> functions, along with related constants, and a | |
452 | handful of new functions. See L<Socket>. | |
453 | ||
1f539a1a | 454 | =head3 DTrace probes now include package name |
5076a392 FC |
455 | |
456 | The DTrace probes now include an additional argument (C<arg3>) which contains | |
457 | the package the subroutine being entered or left was compiled in. | |
458 | ||
459 | For example using the following DTrace script: | |
460 | ||
461 | perl$target:::sub-entry | |
462 | { | |
463 | printf("%s::%s\n", copyinstr(arg0), copyinstr(arg3)); | |
464 | } | |
465 | ||
466 | and then running: | |
467 | ||
468 | perl -e'sub test { }; test' | |
469 | ||
470 | DTrace will print: | |
471 | ||
472 | main::test | |
473 | ||
9378886b FC |
474 | =head2 New C APIs |
475 | ||
1e463951 | 476 | See L</Internal Changes>. |
9378886b | 477 | |
5076a392 FC |
478 | =head1 Security |
479 | ||
948b8455 | 480 | =head2 User-defined regular expression properties |
5076a392 FC |
481 | |
482 | In L<perlunicode/"User-Defined Character Properties">, it says you can | |
483 | create custom properties by defining subroutines whose names begin with | |
948b8455 FC |
484 | "In" or "Is". However, Perl did not actually enforce that naming |
485 | restriction, so \p{foo::bar} could call foo::bar() if it existed. Now this | |
486 | convention has been enforced. | |
5076a392 | 487 | |
948b8455 FC |
488 | Also, Perl no longer allows a tainted regular expression to invoke a |
489 | user-defined. It simply dies instead [perl #82616]. | |
5076a392 FC |
490 | |
491 | =head1 Incompatible Changes | |
492 | ||
61752d82 FC |
493 | Perl 5.14.0 is not binary-compatible with any previous stable release. |
494 | ||
1e463951 FC |
495 | In addition to the sections that follow, see L</C API Changes>. |
496 | ||
61752d82 FC |
497 | =head2 Regular Expressions and String Escapes |
498 | ||
54c7bb16 | 499 | =head3 \400-\777 |
5076a392 | 500 | |
54c7bb16 | 501 | Use of C<\400>-C<\777> in regexes in certain circumstances has given |
5076a392 FC |
502 | different, anomalous behavior than their use in all other |
503 | double-quote-like contexts. Since 5.10.1, a deprecated warning message | |
504 | has been raised when this happens. Now, all double-quote-like contexts | |
505 | have the same behavior, namely to be equivalent to C<\x{100}> - | |
506 | C<\x{1FF}>, with no deprecation warning. Use of these values in the | |
507 | command line option C<"-0"> retains the current meaning to slurp input | |
508 | files whole; previously, this was documented only for C<"-0777">. It is | |
509 | recommended, however, because of various ambiguities, to use the new | |
510 | C<\o{...}> construct to represent characters in octal. | |
5076a392 | 511 | |
61752d82 | 512 | =head3 Most C<\p{}> properties are now immune to case-insensitive matching |
5076a392 | 513 | |
61752d82 FC |
514 | For most Unicode properties, it doesn't make sense to have them match |
515 | differently under C</i> case-insensitive matching than not. And doing | |
516 | so leads to unexpected results and potential security holes. For | |
517 | example | |
5076a392 | 518 | |
61752d82 | 519 | m/\p{ASCII_Hex_Digit}+/i |
5076a392 | 520 | |
61752d82 FC |
521 | could previously match non-ASCII characters because of the Unicode |
522 | matching rules. There were a number of bugs in this feature until an | |
523 | earlier release in the 5.13 series. Now this release reverts, and | |
524 | removes the feature completely except for the few properties where | |
525 | people have come to expect it, namely the ones where casing is an | |
526 | integral part of their functionality, such as C<m/\p{Uppercase}/i> and | |
527 | C<m/\p{Lowercase}/i>, both of which match the exact same code points, | |
528 | namely those matched by C<m/\p{Cased}/i>. Details are in | |
529 | L<perlrecharclass/Unicode Properties>. | |
5076a392 | 530 | |
61752d82 FC |
531 | XXX The mention of ‘until an earlier release in the 5.13 series’ needs to |
532 | change, but I do not fully understand what happened here. | |
5076a392 | 533 | |
61752d82 FC |
534 | User-defined property handlers that need to match differently under |
535 | C</i> must change to read the new boolean parameter passed to it which is | |
536 | non-zero if case-insensitive matching is in effect or 0 otherwise. See | |
537 | L<perluniprops/User-Defined Character Properties>. | |
5076a392 | 538 | |
61752d82 | 539 | =head3 \p{} implies Unicode semantics |
5076a392 | 540 | |
61752d82 FC |
541 | Now, a Unicode property match specified in the pattern will indicate |
542 | that the pattern is meant for matching according to Unicode rules, the way | |
543 | C<\x{}> does. | |
5076a392 | 544 | |
61752d82 | 545 | =head3 Regular expressions retain their localeness when interpolated |
5076a392 | 546 | |
61752d82 FC |
547 | Regular expressions compiled under C<"use locale"> now retain this when |
548 | interpolated into a new regular expression compiled outside a | |
549 | C<"use locale">, and vice-versa. | |
5076a392 | 550 | |
61752d82 FC |
551 | Previously, a regular expression interpolated into another one inherited |
552 | the localeness of the surrounding one, losing whatever state it | |
553 | originally had. This is considered a bug fix, but may trip up code that | |
554 | has come to rely on the incorrect behavior. | |
5076a392 | 555 | |
61752d82 | 556 | =head3 Stringification of regexes has changed |
5076a392 FC |
557 | |
558 | Default regular expression modifiers are now notated by using | |
559 | C<(?^...)>. Code relying on the old stringification will fail. The | |
560 | purpose of this is so that when new modifiers are added, such code will | |
561 | not have to change (after this one time), as the stringification will | |
562 | automatically incorporate the new modifiers. | |
563 | ||
564 | Code that needs to work properly with both old- and new-style regexes | |
f318e2e6 | 565 | can avoid the whole issue by using (for Perls since 5.9.5; see L<re>): |
5076a392 FC |
566 | |
567 | use re qw(regexp_pattern); | |
568 | my ($pat, $mods) = regexp_pattern($re_ref); | |
569 | ||
5076a392 FC |
570 | If the actual stringification is important, or older Perls need to be |
571 | supported, you can use something like the following: | |
572 | ||
573 | # Accept both old and new-style stringification | |
574 | my $modifiers = (qr/foobar/ =~ /\Q(?^/) ? '^' : '-xism'; | |
575 | ||
576 | And then use C<$modifiers> instead of C<-xism>. | |
577 | ||
61752d82 | 578 | =head3 Run-time code blocks in regular expressions inherit pragmata |
5076a392 | 579 | |
61752d82 FC |
580 | Code blocks in regular expressions (C<(?{...})> and C<(??{...})>) used not |
581 | to inherit any pragmata (strict, warnings, etc.) if the regular expression | |
582 | was compiled at run time as happens in cases like these two: | |
5076a392 | 583 | |
61752d82 FC |
584 | use re 'eval'; |
585 | $foo =~ $bar; # when $bar contains (?{...}) | |
586 | $foo =~ /$bar(?{ $finished = 1 })/; | |
587 | ||
588 | This was a bug, which has now been fixed. But it has the potential to break | |
589 | any code that was relying on it. | |
5076a392 | 590 | |
61752d82 | 591 | =head2 Stashes and Package Variables |
5076a392 | 592 | |
61752d82 | 593 | =head3 Localised tied hashes and arrays are no longed tied |
5076a392 | 594 | |
61752d82 | 595 | In the following: |
5076a392 | 596 | |
61752d82 FC |
597 | tie @a, ...; |
598 | { | |
599 | local @a; | |
600 | # here, @a is a now a new, untied array | |
601 | } | |
602 | # here, @a refers again to the old, tied array | |
5076a392 | 603 | |
61752d82 FC |
604 | The new local array used to be made tied too, which was fairly pointless, |
605 | and has now been fixed. This fix could however potentially cause a change | |
606 | in behaviour of some code. | |
5076a392 | 607 | |
61752d82 | 608 | =head3 Stashes are now always defined |
5076a392 | 609 | |
61752d82 FC |
610 | C<defined %Foo::> now always returns true, even when no symbols have yet been |
611 | defined in that package. | |
5076a392 | 612 | |
61752d82 FC |
613 | This is a side effect of removing a special case kludge in the tokeniser, |
614 | added for 5.10.0, to hide side effects of changes to the internal storage of | |
615 | hashes that drastically reduce their memory usage overhead. | |
616 | ||
617 | Calling defined on a stash has been deprecated since 5.6.0, warned on | |
618 | lexicals since 5.6.0, and warned for stashes (and other package | |
619 | variables) since 5.12.0. C<defined %hash> has always exposed an | |
620 | implementation detail - emptying a hash by deleting all entries from it does | |
621 | not make C<defined %hash> false, hence C<defined %hash> is not valid code to | |
622 | determine whether an arbitrary hash is empty. Instead, use the behaviour | |
623 | that an empty C<%hash> always returns false in a scalar context. | |
624 | ||
625 | =head3 Dereferencing typeglobs | |
5076a392 FC |
626 | |
627 | If you assign a typeglob to a scalar variable: | |
628 | ||
629 | $glob = *foo; | |
630 | ||
631 | the glob that is copied to C<$glob> is marked with a special flag | |
632 | indicating that the glob is just a copy. This allows subsequent assignments | |
633 | to C<$glob> to overwrite the glob. The original glob, however, is | |
634 | immutable. | |
635 | ||
636 | Many Perl operators did not distinguish between these two types of globs. | |
637 | This would result in strange behaviour in edge cases: C<untie $scalar> | |
638 | would do nothing if the last thing assigned to the scalar was a glob | |
639 | (because it treated it as C<untie *$scalar>, which unties a handle). | |
f318e2e6 | 640 | Assignment to a glob slot (e.g., C<*$glob = \@some_array>) would simply |
5076a392 FC |
641 | assign C<\@some_array> to C<$glob>. |
642 | ||
643 | To fix this, the C<*{}> operator (including the C<*foo> and C<*$foo> forms) | |
644 | has been modified to make a new immutable glob if its operand is a glob | |
e262cb24 FC |
645 | copy. This allows operators that make a distinction between globs and |
646 | scalars to be modified to treat only immutable globs as globs. (C<tie>, | |
647 | C<tied> and C<untie> have been left as they are for compatibility's sake, | |
61752d82 | 648 | but will warn. See L</Deprecations>.) |
5076a392 FC |
649 | |
650 | This causes an incompatible change in code that assigns a glob to the | |
651 | return value of C<*{}> when that operator was passed a glob copy. Take the | |
652 | following code, for instance: | |
653 | ||
654 | $glob = *foo; | |
655 | *$glob = *bar; | |
656 | ||
657 | The C<*$glob> on the second line returns a new immutable glob. That new | |
658 | glob is made an alias to C<*bar>. Then it is discarded. So the second | |
659 | assignment has no effect. | |
660 | ||
5076a392 FC |
661 | See L<http://rt.perl.org/rt3/Public/Bug/Display.html?id=77810> for even |
662 | more detail. | |
663 | ||
61752d82 | 664 | =head3 Clearing stashes |
5076a392 FC |
665 | |
666 | Stash list assignment C<%foo:: = ()> used to make the stash anonymous | |
667 | temporarily while it was being emptied. Consequently, any of its | |
668 | subroutines referenced elsewhere would become anonymous (showing up as | |
669 | "(unknown)" in C<caller>). Now they retain their package names, such that | |
670 | C<caller> will return the original sub name if there is still a reference | |
671 | to its typeglob, or "foo::__ANON__" otherwise [perl #79208]. | |
672 | ||
61752d82 FC |
673 | =head3 Magic variables outside the main package |
674 | ||
675 | In previous versions of Perl, magic variables like C<$!>, C<%SIG>, etc. would | |
676 | 'leak' into other packages. So C<%foo::SIG> could be used to access signals, | |
677 | C<${"foo::!"}> (with strict mode off) to access C's C<errno>, etc. | |
678 | ||
679 | This was a bug, or an 'unintentional' feature, which caused various ill effects, | |
680 | such as signal handlers being wiped when modules were loaded, etc. | |
681 | ||
682 | This has been fixed (or the feature has been removed, depending on how you see | |
683 | it). | |
684 | ||
685 | =head2 Changes to Syntax or to Perl Operators | |
686 | ||
687 | =head3 C<given> return values | |
688 | ||
689 | C<given> blocks now return the last evaluated | |
690 | expression, or an empty list if the block was exited by C<break>. Thus you | |
691 | can now write: | |
692 | ||
693 | my $type = do { | |
694 | given ($num) { | |
695 | break when undef; | |
696 | 'integer' when /^[+-]?[0-9]+$/; | |
697 | 'float' when /^[+-]?[0-9]+(?:\.[0-9]+)?$/; | |
698 | 'unknown'; | |
699 | } | |
700 | }; | |
701 | ||
702 | See L<perlsyn/Return value> for details. | |
703 | ||
704 | =head3 Change in the parsing of certain prototypes | |
705 | ||
706 | Functions declared with the following prototypes now behave correctly as unary | |
707 | functions: | |
708 | ||
709 | * | |
710 | \$ \% \@ \* \& | |
711 | \[...] | |
712 | ;$ ;* | |
713 | ;\$ ;\% etc. | |
714 | ;\[...] | |
715 | ||
716 | Due to this bug fix [perl #75904], functions | |
717 | using the C<(*)>, C<(;$)> and C<(;*)> prototypes | |
718 | are parsed with higher precedence than before. So in the following example: | |
719 | ||
720 | sub foo($); | |
721 | foo $a < $b; | |
722 | ||
723 | the second line is now parsed correctly as C<< foo($a) < $b >>, rather than | |
724 | C<< foo($a < $b) >>. This happens when one of these operators is used in | |
725 | an unparenthesised argument: | |
726 | ||
727 | < > <= >= lt gt le ge | |
728 | == != <=> eq ne cmp ~~ | |
729 | & | |
730 | | ^ | |
731 | && | |
732 | || // | |
733 | .. ... | |
734 | ?: | |
735 | = += -= *= etc. | |
736 | ||
737 | =head3 Smart-matching against array slices | |
738 | ||
739 | Previously, the following code resulted in a successful match: | |
740 | ||
741 | my @a = qw(a y0 z); | |
742 | my @b = qw(a x0 z); | |
743 | @a[0 .. $#b] ~~ @b; | |
744 | ||
745 | This odd behaviour has now been fixed [perl #77468]. | |
746 | ||
747 | =head3 Negation treats strings differently from before | |
748 | ||
749 | The unary negation operator C<-> now treats strings that look like numbers | |
750 | as numbers [perl #57706]. | |
751 | ||
752 | =head3 Negative zero | |
753 | ||
754 | Negative zero (-0.0), when converted to a string, now becomes "0" on all | |
755 | platforms. It used to become "-0" on some, but "0" on others. | |
756 | ||
757 | If you still need to determine whether a zero is negative, use | |
758 | C<sprintf("%g", $zero) =~ /^-/> or the L<Data::Float> module on CPAN. | |
759 | ||
760 | =head3 C<:=> is now a syntax error | |
5076a392 FC |
761 | |
762 | Previously C<my $pi := 4;> was exactly equivalent to C<my $pi : = 4;>, | |
763 | with the C<:> being treated as the start of an attribute list, ending before | |
764 | the C<=>. The use of C<:=> to mean C<: => was deprecated in 5.12.0, and is now | |
765 | a syntax error. This will allow the future use of C<:=> as a new token. | |
766 | ||
767 | We find no Perl 5 code on CPAN using this construction, outside the core's | |
768 | tests for it, so we believe that this change will have very little impact on | |
769 | real-world codebases. | |
770 | ||
771 | If it is absolutely necessary to have empty attribute lists (for example, | |
772 | because of a code generator) then avoid the error by adding a space before | |
773 | the C<=>. | |
774 | ||
61752d82 | 775 | =head2 Threads and Processes |
5076a392 | 776 | |
61752d82 | 777 | =head3 Directory handles not copied to threads |
5076a392 | 778 | |
61752d82 FC |
779 | On systems other than Windows that do not have |
780 | a C<fchdir> function, newly-created threads no | |
781 | longer inherit directory handles from their parent threads. Such programs | |
782 | would usually have crashed anyway [perl #75154]. | |
5076a392 | 783 | |
61752d82 | 784 | =head3 C<close> on shared pipes |
5076a392 | 785 | |
61752d82 FC |
786 | The C<close> function no longer waits for the child process to exit if the |
787 | underlying file descriptor is still in use by another thread, to avoid | |
788 | deadlocks. It returns true in such cases. | |
5076a392 | 789 | |
144b6ea2 FC |
790 | =head3 fork() emulation will not wait for signalled children |
791 | ||
792 | On Windows parent processes would not terminate until all forked | |
793 | childred had terminated first. However, C<kill('KILL', ...)> is | |
794 | inherently unstable on pseudo-processes, and C<kill('TERM', ...)> | |
795 | might not get delivered if the child if blocked in a system call. | |
796 | ||
797 | To avoid the deadlock and still provide a safe mechanism to terminate | |
798 | the hosting process, Perl will now no longer wait for children that | |
799 | have been sent a SIGTERM signal. It is up to the parent process to | |
800 | waitpid() for these children if child clean-up processing must be | |
801 | allowed to finish. However, it is also the responsibility of the | |
802 | parent then to avoid the deadlock by making sure the child process | |
803 | can't be blocked on I/O either. | |
804 | ||
805 | See L<perlfork> for more information about the fork() emulation on | |
806 | Windows. | |
807 | ||
61752d82 | 808 | =head2 Configuration |
5076a392 | 809 | |
61752d82 | 810 | =head3 Naming fixes in Policy_sh.SH may invalidate Policy.sh |
5076a392 | 811 | |
61752d82 FC |
812 | Several long-standing typos and naming confusions in Policy_sh.SH have |
813 | been fixed, standardizing on the variable names used in config.sh. | |
5076a392 | 814 | |
61752d82 FC |
815 | This will change the behavior of Policy.sh if you happen to have been |
816 | accidentally relying on the Policy.sh incorrect behavior. | |
f318e2e6 | 817 | |
5a1f7719 FC |
818 | =head3 Perl source code is read in text mode on Windows |
819 | ||
820 | Perl scripts used to be read in binary mode on Windows for the benefit | |
821 | of the ByteLoader module (which is no longer part of core Perl). This | |
822 | had the side effect of breaking various operations on the DATA filehandle, | |
823 | including seek()/tell(), and even simply reading from DATA after file handles | |
824 | have been flushed by a call to system(), backticks, fork() etc. | |
825 | ||
826 | The default build options for Windows have been changed to read Perl source | |
827 | code on Windows in text mode now. Hopefully ByteLoader will be updated on | |
828 | CPAN to automatically handle this situation [perl #28106]. | |
829 | ||
5076a392 FC |
830 | =head1 Deprecations |
831 | ||
1e463951 FC |
832 | See also L</Deprecated C APIs>. |
833 | ||
5076a392 FC |
834 | =head2 Omitting a space between a regular expression and subsequent word |
835 | ||
18139a1b FC |
836 | Omitting a space between a regular expression operator or |
837 | its modifiers and the following word is deprecated. For | |
838 | example, C<< m/foo/sand $bar >> will still be parsed | |
839 | as C<< m/foo/s and $bar >> but will issue a warning. | |
5076a392 | 840 | |
e683df94 KW |
841 | =head2 C<\cI<X>> |
842 | ||
843 | The backslash-c construct was designed as a way of specifying | |
844 | non-printable characters, but there were no restrictions (on ASCII | |
845 | platforms) on what the character following the C<c> could be. Now, | |
846 | a deprecation warning is raised if that character isn't an ASCII character. | |
847 | Also, a deprecation warning is raised for C<"\c{"> (which is the same | |
848 | as simply saying C<";">). | |
849 | ||
4528361d KW |
850 | =head2 C<"\b{"> and C<"\B{"> |
851 | ||
852 | In regular expressions, a literal C<"{"> immediately following a C<"\b"> | |
853 | (not in a bracketed character class) or a C<"\B{"> is now deprecated | |
854 | to allow for its future use by Perl itself. | |
855 | ||
5076a392 FC |
856 | =head2 Deprecation warning added for deprecated-in-core .pl libs |
857 | ||
858 | This is a mandatory warning, not obeying -X or lexical warning bits. | |
859 | The warning is modelled on that supplied by deprecate.pm for | |
860 | deprecated-in-core .pm libraries. It points to the specific CPAN | |
823d0e46 FC |
861 | distribution that contains the .pl libraries. The CPAN version, of |
862 | course, does not generate the warning. | |
5076a392 FC |
863 | |
864 | =head2 List assignment to C<$[> | |
865 | ||
823d0e46 FC |
866 | Assignment to C<$[> was deprecated and started to give warnings in |
867 | Perl version 5.12.0. This version of perl also starts to emit a warning when | |
868 | assigning to C<$[> in list context. This fixes an oversight in 5.12.0. | |
5076a392 FC |
869 | |
870 | =head2 Use of qw(...) as parentheses | |
871 | ||
872 | Historically the parser fooled itself into thinking that C<qw(...)> literals | |
873 | were always enclosed in parentheses, and as a result you could sometimes omit | |
874 | parentheses around them: | |
875 | ||
876 | for $x qw(a b c) { ... } | |
877 | ||
878 | The parser no longer lies to itself in this way. Wrap the list literal in | |
823d0e46 | 879 | parentheses, like this: |
5076a392 FC |
880 | |
881 | for $x (qw(a b c)) { ... } | |
882 | ||
883 | =head2 C<\N{BELL}> is deprecated | |
884 | ||
885 | This is because Unicode is using that name for a different character. | |
886 | See L</Unicode Version 6.0 is now supported (mostly)> for more | |
887 | explanation. | |
888 | ||
889 | =head2 C<?PATTERN?> is deprecated | |
890 | ||
891 | C<?PATTERN?> (without the initial m) has been deprecated and now produces | |
892 | a warning. This is to allow future use of C<?> in new operators. | |
893 | The match-once functionality is still available in the form of C<m?PATTERN?>. | |
894 | ||
5076a392 FC |
895 | =head2 Tie functions on scalars holding typeglobs |
896 | ||
897 | Calling a tie function (C<tie>, C<tied>, C<untie>) with a scalar argument | |
898 | acts on a file handle if the scalar happens to hold a typeglob. | |
899 | ||
900 | This is a long-standing bug that will be removed in Perl 5.16, as | |
901 | there is currently no way to tie the scalar itself when it holds | |
902 | a typeglob, and no way to untie a scalar that has had a typeglob | |
903 | assigned to it. | |
904 | ||
823d0e46 | 905 | Now there is a deprecation warning whenever a tie |
5076a392 FC |
906 | function is used on a handle without an explicit C<*>. |
907 | ||
18139a1b | 908 | =head2 User-defined case-mapping |
5076a392 | 909 | |
18139a1b FC |
910 | This feature is being deprecated due to its many issues, as documented in |
911 | L<perlunicode/User-Defined Case Mappings (for serious hackers only)>. | |
bb5c3f11 KW |
912 | It is planned to remove this feature in Perl 5.16. A CPAN module, |
913 | L<Unicode::Casing>, providing improved functionality is being prepared for | |
914 | release by the time 5.14 is available. | |
823d0e46 | 915 | |
18139a1b | 916 | =head2 Deprecated modules |
5076a392 FC |
917 | |
918 | The following modules will be removed from the core distribution in a | |
919 | future release, and should be installed from CPAN instead. Distributions | |
920 | on CPAN which require these should add them to their prerequisites. The | |
823d0e46 | 921 | core versions of these modules will issue a deprecation warning. |
5076a392 FC |
922 | |
923 | If you ship a packaged version of Perl, either alone or as part of a | |
924 | larger system, then you should carefully consider the repercussions of | |
823d0e46 | 925 | core module deprecations. You may want to consider shipping your default |
5076a392 | 926 | build of Perl with packages for some or all deprecated modules which |
823d0e46 | 927 | install into C<vendor> or C<site> perl library directories. This will |
5076a392 FC |
928 | inhibit the deprecation warnings. |
929 | ||
930 | Alternatively, you may want to consider patching F<lib/deprecate.pm> | |
931 | to provide deprecation warnings specific to your packaging system | |
932 | or distribution of Perl, consistent with how your packaging system | |
933 | or distribution manages a staged transition from a release where the | |
934 | installation of a single package provides the given functionality, to | |
935 | a later release where the system administrator needs to know to install | |
936 | multiple packages to get that same functionality. | |
937 | ||
938 | You can silence these deprecation warnings by installing the modules | |
939 | in question from CPAN. To install the latest version of all of them, | |
940 | just install C<Task::Deprecations::5_14>. | |
941 | ||
942 | =over | |
943 | ||
944 | =item L<Devel::DProf> | |
945 | ||
946 | We strongly recommend that you install and used L<Devel::NYTProf> in | |
947 | preference, as it offers significantly improved profiling and reporting. | |
948 | ||
949 | =back | |
950 | ||
5076a392 FC |
951 | =head1 Performance Enhancements |
952 | ||
54c7bb16 | 953 | =head2 "Safe signals" optimisation |
df91d470 FC |
954 | |
955 | Signal dispatch has been moved from the runloop into control ops. This | |
956 | should give a few percent speed increase, and eliminates almost all of | |
957 | the speed penalty caused by the introduction of "safe signals" in | |
958 | 5.8.0. Signals should still be dispatched within the same statement as | |
959 | they were previously - if this is not the case, or it is possible to | |
960 | create uninterruptible loops, this is a bug, and reports are encouraged | |
961 | of how to recreate such issues. | |
962 | ||
54c7bb16 | 963 | =head2 Optimisation of shift; and pop; calls without arguments |
df91d470 | 964 | |
111b6aa7 FC |
965 | Two fewer OPs are used for shift and pop calls with no argument (with |
966 | implicit C<@_>). This change makes C<shift;> 5% faster than C<shift @_;> | |
967 | on non-threaded perls and 25% faster on threaded. | |
df91d470 | 968 | |
fa232254 | 969 | =head2 Optimisation of regexp engine string comparison work |
df91d470 | 970 | |
fa232254 FC |
971 | The foldEQ_utf8 API function for case-insensitive comparison of strings (which |
972 | is used heavily by the regexp engine) was substantially refactored and | |
973 | optimised - and its documentation much improved as a free bonus gift. | |
df91d470 | 974 | |
fa232254 | 975 | =head2 Regular expression compilation speed-up |
df91d470 | 976 | |
fa232254 FC |
977 | Compiling regular expressions has been made faster for the case where upgrading |
978 | the regex to utf8 is necessary but that isn't known when the compilation begins. | |
df91d470 | 979 | |
fa232254 | 980 | =head2 String appending is 100 times faster |
df91d470 | 981 | |
fa232254 FC |
982 | When doing a lot of string appending, perl could end up allocating a lot more |
983 | memory than needed in a very inefficient way, if perl was configured to use the | |
984 | system's C<malloc> implementation instead of its own. | |
985 | ||
986 | C<sv_grow>, which is what's being used to allocate more memory if necessary | |
987 | when appending to a string, has now been taught how to round up the memory | |
988 | it requests to a certain geometric progression, making it much faster on | |
989 | certain platforms and configurations. On Win32, it's now about 100 times | |
990 | faster. | |
991 | ||
992 | =head2 Eliminate C<PL_*> accessor functions under ithreads | |
993 | ||
994 | When C<MULTIPLICITY> was first developed, and interpreter state moved into | |
995 | an interpreter struct, thread and interpreter local C<PL_*> variables were | |
996 | defined as macros that called accessor functions, returning the address of | |
997 | the value, outside of the perl core. The intent was to allow members | |
998 | within the interpreter struct to change size without breaking binary | |
999 | compatibility, so that bug fixes could be merged to a maintenance branch | |
1000 | that necessitated such a size change. | |
1001 | ||
1002 | However, some non-core code defines C<PERL_CORE>, sometimes intentionally | |
1003 | to bypass this mechanism for speed reasons, sometimes for other reasons but | |
1004 | with the inadvertent side effect of bypassing this mechanism. As some of | |
1005 | this code is widespread in production use, the result is that the core | |
1006 | I<can't> change the size of members of the interpreter struct, as it will | |
1007 | break such modules compiled against a previous release on that maintenance | |
1008 | branch. The upshot is that this mechanism is redundant, and well-behaved | |
1009 | code is penalised by it. Hence it can and should be removed (and has | |
1010 | been). | |
1011 | ||
1012 | =head2 Freeing weak references | |
1013 | ||
1014 | When an object has many weak references to it, freeing that object | |
1015 | can under some some circumstances take O(N^2) time to free (where N is the | |
1016 | number of references). The number of circumstances has been reduced | |
1017 | [perl #75254] | |
1018 | ||
1019 | =head2 Lexical array and hash assignments | |
1020 | ||
1021 | An earlier optimisation to speed up C<my @array = ...> and | |
1022 | C<my %hash = ...> assignments caused a bug and was disabled in Perl 5.12.0. | |
1023 | ||
1024 | Now we have found another way to speed up these assignments [perl #82110]. | |
df91d470 | 1025 | |
111b6aa7 | 1026 | =head2 C<@_> uses less memory |
df91d470 | 1027 | |
111b6aa7 FC |
1028 | Previously, C<@_> was allocated for every subroutine at compile time with |
1029 | enough space for four entries. Now this allocation is done on demand when | |
1030 | the subroutine is called [perl #72416]. | |
5076a392 | 1031 | |
5076a392 FC |
1032 | =head2 Size optimisations to SV and HV structures |
1033 | ||
1034 | xhv_fill has been eliminated from struct xpvhv, saving 1 IV per hash and | |
111b6aa7 | 1035 | on some systems will cause struct xpvhv to become cache-aligned. To avoid |
5076a392 FC |
1036 | this memory saving causing a slowdown elsewhere, boolean use of HvFILL |
1037 | now calls HvTOTALKEYS instead (which is equivalent) - so while the fill | |
111b6aa7 FC |
1038 | data when actually required are now calculated on demand, the cases when |
1039 | this needs to be done should be few and far between. | |
5076a392 | 1040 | |
111b6aa7 FC |
1041 | The order of structure elements in SV bodies has changed. Effectively, |
1042 | the NV slot has swapped location with STASH and MAGIC. As all access to | |
1043 | SV members is via macros, this should be completely transparent. This | |
5076a392 FC |
1044 | change allows the space saving for PVHVs documented above, and may reduce |
1045 | the memory allocation needed for PVIVs on some architectures. | |
1046 | ||
fa232254 FC |
1047 | C<XPV>, C<XPVIV>, and C<XPVNV> now only allocate the parts of the C<SV> body |
1048 | they actually use, saving some space. | |
5076a392 | 1049 | |
fa232254 FC |
1050 | Scalars containing regular expressions now only allocate the part of the C<SV> |
1051 | body they actually use, saving some space. | |
5076a392 FC |
1052 | |
1053 | =head2 Memory consumption improvements to Exporter | |
1054 | ||
1055 | The @EXPORT_FAIL AV is no longer created unless required, hence neither is | |
111b6aa7 FC |
1056 | the typeglob backing it. This saves about 200 bytes for every package that |
1057 | uses Exporter but doesn't use this functionality. | |
5076a392 | 1058 | |
111b6aa7 | 1059 | =head2 Memory savings for weak references |
5076a392 FC |
1060 | |
1061 | For weak references, the common case of just a single weak reference per | |
1062 | referent has been optimised to reduce the storage required. In this case it | |
111b6aa7 | 1063 | saves the equivalent of one small Perl array per referent. |
5076a392 | 1064 | |
111b6aa7 | 1065 | =head2 C<%+> and C<%-> use less memory |
5076a392 FC |
1066 | |
1067 | The bulk of the C<Tie::Hash::NamedCapture> module used to be in the perl | |
111b6aa7 | 1068 | core. It has now been moved to an XS module, to reduce the overhead for |
5076a392 FC |
1069 | programs that do not use C<%+> or C<%->. |
1070 | ||
fa232254 | 1071 | =head2 Multiple small improvements to threads |
5076a392 | 1072 | |
fa232254 FC |
1073 | The internal structures of threading now make fewer API calls and fewer |
1074 | allocations, resulting in noticeably smaller object code. Additionally, | |
1075 | many thread context checks have been deferred so that they're only done | |
1076 | when required (although this is only possible for non-debugging builds). | |
5076a392 | 1077 | |
fa232254 | 1078 | =head2 Adjacent pairs of nextstate opcodes are now optimized away |
5076a392 | 1079 | |
fa232254 | 1080 | Previously, in code such as |
5076a392 | 1081 | |
fa232254 | 1082 | use constant DEBUG => 0; |
5076a392 | 1083 | |
fa232254 FC |
1084 | sub GAK { |
1085 | warn if DEBUG; | |
1086 | print "stuff\n"; | |
1087 | } | |
5076a392 | 1088 | |
fa232254 FC |
1089 | the ops for C<warn if DEBUG;> would be folded to a C<null> op (C<ex-const>), but |
1090 | the C<nextstate> op would remain, resulting in a runtime op dispatch of | |
1091 | C<nextstate>, C<nextstate>, .... | |
5076a392 | 1092 | |
fa232254 FC |
1093 | The execution of a sequence of C<nextstate> ops is indistinguishable from just |
1094 | the last C<nextstate> op so the peephole optimizer now eliminates the first of | |
1095 | a pair of C<nextstate> ops, except where the first carries a label, since labels | |
1096 | must not be eliminated by the optimizer and label usage isn't conclusively known | |
1097 | at compile time. | |
5076a392 FC |
1098 | |
1099 | =head1 Modules and Pragmata | |
1100 | ||
1101 | =head2 New Modules and Pragmata | |
1102 | ||
1103 | =over 4 | |
1104 | ||
1105 | =item * | |
1106 | ||
1107 | C<CPAN::Meta::YAML> 0.003 has been added as a dual-life module. It supports a | |
1108 | subset of YAML sufficient for reading and writing META.yml and MYMETA.yml files | |
1109 | included with CPAN distributions or generated by the module installation | |
1110 | toolchain. It should not be used for any other general YAML parsing or | |
1111 | generation task. | |
1112 | ||
1113 | =item * | |
1114 | ||
1115 | C<CPAN::Meta> version 2.110440 has been added as a dual-life module. It | |
1116 | provides a standard library to read, interpret and write CPAN distribution | |
1117 | metadata files (e.g. META.json and META.yml) which describes a | |
1118 | distribution, its contents, and the requirements for building it and | |
1119 | installing it. The latest CPAN distribution metadata specification is | |
1120 | included as C<CPAN::Meta::Spec> and notes on changes in the specification | |
1121 | over time are given in C<CPAN::Meta::History>. | |
1122 | ||
1123 | =item * | |
1124 | ||
5a553547 | 1125 | C<HTTP::Tiny> 0.011 has been added as a dual-life module. It is a very |
5076a392 FC |
1126 | small, simple HTTP/1.1 client designed for simple GET requests and file |
1127 | mirroring. It has has been added to enable CPAN.pm and CPANPLUS to | |
1128 | "bootstrap" HTTP access to CPAN using pure Perl without relying on external | |
1129 | binaries like F<curl> or F<wget>. | |
1130 | ||
1131 | =item * | |
1132 | ||
1133 | C<JSON::PP> 2.27105 has been added as a dual-life module, for the sake of | |
1134 | reading F<META.json> files in CPAN distributions. | |
1135 | ||
1136 | =item * | |
1137 | ||
1138 | C<Module::Metadata> 1.000003 has been added as a dual-life module. It gathers | |
1139 | package and POD information from Perl module files. It is a standalone module | |
1140 | based on Module::Build::ModuleInfo for use by other module installation | |
1141 | toolchain components. Module::Build::ModuleInfo has been deprecated in | |
1142 | favor of this module instead. | |
1143 | ||
1144 | =item * | |
1145 | ||
1146 | C<Perl::OSType> 1.002 has been added as a dual-life module. It maps Perl | |
1147 | operating system names (e.g. 'dragonfly' or 'MSWin32') to more generic types | |
1148 | with standardized names (e.g. "Unix" or "Windows"). It has been refactored | |
1149 | out of Module::Build and ExtUtils::CBuilder and consolidates such mappings into | |
1150 | a single location for easier maintenance. | |
1151 | ||
1152 | =item * | |
1153 | ||
1154 | The following modules were added by the C<Unicode::Collate> | |
1155 | upgrade. See below for details. | |
1156 | ||
1157 | C<Unicode::Collate::CJK::Big5> | |
1158 | ||
1159 | C<Unicode::Collate::CJK::GB2312> | |
1160 | ||
1161 | C<Unicode::Collate::CJK::JISX0208> | |
1162 | ||
1163 | C<Unicode::Collate::CJK::Korean> | |
1164 | ||
1165 | C<Unicode::Collate::CJK::Pinyin> | |
1166 | ||
1167 | C<Unicode::Collate::CJK::Stroke> | |
1168 | ||
1169 | =item * | |
1170 | ||
1171 | C<Version::Requirements> version 0.101020 has been added as a dual-life | |
1172 | module. It provides a standard library to model and manipulates module | |
1173 | prerequisites and version constraints as defined in the L<CPAN::Meta::Spec>. | |
1174 | ||
1175 | =back | |
1176 | ||
d622514a | 1177 | =head2 Selected Module and Pragma Updates |
5076a392 FC |
1178 | |
1179 | =over 4 | |
1180 | ||
1181 | =item * | |
1182 | ||
5076a392 FC |
1183 | C<Archive::Extract> has been upgraded from version 0.38 to 0.48. |
1184 | ||
1185 | Updates since 0.38 include: a safe print method that guards | |
1186 | Archive::Extract from changes to $\; a fix to the tests when run in core | |
1984204c FC |
1187 | perl; support for TZ files; a modification for the lzma |
1188 | logic to favour IO::Uncompress::Unlzma; and a fix | |
1189 | for an issue with NetBSD-current and its new unzip | |
5076a392 FC |
1190 | executable. |
1191 | ||
1192 | =item * | |
1193 | ||
1194 | C<Archive::Tar> has been upgraded from version 1.54 to 1.76. | |
1195 | ||
1984204c FC |
1196 | Important changes since 1.54 include the following: |
1197 | ||
1198 | =over | |
1199 | ||
1200 | =item * | |
1201 | ||
1202 | Compatibility with busybox implementations of tar | |
1203 | ||
1204 | =item * | |
1205 | ||
1206 | A fix so that C<write()> and C<create_archive()> | |
1207 | close only handles they opened | |
1208 | ||
1209 | =item * | |
1210 | ||
1211 | A bug was fixed regarding the exit code of extract_archive. | |
5076a392 | 1212 | |
1984204c FC |
1213 | =item * |
1214 | ||
1215 | C<ptar> has a new option to allow safe | |
5076a392 FC |
1216 | creation of tarballs without world-writable files on Windows, allowing those |
1217 | archives to be uploaded to CPAN. | |
1218 | ||
1984204c FC |
1219 | =item * |
1220 | ||
1221 | A new ptargrep utility for using regular expressions against | |
5076a392 FC |
1222 | the contents of files in a tar archive. |
1223 | ||
1984204c FC |
1224 | =item * |
1225 | ||
1226 | Pax extended headers are now skipped. | |
1227 | ||
1228 | =back | |
5076a392 FC |
1229 | |
1230 | =item * | |
1231 | ||
5076a392 FC |
1232 | C<B> has been upgraded from version 1.23 to 1.27. |
1233 | ||
1234 | It no longer crashes when taking apart a C<y///> containing characters | |
1235 | outside the octet range or compiled in a C<use utf8> scope. | |
1236 | ||
1237 | The size of the shared object has been reduced by about 40%, with no | |
1238 | reduction in functionality. | |
1239 | ||
1240 | =item * | |
1241 | ||
1242 | C<B::Concise> has been upgraded from version 0.78 to 0.82. | |
1243 | ||
1244 | B::Concise marks rv2sv, rv2av and rv2hv ops with the new OPpDEREF flag | |
1245 | as "DREFed". | |
1246 | ||
1247 | It no longer produces mangled output with the C<-tree> option | |
1248 | [perl #80632]. | |
1249 | ||
1250 | =item * | |
1251 | ||
5076a392 FC |
1252 | C<B::Deparse> has been upgraded from version 0.96 to 1.02. |
1253 | ||
1984204c | 1254 | The deparsing of a nextstate op has changed when it has both a |
5076a392 FC |
1255 | change of package (relative to the previous nextstate), or a change of |
1256 | C<%^H> or other state, and a label. Previously the label was emitted | |
cdc10f43 | 1257 | first, but now the label is emitted last (5.12.1). |
5076a392 | 1258 | |
5a553547 FC |
1259 | The C<no 5.13.2> or similar form is now correctly handled by B::Deparse |
1260 | (5.12.3). | |
5076a392 FC |
1261 | |
1262 | B::Deparse now properly handles the code that applies a conditional | |
1263 | pattern match against implicit C<$_> as it was fixed in [perl #20444]. | |
1264 | ||
1984204c FC |
1265 | Deparsing of C<our> followed by a variable with funny characters |
1266 | (as permitted under the C<utf8> pragma) has also been fixed [perl #33752]. | |
5076a392 FC |
1267 | |
1268 | =item * | |
1269 | ||
d430b8e7 | 1270 | C<Carp> has been upgraded from version 1.15 to 1.19. |
5076a392 FC |
1271 | |
1272 | L<Carp> now detects incomplete L<caller()|perlfunc/"caller EXPR"> overrides and | |
d430b8e7 FC |
1273 | avoids using bogus C<@DB::args>. To provide backtraces, |
1274 | Carp relies on particular behaviour of the C<caller> | |
1275 | built-in. Carp now detects if other code has | |
5076a392 | 1276 | overridden this with an incomplete implementation, and modifies its backtrace |
d430b8e7 FC |
1277 | accordingly. Previously incomplete overrides would cause incorrect values |
1278 | in backtraces (best case), or obscure fatal errors (worst case). | |
5076a392 FC |
1279 | |
1280 | This fixes certain cases of C<Bizarre copy of ARRAY> caused by modules | |
d430b8e7 | 1281 | overriding C<caller()> incorrectly (5.12.2). |
5076a392 | 1282 | |
1984204c | 1283 | It now also avoids using regular expressions that cause perl to |
5076a392 FC |
1284 | load its Unicode tables, in order to avoid the 'BEGIN not safe after |
1285 | errors' error that will ensue if there has been a syntax error | |
1286 | [perl #82854]. | |
1287 | ||
1288 | =item * | |
1289 | ||
1290 | C<CGI> has been upgraded from version 3.48 to 3.51. | |
1291 | ||
1292 | This provides the following security fixes: the MIME boundary in | |
1984204c FC |
1293 | multipart_init is now random and the handling of |
1294 | newlines embedded in header values has been improved. | |
5076a392 FC |
1295 | |
1296 | =item * | |
1297 | ||
5076a392 FC |
1298 | C<Compress::Raw::Bzip2> has been upgraded from version 2.024 to 2.033. |
1299 | ||
1984204c | 1300 | It has been updated to use bzip2 1.0.6. |
5076a392 FC |
1301 | |
1302 | =item * | |
1303 | ||
1984204c FC |
1304 | C<CPAN> has been upgraded from version 1.94_56 to 1.9600.- |
1305 | ||
1306 | Major highlights: | |
5076a392 FC |
1307 | |
1308 | =over 4 | |
1309 | ||
1984204c | 1310 | =item * much less configuration dialog hassle |
5076a392 | 1311 | |
1984204c | 1312 | =item * support for META/MYMETA.json |
5076a392 | 1313 | |
1984204c | 1314 | =item * support for local::lib |
5076a392 | 1315 | |
1984204c | 1316 | =item * support for HTTP::Tiny to reduce the dependency on ftp sites |
5076a392 | 1317 | |
1984204c | 1318 | =item * automatic mirror selection |
5076a392 | 1319 | |
1984204c | 1320 | =item * iron out all known bugs in configure_requires |
5076a392 | 1321 | |
1984204c FC |
1322 | =item * support for distributions compressed with bzip2 |
1323 | ||
1324 | =item * allow Foo/Bar.pm on the commandline to mean Foo::Bar | |
1325 | ||
1326 | =back | |
5076a392 FC |
1327 | |
1328 | =item * | |
1329 | ||
d430b8e7 FC |
1330 | C<CPANPLUS> has been upgraded from version 0.90 to 0.9103. |
1331 | ||
1332 | A change to F<cpanp-run-perl> | |
1333 | resolves L<RT #55964|http://rt.cpan.org/Public/Bug/Display.html?id=55964> | |
1334 | and L<RT #57106|http://rt.cpan.org/Public/Bug/Display.html?id=57106>, both | |
1335 | of which related to failures to install distributions that use | |
1336 | C<Module::Install::DSL> (5.12.2). | |
5076a392 | 1337 | |
1984204c FC |
1338 | A dependency on Config was not recognised as a |
1339 | core module dependency. This has been fixed. | |
5076a392 | 1340 | |
1984204c | 1341 | CPANPLUS now includes support for META.json and MYMETA.json. |
5076a392 FC |
1342 | |
1343 | =item * | |
1344 | ||
5076a392 FC |
1345 | C<Data::Dumper> has been upgraded from version 2.125 to 2.130_02. |
1346 | ||
4ed2cea4 FC |
1347 | The indentation used to be off when C<$Data::Dumper::Terse> was set. This |
1348 | has been fixed [perl #73604]. | |
1349 | ||
1984204c FC |
1350 | This upgrade also fixes a crash when using custom sort functions that might |
1351 | cause the stack to change [perl #74170]. | |
5076a392 FC |
1352 | |
1353 | C<Dumpxs> no longer crashes with globs returned by C<*$io_ref> | |
1354 | [perl #72332]. | |
1355 | ||
1356 | =item * | |
1357 | ||
5076a392 FC |
1358 | C<Devel::DProf> has been upgraded from version 20080331.00 to 20110228.00. |
1359 | ||
1360 | Merely loading C<Devel::DProf> now no longer triggers profiling to start. | |
1361 | C<use Devel::DProf> and C<perl -d:DProf ...> still behave as before and start | |
1362 | the profiler. | |
1363 | ||
1364 | NOTE: C<Devel::DProf> is deprecated and will be removed from a future | |
1984204c | 1365 | version of Perl. We strongly recommend that you install and use |
5076a392 FC |
1366 | L<Devel::NYTProf> instead, as it offers significantly improved |
1367 | profiling and reporting. | |
1368 | ||
1369 | =item * | |
1370 | ||
5076a392 FC |
1371 | C<diagnostics> has been upgraded from version 1.19 to 1.22. |
1372 | ||
1373 | It now renders pod links slightly better, and has been taught to find | |
1374 | descriptions for messages that share their descriptions with other | |
1375 | messages. | |
1376 | ||
1377 | =item * | |
1378 | ||
1379 | C<Digest::MD5> has been upgraded from version 2.39 to 2.51. | |
1380 | ||
1381 | It is now safe to use this module in combination with threads. | |
1382 | ||
1383 | =item * | |
1384 | ||
1385 | C<Digest::SHA> has been upgraded from version 5.47 to 5.61. | |
1386 | ||
1387 | C<shasum> now more closely mimics C<sha1sum>/C<md5sum>. | |
1388 | ||
1389 | C<Addfile> accepts all POSIX filenames. | |
1390 | ||
1984204c FC |
1391 | New SHA-512/224 and SHA-512/256 transforms (ref. NIST Draft FIPS 180-4 |
1392 | [February 2011]) | |
5076a392 FC |
1393 | |
1394 | =item * | |
1395 | ||
5076a392 FC |
1396 | C<DynaLoader> has been upgraded from version 1.10 to 1.12. |
1397 | ||
1398 | It fixes a buffer overflow when passed a very long file name. | |
1399 | ||
1400 | It no longer inherits from AutoLoader; hence it no longer | |
1401 | produces weird error messages for unsuccessful method calls on classes that | |
1402 | inherit from DynaLoader [perl #84358]. | |
1403 | ||
1404 | =item * | |
1405 | ||
1406 | C<Encode> has been upgraded from version 2.39 to 2.42. | |
1407 | ||
1408 | Now, all 66 Unicode non-characters are treated the same way U+FFFF has | |
1984204c FC |
1409 | always been treated; in cases when it was disallowed, all 66 are |
1410 | disallowed; in those cases where it warned, all 66 warn. | |
5076a392 FC |
1411 | |
1412 | =item * | |
1413 | ||
5076a392 FC |
1414 | C<Errno> has been upgraded from version 1.11 to 1.13. |
1415 | ||
1416 | The implementation of C<Errno> has been refactored to use about 55% less memory. | |
5076a392 FC |
1417 | |
1418 | On some platforms with unusual header files, like Win32/gcc using mingw64 | |
1419 | headers, some constants which weren't actually error numbers have been exposed | |
1420 | by C<Errno>. This has been fixed [perl #77416]. | |
1421 | ||
1422 | =item * | |
1423 | ||
1424 | C<Exporter> has been upgraded from version 5.64_01 to 5.64_03. | |
1425 | ||
1426 | Exporter no longer overrides C<$SIG{__WARN__}> [perl #74472] | |
1427 | ||
1428 | =item * | |
1429 | ||
5076a392 FC |
1430 | C<ExtUtils::Constant> has been upgraded from 0.22 to 0.23. |
1431 | ||
1432 | The C<AUTOLOAD> helper code generated by C<ExtUtils::Constant::ProxySubs> | |
1433 | can now C<croak> for missing constants, or generate a complete C<AUTOLOAD> | |
1984204c FC |
1434 | subroutine in XS, allowing simplification of many modules that use it |
1435 | (C<Fcntl>, C<File::Glob>, C<GDBM_File>, C<I18N::Langinfo>, C<POSIX>, | |
1436 | C<Socket>). | |
5076a392 FC |
1437 | |
1438 | C<ExtUtils::Constant::ProxySubs> can now optionally push the names of all | |
1984204c | 1439 | constants onto the package's C<@EXPORT_OK>. |
5076a392 FC |
1440 | |
1441 | =item * | |
1442 | ||
5076a392 FC |
1443 | C<File::DosGlob> has been upgraded from version 1.01 to 1.03. |
1444 | ||
1445 | It allows patterns containing literal parentheses (they no longer need to | |
1984204c FC |
1446 | be escaped). On Windows, it no longer |
1447 | adds an extra F<./> to the file names | |
5076a392 FC |
1448 | returned when the pattern is a relative glob with a drive specification, |
1449 | like F<c:*.pl> [perl #71712]. | |
1450 | ||
1451 | =item * | |
1452 | ||
1453 | C<File::Fetch> has been upgraded from version 0.24 to 0.32. | |
1454 | ||
1455 | C<HTTP::Lite> is now supported for 'http' scheme. | |
1456 | ||
1457 | The C<fetch> utility is supported on FreeBSD, NetBSD and | |
1458 | Dragonfly BSD for the C<http> and C<ftp> schemes. | |
1459 | ||
1460 | =item * | |
1461 | ||
1462 | C<File::Find> has been upgraded from version 1.15 to 1.18. | |
1463 | ||
1984204c | 1464 | It improves handling of backslashes on Windows, so that paths like |
5076a392 FC |
1465 | F<c:\dir\/file> are no longer generated [perl #71710]. |
1466 | ||
1467 | =item * | |
1468 | ||
d430b8e7 FC |
1469 | C<File::Spec> has been upgraded from version 3.31 to 3.33. |
1470 | ||
1471 | Several portability fixes were made in C<File::Spec::VMS>: a colon is now | |
1472 | recognized as a delimiter in native filespecs; caret-escaped delimiters are | |
1473 | recognized for better handling of extended filespecs; C<catpath()> returns | |
1474 | an empty directory rather than the current directory if the input directory | |
1475 | name is empty; C<abs2rel()> properly handles Unix-style input (5.12.2). | |
1476 | ||
1477 | =item * | |
1478 | ||
5076a392 FC |
1479 | C<File::stat> has been upgraded from 1.02 to 1.04. |
1480 | ||
1481 | The C<-x> and C<-X> file test operators now work correctly under the root | |
1482 | user. | |
1483 | ||
1484 | =item * | |
1485 | ||
5076a392 FC |
1486 | C<GDBM_File> has been upgraded from 1.10 to 1.13. |
1487 | ||
1488 | This fixes a memory leak when DBM filters are used. | |
1489 | ||
1490 | =item * | |
1491 | ||
1492 | C<Hash::Util> has been upgraded from 0.07 to 0.10. | |
1493 | ||
1984204c FC |
1494 | Hash::Util no longer emits spurious "uninitialized" warnings when |
1495 | recursively locking hashes that have undefined values [perl #74280]. | |
5076a392 FC |
1496 | |
1497 | =item * | |
1498 | ||
1499 | C<I18N::Langinfo> has been upgraded from version 0.03 to 0.07. | |
1500 | ||
1501 | C<langinfo()> now defaults to using C<$_> if there is no argument given, just | |
5334145a | 1502 | as the documentation has always claimed. |
5076a392 FC |
1503 | |
1504 | =item * | |
1505 | ||
1506 | C<IO::Select> has been upgraded from version 1.17 to 1.18. | |
1507 | ||
1508 | It now allows IO::Handle objects (and objects in derived classes) to be | |
1509 | removed from an IO::Select set even if the underlying file descriptor is | |
1510 | closed or invalid. | |
1511 | ||
1512 | =item * | |
1513 | ||
5076a392 FC |
1514 | C<IPC::Cmd> has been upgraded from version 0.54 to 0.68. |
1515 | ||
1984204c FC |
1516 | Resolves an issue with splitting Win32 command lines. An argument |
1517 | consisting of the single character "0" used to be omitted (CPAN RT #62961). | |
5076a392 FC |
1518 | |
1519 | =item * | |
1520 | ||
1521 | C<IPC::Open3> has been upgraded from 1.05 to 1.08. | |
1522 | ||
4ed2cea4 FC |
1523 | C<open3> now produces an error if the C<exec> call fails, allowing this |
1524 | condition to be distinguished from a child process that exited with a | |
1525 | non-zero status [perl #72016]. | |
1526 | ||
5076a392 FC |
1527 | The internal C<xclose> routine now knows how to handle file descriptors, as |
1528 | documented, so duplicating STDIN in a child process using its file | |
1529 | descriptor now works [perl #76474]. | |
1530 | ||
1531 | =item * | |
1532 | ||
5076a392 FC |
1533 | C<Locale::Maketext> has been upgraded from version 1.14 to 1.17. |
1534 | ||
1984204c | 1535 | Locale::Maketext now supports external caches. |
5076a392 | 1536 | |
1984204c FC |
1537 | This upgrade also fixes an infinite loop in |
1538 | C<Locale::Maketext::Guts::_compile()> when | |
5076a392 FC |
1539 | working with tainted values (CPAN RT #40727). |
1540 | ||
1984204c | 1541 | C<< ->maketext >> calls will now back up and restore C<$@> so that error |
5076a392 FC |
1542 | messages are not suppressed (CPAN RT #34182). |
1543 | ||
1544 | =item * | |
1545 | ||
5076a392 FC |
1546 | C<Math::BigInt> has been upgraded from version 1.89_01 to 1.994. |
1547 | ||
1548 | This fixes, among other things, incorrect results when computing binomial | |
1549 | coefficients [perl #77640]. | |
1550 | ||
1984204c | 1551 | It also prevents C<sqrt($int)> from crashing under C<use bigrat;> |
5076a392 FC |
1552 | [perl #73534]. |
1553 | ||
1554 | =item * | |
1555 | ||
5076a392 FC |
1556 | C<MIME::Base64> has been upgraded from 3.08 to 3.13. |
1557 | ||
1558 | Includes new functions to calculate the length of encoded and decoded | |
1559 | base64 strings. | |
1560 | ||
1561 | Now provides C<encode_base64url> and C<decode_base64url> functions to process | |
1562 | the base64 scheme for "URL applications". | |
1563 | ||
1564 | =item * | |
1565 | ||
1566 | C<Module::Build> has been upgraded from version 0.3603 to 0.3800. | |
1567 | ||
1568 | A notable change is the deprecation of several modules. | |
1569 | Module::Build::Version has been deprecated and Module::Build now relies | |
1570 | directly upon L<version>. Module::Build::ModuleInfo has been deprecated in | |
1571 | favor of a standalone copy of it called L<Module::Metadata>. | |
1572 | Module::Build::YAML has been deprecated in favor of L<CPAN::Meta::YAML>. | |
1573 | ||
1574 | Module::Build now also generates META.json and MYMETA.json files | |
1575 | in accordance with version 2 of the CPAN distribution metadata specification, | |
1576 | L<CPAN::Meta::Spec>. The older format META.yml and MYMETA.yml files are | |
1577 | still generated, as well. | |
1578 | ||
1579 | =item * | |
1580 | ||
1581 | C<Module::CoreList> has been upgraded from version 2.29 to XXX. | |
1582 | ||
1583 | Besides listing the updated core modules of this release, it also stops listing | |
1984204c | 1584 | the C<Filespec> module. That module never existed in core. The scripts |
5076a392 | 1585 | generating C<Module::CoreList> confused it with C<VMS::Filespec>, which actually |
1984204c | 1586 | is a core module as of perl 5.8.7. |
5076a392 FC |
1587 | |
1588 | =item * | |
1589 | ||
1984204c FC |
1590 | C<NDBM_File> and C<ODBM_File> have been upgraded from 1.08 to 1.11, and |
1591 | from 1.08 to 1.09, respectively. | |
5076a392 FC |
1592 | |
1593 | This fixes a memory leak when DBM filters are used. | |
1594 | ||
1595 | =item * | |
1596 | ||
5076a392 FC |
1597 | C<overload> has been upgraded from 1.11 to 1.12. |
1598 | ||
1599 | C<overload::Method> can now handle subroutines that are themselves blessed | |
1600 | into overloaded classes [perl #71998]. | |
1601 | ||
5076a392 FC |
1602 | The documentation has greatly improved. See L</Documentation> below. |
1603 | ||
1604 | =item * | |
1605 | ||
5076a392 FC |
1606 | C<Parse::CPAN::Meta> has been upgraded from version 1.40 to 1.4401. |
1607 | ||
1984204c | 1608 | The latest Parse::CPAN::Meta can now read YAML and JSON files using |
5076a392 FC |
1609 | L<CPAN::Meta::YAML> and L<JSON::PP>, which are now part of the Perl core. |
1610 | ||
1611 | =item * | |
1612 | ||
5076a392 FC |
1613 | C<PerlIO::scalar> has been upgraded from 0.07 to 0.11. |
1614 | ||
1615 | A C<read> after a C<seek> beyond the end of the string no longer thinks it | |
1616 | has data to read [perl #78716]. | |
1617 | ||
1618 | =item * | |
1619 | ||
5076a392 FC |
1620 | C<POSIX> has been upgraded from 1.19 to 1.23. |
1621 | ||
1622 | It now includes constants for POSIX signal constants. | |
1623 | ||
1624 | =item * | |
1625 | ||
1984204c | 1626 | C<re> has been upgraded from version 0.11 to 0.17. |
5076a392 FC |
1627 | |
1628 | New C<use re "/flags"> pragma | |
1629 | ||
5076a392 | 1630 | The C<regmust> function used to crash when called on a regular expression |
1984204c | 1631 | belonging to a pluggable engine. Now it croaks instead. |
5076a392 FC |
1632 | |
1633 | C<regmust> no longer leaks memory. | |
1634 | ||
1635 | =item * | |
1636 | ||
1637 | C<Safe> has been upgraded from version 2.25 to 2.29. | |
1638 | ||
cdc10f43 FC |
1639 | Coderefs returned by C<reval()> and C<rdo()> are now wrapped via |
1640 | C<wrap_code_refs> (5.12.1). | |
1641 | ||
5076a392 FC |
1642 | This fixes a possible infinite loop when looking for coderefs. |
1643 | ||
cdc10f43 | 1644 | It adds several version::vxs::* routines to the default share. |
5076a392 FC |
1645 | |
1646 | =item * | |
1647 | ||
5076a392 FC |
1648 | C<SelfLoader> has been upgraded from 1.17 to 1.18. |
1649 | ||
1650 | It now works in taint mode [perl #72062]. | |
1651 | ||
1652 | =item * | |
1653 | ||
1654 | C<sigtrap> has been upgraded from version 1.04 to 1.05. | |
1655 | ||
1656 | It no longer tries to modify read-only arguments when generating a | |
1657 | backtrace [perl #72340]. | |
1658 | ||
1659 | =item * | |
1660 | ||
1984204c | 1661 | C<Socket> has been upgraded from version 1.87 to 1.94. |
5076a392 | 1662 | |
1984204c | 1663 | See L</IPv6 support>, above. |
5076a392 FC |
1664 | |
1665 | =item * | |
1666 | ||
1667 | C<Storable> has been upgraded from version 2.22 to 2.27. | |
1668 | ||
1669 | Includes performance improvement for overloaded classes. | |
1670 | ||
5076a392 | 1671 | This adds support for serialising code references that contain UTF-8 strings |
1984204c FC |
1672 | correctly. The Storable minor version |
1673 | number changed as a result, meaning that | |
5076a392 FC |
1674 | Storable users who set C<$Storable::accept_future_minor> to a C<FALSE> value |
1675 | will see errors (see L<Storable/FORWARD COMPATIBILITY> for more details). | |
1676 | ||
1677 | Freezing no longer gets confused if the Perl stack gets reallocated | |
1678 | during freezing [perl #80074]. | |
1679 | ||
1680 | =item * | |
1681 | ||
5076a392 FC |
1682 | C<Test::Simple> has been upgraded from version 0.94 to 0.98. |
1683 | ||
1684 | Among many other things, subtests without a C<plan> or C<no_plan> now have an | |
1685 | implicit C<done_testing()> added to them. | |
1686 | ||
1687 | =item * | |
1688 | ||
5076a392 FC |
1689 | C<Thread::Semaphore> has been upgraded from version 2.09 to 2.12. |
1690 | ||
1984204c FC |
1691 | It provides two new methods that give more control over the decrementing of |
1692 | semaphores: C<down_nb> and C<down_force>. | |
5076a392 FC |
1693 | |
1694 | =item * | |
1695 | ||
5076a392 FC |
1696 | C<Tie::Hash> has been upgraded from version 1.03 to 1.04. |
1697 | ||
1698 | Calling C<< Tie::Hash-E<gt>TIEHASH() >> used to loop forever. Now it C<croak>s. | |
1699 | ||
1700 | =item * | |
1701 | ||
5076a392 FC |
1702 | C<Unicode::Collate> has been upgraded from version 0.52_01 to 0.73. |
1703 | ||
1984204c | 1704 | Unicode::Collate has been updated to use Unicode 6.0.0. |
5076a392 | 1705 | |
1984204c FC |
1706 | Unicode::Collate::Locale now supports a plethora of new locales: ar, be, |
1707 | bg, de__phonebook, hu, hy, kk, mk, nso, om, tn, vi, hr, ig, ja, ko, ru, sq, | |
1708 | se, sr, to, uk, zh, zh__big5han, zh__gb2312han, zh__pinyin and zh__stroke. | |
5076a392 FC |
1709 | |
1710 | The following modules have been added: | |
1711 | ||
1712 | C<Unicode::Collate::CJK::Big5> for C<zh__big5han> which makes | |
1713 | tailoring of CJK Unified Ideographs in the order of CLDR's big5han ordering. | |
1714 | ||
1715 | C<Unicode::Collate::CJK::GB2312> for C<zh__gb2312han> which makes | |
1716 | tailoring of CJK Unified Ideographs in the order of CLDR's gb2312han ordering. | |
1717 | ||
1718 | C<Unicode::Collate::CJK::JISX0208> which makes tailoring of 6355 kanji | |
1719 | (CJK Unified Ideographs) in the JIS X 0208 order. | |
1720 | ||
1721 | C<Unicode::Collate::CJK::Korean> which makes tailoring of CJK Unified Ideographs | |
1722 | in the order of CLDR's Korean ordering. | |
1723 | ||
1724 | C<Unicode::Collate::CJK::Pinyin> for C<zh__pinyin> which makes | |
1725 | tailoring of CJK Unified Ideographs in the order of CLDR's pinyin ordering. | |
1726 | ||
1727 | C<Unicode::Collate::CJK::Stroke> for C<zh__stroke> which makes | |
1728 | tailoring of CJK Unified Ideographs in the order of CLDR's stroke ordering. | |
1729 | ||
5076a392 FC |
1730 | This also sees the switch from using the pure-perl version of this |
1731 | module to the XS version. | |
1732 | ||
1733 | =item * | |
1734 | ||
5076a392 FC |
1735 | C<Unicode::UCD> has been upgraded from version 0.27 to 0.32. |
1736 | ||
1984204c FC |
1737 | A new function, C<Unicode::UCD::num()>, has been added. This function |
1738 | returns the numeric value of the string passed it or C<undef> if the string | |
1739 | in its entirety has no "safe" numeric value. (For more detail, and for the | |
1740 | definition of "safe", see L<Unicode::UCD/num>.) | |
5076a392 | 1741 | |
1984204c | 1742 | This upgrade also includes a number of bug fixes: |
5076a392 FC |
1743 | |
1744 | =over 4 | |
1745 | ||
1746 | =item charinfo() | |
1747 | ||
1748 | =over 4 | |
1749 | ||
1750 | =item * | |
1751 | ||
1752 | It is now updated to Unicode Version 6 with Corrigendum #8, except, | |
1753 | as with Perl 5.14, the code point at U+1F514 has no name. | |
1754 | ||
1755 | =item * | |
1756 | ||
1757 | The Hangul syllable code points have the correct names, and their | |
1758 | decompositions are always output without requiring L<Lingua::KO::Hangul::Util> | |
1759 | to be installed. | |
1760 | ||
1761 | =item * | |
1762 | ||
54c7bb16 FC |
1763 | The CJK (Chinese-Japanese-Korean) code points U+2A700 to U+2B734 |
1764 | and U+2B740 to U+2B81D are now properly handled. | |
5076a392 FC |
1765 | |
1766 | =item * | |
1767 | ||
1768 | The numeric values are now output for those CJK code points that have them. | |
1769 | ||
1770 | =item * | |
1771 | ||
1772 | The names that are output for code points with multiple aliases are now the | |
1773 | corrected ones. | |
1774 | ||
1775 | =back | |
1776 | ||
1777 | =item charscript() | |
1778 | ||
1779 | This now correctly returns "Unknown" instead of C<undef> for the script | |
1780 | of a code point that hasn't been assigned another one. | |
1781 | ||
1782 | =item charblock() | |
1783 | ||
1784 | This now correctly returns "No_Block" instead of C<undef> for the block | |
1785 | of a code point that hasn't been assigned to another one. | |
1786 | ||
1787 | =back | |
1788 | ||
5076a392 FC |
1789 | =item * |
1790 | ||
1791 | C<version> has been upgraded from 0.82 to 0.88. | |
1792 | ||
1984204c | 1793 | Due to a bug, now fixed, the C<is_strict> and C<is_lax> functions did not |
cdc10f43 | 1794 | work when exported (5.12.1). |
5076a392 FC |
1795 | |
1796 | =item * | |
1797 | ||
1798 | C<warnings> and C<warnings::register> have been upgraded from version 1.09 | |
1799 | to 1.11 and from version 1.01 to 1.02 respectively. | |
1800 | ||
1801 | Calling C<use warnings> without arguments is now significantly more efficient. | |
1802 | ||
1803 | It is now possible to register warning categories other than the names of | |
1804 | packages using C<warnings::register>. See L<perllexwarn> for more information. | |
1805 | ||
1806 | =item * | |
1807 | ||
1808 | C<VMS::DCLsym> has been upgraded from version 1.03 to 1.05. | |
1809 | ||
1810 | Two bugs have been fixed [perl #84086]: | |
1811 | ||
1812 | The symbol table name was lost when tying a hash, due to a thinko in | |
1813 | C<TIEHASH>. The result was that all tied hashes interacted with the | |
1814 | local symbol table. | |
1815 | ||
1816 | Unless a symbol table name had been explicitly specified in the call | |
1817 | to the constructor, querying the special key ':LOCAL' failed to | |
1818 | identify objects connected to the local symbol table. | |
1819 | ||
1820 | =item * | |
1821 | ||
1822 | C<Win32> has been upgraded from version 0.39 to 0.44. | |
1823 | ||
1984204c FC |
1824 | This release has several new functions: C<Win32::GetSystemMetrics>, |
1825 | C<Win32::GetProductInfo>, C<Win32::GetOSDisplayName>. | |
5076a392 | 1826 | |
1984204c FC |
1827 | The names returned by C<Win32::GetOSName> and C<Win32::GetOSDisplayName> |
1828 | have been corrected. | |
5076a392 | 1829 | |
5076a392 FC |
1830 | =back |
1831 | ||
5076a392 FC |
1832 | =head2 Removed Modules and Pragmata |
1833 | ||
1834 | The following modules have been removed from the core distribution, and if | |
1835 | needed should be installed from CPAN instead. | |
1836 | ||
1837 | =over | |
1838 | ||
1839 | =item C<Class::ISA> | |
1840 | ||
1841 | =item C<Pod::Plainer> | |
1842 | ||
1843 | =item C<Switch> | |
1844 | ||
1845 | =back | |
1846 | ||
1847 | The removal of C<Shell> has been deferred until after 5.14, as the | |
1848 | implementation of C<Shell> shipped with 5.12.0 did not correctly issue the | |
1849 | warning that it was to be removed from core. | |
1850 | ||
1851 | =head1 Documentation | |
1852 | ||
5076a392 FC |
1853 | =head2 New Documentation |
1854 | ||
41e29def | 1855 | =head3 L<perlgpl> |
5076a392 FC |
1856 | |
1857 | L<perlgpl> has been updated to contain GPL version 1, as is included in the | |
cdc10f43 | 1858 | F<README> distributed with perl (5.12.1). |
5076a392 | 1859 | |
41e29def | 1860 | =head3 Perl 5.12.x delta files |
5076a392 | 1861 | |
41e29def FC |
1862 | The perldelta files for Perl 5.12.1 to 5.12.3 have been added from the |
1863 | maintenance branch: L<perl5121delta>, L<perl5122delta>, L<perl5123delta>. | |
5076a392 FC |
1864 | |
1865 | =head3 L<perlpodstyle> | |
1866 | ||
1867 | New style guide for POD documentation, | |
1868 | split mostly from the NOTES section of the pod2man man page. | |
1869 | ||
41e29def FC |
1870 | =head3 L<perlsource>, L<perlinterp>, L<perlhacktut>, and L<perlhacktips> |
1871 | ||
1872 | See L</L<perlhack> and perlrepository revamp>, below. | |
5076a392 FC |
1873 | |
1874 | =head2 Changes to Existing Documentation | |
1875 | ||
41e29def | 1876 | =head3 L<perlmodlib> is now complete |
4ed2cea4 FC |
1877 | |
1878 | The perlmodlib page that came with Perl 5.12.0 was missing a lot of | |
1879 | modules, due to a bug in the script that generates the list. This has been | |
cdc10f43 | 1880 | fixed [perl #74332] (5.12.1). |
4ed2cea4 | 1881 | |
41e29def | 1882 | =head3 Replace wrong tr/// table in L<perlebcdic> |
5076a392 | 1883 | |
41e29def | 1884 | L<perlebcdic> contains a helpful table to use in tr/// to convert |
5076a392 FC |
1885 | between EBCDIC and Latin1/ASCII. Unfortunately, the table was the |
1886 | inverse of the one it describes, though the code that used the table | |
1887 | worked correctly for the specific example given. | |
1888 | ||
1889 | The table has been changed to its inverse, and the sample code changed | |
1890 | to correspond, as this is easier for the person trying to follow the | |
1891 | instructions since deriving the old table is somewhat more complicated. | |
1892 | ||
1893 | The table has also been changed to hex from octal, as that is more the norm | |
1894 | these days, and the recipes in the pod altered to print out leading | |
41e29def | 1895 | zeros to make all the values the same length. |
5076a392 | 1896 | |
41e29def | 1897 | =head3 Tricks for user-defined casing |
5076a392 | 1898 | |
41e29def FC |
1899 | L<perlunicode> now contains an explanation of how to override, mangle |
1900 | and otherwise tweak the way perl handles upper-, lower- and other-case | |
1901 | conversions on Unicode data, and how to provide scoped changes to alter | |
1902 | one's own code's behaviour without stomping on anybody else. | |
5076a392 FC |
1903 | |
1904 | =head3 INSTALL explicitly states the requirement for C89 | |
1905 | ||
d430b8e7 FC |
1906 | This was already true but it's now Officially Stated For The Record |
1907 | (5.12.2). | |
5076a392 | 1908 | |
41e29def | 1909 | =head3 Explanation of C<\xI<HH>> and C<\oI<OOO>> escapes |
5076a392 | 1910 | |
41e29def FC |
1911 | L<perlop> has been updated with more detailed explanation of these two |
1912 | character escapes. | |
5076a392 | 1913 | |
41e29def | 1914 | =head3 C<-0I<NNN>> switch |
5076a392 | 1915 | |
41e29def | 1916 | In L<perlrun>, the behavior of the C<-0NNN> switch for C<-0400> or higher |
d430b8e7 | 1917 | has been clarified (5.12.2). |
5076a392 | 1918 | |
cdc10f43 FC |
1919 | =head3 Maintenance policy |
1920 | ||
1921 | L<perlpolicy> now contains the policy on what patches are acceptable for | |
1922 | maintenance branches (5.12.1). | |
1923 | ||
41e29def | 1924 | =head3 Deprecation policy |
5076a392 | 1925 | |
41e29def | 1926 | L<perlpolicy> now contains the policy on compatibility and deprecation |
d430b8e7 | 1927 | along with definitions of terms like "deprecation" (5.12.2). |
5076a392 | 1928 | |
41e29def | 1929 | =head3 New descriptions in L<perldiag> |
5076a392 FC |
1930 | |
1931 | The following existing diagnostics are now documented: | |
1932 | ||
1933 | =over 4 | |
1934 | ||
1935 | =item * | |
1936 | ||
1937 | L<Ambiguous use of %c resolved as operator %c|perldiag/"Ambiguous use of %c resolved as operator %c"> | |
1938 | ||
1939 | =item * | |
1940 | ||
1941 | L<Ambiguous use of %c{%s} resolved to %c%s|perldiag/"Ambiguous use of %c{%s} resolved to %c%s"> | |
1942 | ||
1943 | =item * | |
1944 | ||
1945 | L<Ambiguous use of %c{%s%s} resolved to %c%s%s|perldiag/"Ambiguous use of %c{%s%s} resolved to %c%s%s"> | |
1946 | ||
1947 | =item * | |
1948 | ||
1949 | L<Ambiguous use of -%s resolved as -&%s()|perldiag/"Ambiguous use of -%s resolved as -&%s()"> | |
1950 | ||
1951 | =item * | |
1952 | ||
1953 | L<Invalid strict version format (%s)|perldiag/"Invalid strict version format (%s)"> | |
1954 | ||
1955 | =item * | |
1956 | ||
1957 | L<Invalid version format (%s)|perldiag/"Invalid version format (%s)"> | |
1958 | ||
1959 | =item * | |
1960 | ||
1961 | L<Invalid version object|perldiag/"Invalid version object"> | |
1962 | ||
1963 | =back | |
1964 | ||
5076a392 FC |
1965 | =head3 L<perlbook> |
1966 | ||
41e29def | 1967 | L<perlbook> has been expanded to cover many more popular books. |
5076a392 | 1968 | |
41e29def | 1969 | =head3 C<SvTRUE> macro |
5076a392 | 1970 | |
41e29def FC |
1971 | The documentation for the C<SvTRUE> macro in |
1972 | L<perlapi> was simply wrong in stating that | |
5076a392 FC |
1973 | get-magic is not processed. It has been corrected. |
1974 | ||
41e29def | 1975 | =head3 L<perlvar> revamp |
5076a392 | 1976 | |
41e29def | 1977 | L<perlvar> reorders the variables and groups them by topic. Each variable |
5076a392 | 1978 | introduced after Perl 5.000 notes the first version in which it is |
41e29def | 1979 | available. L<perlvar> also has a new section for deprecated variables to |
5076a392 FC |
1980 | note when they were removed. |
1981 | ||
41e29def | 1982 | =head3 Array and hash slices in scalar context |
5076a392 | 1983 | |
41e29def | 1984 | These are now documented in L<perldata>. |
5076a392 | 1985 | |
41e29def | 1986 | =head3 C<use locale> and formats |
5076a392 FC |
1987 | |
1988 | L<perlform> and L<perllocale> have been corrected to state that | |
1989 | C<use locale> affects formats. | |
1990 | ||
5076a392 FC |
1991 | =head3 L<overload> |
1992 | ||
5076a392 FC |
1993 | L<overload>'s documentation has practically undergone a rewrite. It |
1994 | is now much more straightforward and clear. | |
1995 | ||
41e29def | 1996 | =head3 L<perlhack> and perlrepository revamp |
5076a392 FC |
1997 | |
1998 | The L<perlhack> and perlrepository documents have been heavily edited and | |
1999 | split up into several new documents. | |
2000 | ||
2001 | The L<perlhack> document is now much shorter, and focuses on the Perl 5 | |
2002 | development process and submitting patches to Perl. The technical content has | |
2003 | been moved to several new documents, L<perlsource>, L<perlinterp>, | |
2004 | L<perlhacktut>, and L<perlhacktips>. This technical content has only been | |
2005 | lightly edited. | |
2006 | ||
2007 | The perlrepository document has been renamed to L<perlgit>. This new document | |
2008 | is just a how-to on using git with the Perl source code. Any other content | |
2009 | that used to be in perlrepository has been moved to perlhack. | |
2010 | ||
41e29def | 2011 | =head3 Time::Piece examples |
5076a392 FC |
2012 | |
2013 | Examples in L<perlfaq4> have been updated to show the use of | |
41e29def | 2014 | L<Time::Piece>. |
5076a392 FC |
2015 | |
2016 | =head1 Diagnostics | |
2017 | ||
2018 | The following additions or changes have been made to diagnostic output, | |
2019 | including warnings and fatal error messages. For the complete list of | |
2020 | diagnostic messages, see L<perldiag>. | |
2021 | ||
2022 | =head2 New Diagnostics | |
2023 | ||
a593b319 FC |
2024 | =head3 New Errors |
2025 | ||
5076a392 FC |
2026 | =over |
2027 | ||
a593b319 | 2028 | =item Closure prototype called |
5076a392 | 2029 | |
a593b319 FC |
2030 | This error occurs when a subroutine reference passed to an attribute |
2031 | handler is called, if the subroutine is a closure [perl #68560]. | |
5076a392 | 2032 | |
a593b319 | 2033 | =item Insecure user-defined property %s |
5076a392 | 2034 | |
a593b319 FC |
2035 | Perl detected tainted data when trying to compile a regular |
2036 | expression that contains a call to a user-defined character property | |
2037 | function, i.e. C<\p{IsFoo}> or C<\p{InFoo}>. | |
2038 | See L<perlunicode/User-Defined Character Properties> and L<perlsec>. | |
5076a392 | 2039 | |
a593b319 | 2040 | =item panic: gp_free failed to free glob pointer - something is repeatedly re-creating entries |
5076a392 | 2041 | |
a593b319 FC |
2042 | This new error is triggered if a destructor called on an object in a |
2043 | typeglob that is being freed creates a new typeglob entry containing an | |
2044 | object with a destructor that creates a new entry containing an object.... | |
5076a392 | 2045 | |
a593b319 | 2046 | =item Parsing code internal error (%s) |
5076a392 | 2047 | |
a593b319 FC |
2048 | This new fatal error is produced when parsing |
2049 | code supplied by an extension violates the | |
2050 | parser's API in a detectable way. | |
5076a392 | 2051 | |
a593b319 | 2052 | =item refcnt: fd %d%s |
5076a392 | 2053 | |
a593b319 FC |
2054 | This new error only occurs if a internal consistency check fails when a |
2055 | pipe is about to be closed. | |
5076a392 | 2056 | |
a593b319 | 2057 | =item Regexp modifier "/%c" may not appear twice |
5076a392 | 2058 | |
a593b319 FC |
2059 | The regular expression pattern has one of the |
2060 | mutually exclusive modifiers repeated. | |
5076a392 | 2061 | |
a593b319 | 2062 | =item Regexp modifiers "/%c" and "/%c" are mutually exclusive |
5076a392 | 2063 | |
a593b319 FC |
2064 | The regular expression pattern has more than one of the mutually |
2065 | exclusive modifiers. | |
5076a392 | 2066 | |
a593b319 | 2067 | =item Using !~ with %s doesn't make sense |
5076a392 | 2068 | |
a593b319 | 2069 | This error occurs when C<!~> is used with C<s///r> or C<y///r>. |
5076a392 | 2070 | |
a593b319 | 2071 | =back |
5076a392 | 2072 | |
a593b319 | 2073 | =head3 New Warnings |
5076a392 | 2074 | |
a593b319 | 2075 | =over |
5076a392 | 2076 | |
a593b319 | 2077 | =item "\b{" is deprecated; use "\b\{" instead |
5076a392 | 2078 | |
a593b319 | 2079 | =item "\B{" is deprecated; use "\B\{" instead |
5076a392 | 2080 | |
a593b319 FC |
2081 | Use of an unescaped "{" immediately following a C<\b> or C<\B> is now |
2082 | deprecated so as to reserve its use for Perl itself in a future release. | |
5076a392 | 2083 | |
a593b319 | 2084 | =item Operation "%s" returns its argument for ... |
5076a392 | 2085 | |
a593b319 FC |
2086 | Performing an operation requiring Unicode semantics (such as case-folding) |
2087 | on a Unicode surrogate or a non-Unicode character now triggers a warning: | |
2088 | 'Operation "%s" returns its argument for ...'. | |
5076a392 | 2089 | |
a593b319 FC |
2090 | =item Use of qw(...) as parentheses is deprecated |
2091 | ||
2092 | See L</"Use of qw(...) as parentheses">, above, for details. | |
5076a392 FC |
2093 | |
2094 | =back | |
2095 | ||
2096 | =head2 Changes to Existing Diagnostics | |
2097 | ||
2098 | =over 4 | |
2099 | ||
2100 | =item * | |
2101 | ||
4ed2cea4 FC |
2102 | The "Variable $foo is not imported" warning that precedes a |
2103 | C<strict 'vars'> error has now been assigned the "misc" category, so that | |
2104 | C<no warnings> will suppress it [perl #73712]. | |
2105 | ||
2106 | =item * | |
2107 | ||
5076a392 FC |
2108 | C<warn> and C<die> now produce 'Wide character' warnings when fed a |
2109 | character outside the byte range if STDERR is a byte-sized handle. | |
2110 | ||
2111 | =item * | |
2112 | ||
2113 | The 'Layer does not match this perl' error message has been replaced with | |
a593b319 | 2114 | these more helpful messages [perl #73754]: |
5076a392 FC |
2115 | |
2116 | =over 4 | |
2117 | ||
2118 | =item * | |
2119 | ||
2120 | PerlIO layer function table size (%d) does not match size expected by this | |
2121 | perl (%d) | |
2122 | ||
2123 | =item * | |
2124 | ||
2125 | PerlIO layer instance size (%d) does not match size expected by this perl | |
2126 | (%d) | |
2127 | ||
2128 | =back | |
2129 | ||
5076a392 FC |
2130 | =item * |
2131 | ||
2132 | The "Found = in conditional" warning that is emitted when a constant is | |
2133 | assigned to a variable in a condition is now withheld if the constant is | |
2134 | actually a subroutine or one generated by C<use constant>, since the value | |
2135 | of the constant may not be known at the time the program is written | |
2136 | [perl #77762]. | |
2137 | ||
2138 | =item * | |
2139 | ||
2140 | Previously, if none of the C<gethostbyaddr>, C<gethostbyname> and | |
2141 | C<gethostent> functions were implemented on a given platform, they would | |
2142 | all die with the message 'Unsupported socket function "gethostent" called', | |
2143 | with analogous messages for C<getnet*> and C<getserv*>. This has been | |
2144 | corrected. | |
2145 | ||
2146 | =item * | |
2147 | ||
a593b319 FC |
2148 | The warning message about unrecognized regular expression escapes passed |
2149 | through has been changed to include any literal '{' following the | |
2150 | two-character escape. E.g., "\q{" is now emitted instead of "\q". | |
5076a392 FC |
2151 | |
2152 | =back | |
2153 | ||
2154 | =head1 Utility Changes | |
2155 | ||
0b88cc74 | 2156 | =head3 L<perlbug> |
5076a392 FC |
2157 | |
2158 | =over 4 | |
2159 | ||
2160 | =item * | |
2161 | ||
0b88cc74 FC |
2162 | L<perlbug> now looks in the EMAIL environment variable for a return address |
2163 | if the REPLY-TO and REPLYTO variables are empty. | |
5076a392 FC |
2164 | |
2165 | =item * | |
2166 | ||
0b88cc74 FC |
2167 | L<perlbug> did not previously generate a From: header, potentially |
2168 | resulting in dropped mail. Now it does include that header. | |
5076a392 FC |
2169 | |
2170 | =item * | |
2171 | ||
0b88cc74 | 2172 | The user's address is now used as the return-path. |
4ed2cea4 | 2173 | |
0b88cc74 FC |
2174 | Many systems these days don't have a valid Internet domain name and |
2175 | perlbug@perl.org does not accept email with a return-path that does | |
2176 | not resolve. So the user's address is now passed to sendmail so it's | |
2177 | less likely to get stuck in a mail queue somewhere [perl #82996]. | |
5076a392 | 2178 | |
2c389f6c FC |
2179 | =item * |
2180 | ||
d430b8e7 FC |
2181 | L<perlbug> now always gives the reporter a chance to change the email |
2182 | address it guesses for them (5.12.2). | |
2183 | ||
2184 | =item * | |
2185 | ||
2186 | L<perlbug> should no longer warn about uninitialized values when using the C<-d> | |
2187 | and C<-v> options (5.12.2). | |
2c389f6c | 2188 | |
5076a392 FC |
2189 | =back |
2190 | ||
0b88cc74 | 2191 | =head3 L<perl5db.pl> |
5076a392 | 2192 | |
0b88cc74 | 2193 | =over |
5076a392 FC |
2194 | |
2195 | =item * | |
2196 | ||
0b88cc74 FC |
2197 | The remote terminal works after forking and spawns new sessions - one |
2198 | for each forked process. | |
5076a392 FC |
2199 | |
2200 | =back | |
2201 | ||
0b88cc74 | 2202 | =head3 L<ptargrep> |
5076a392 FC |
2203 | |
2204 | =over 4 | |
2205 | ||
2206 | =item * | |
2207 | ||
0b88cc74 FC |
2208 | L<ptargrep> is a new utility to apply pattern matching to the contents of |
2209 | files in a tar archive. It comes with C<Archive::Tar>. | |
5076a392 FC |
2210 | |
2211 | =back | |
2212 | ||
2213 | =head1 Configuration and Compilation | |
2214 | ||
61752d82 FC |
2215 | See also L</"Naming fixes in Policy_sh.SH may invalidate Policy.sh">, |
2216 | above. | |
2217 | ||
5076a392 FC |
2218 | =over 4 |
2219 | ||
2220 | =item * | |
2221 | ||
87595b22 FC |
2222 | CCINCDIR and CCLIBDIR for the mingw64 |
2223 | cross-compiler are now correctly under | |
5076a392 FC |
2224 | $(CCHOME)\mingw\include and \lib rather than immediately below $(CCHOME). |
2225 | ||
5076a392 FC |
2226 | This means the 'incpath', 'libpth', 'ldflags', 'lddlflags' and |
2227 | 'ldflags_nolargefiles' values in Config.pm and Config_heavy.pl are now | |
87595b22 | 2228 | set correctly. |
5076a392 FC |
2229 | |
2230 | =item * | |
2231 | ||
87595b22 FC |
2232 | 'make test.valgrind' has been adjusted to account for cpan/dist/ext |
2233 | separation. | |
5076a392 FC |
2234 | |
2235 | =item * | |
2236 | ||
2237 | On compilers that support it, C<-Wwrite-strings> is now added to cflags by | |
2238 | default. | |
2239 | ||
2240 | =item * | |
2241 | ||
2242 | The C<Encode> module can now (once again) be included in a static Perl | |
2243 | build. The special-case handling for this situation got broken in Perl | |
2244 | 5.11.0, and has now been repaired. | |
2245 | ||
1e463951 FC |
2246 | =item * |
2247 | ||
2248 | The previous default size of a PerlIO buffer (4096 bytes) has been increased | |
2249 | to the larger of 8192 bytes and your local BUFSIZ. Benchmarks show that doubling | |
2250 | this decade-old default increases read and write performance in the neighborhood | |
2251 | of 25% to 50% when using the default layers of perlio on top of unix. To choose | |
2252 | a non-default size, such as to get back the old value or to obtain an even | |
2253 | larger value, configure with: | |
2254 | ||
2255 | ./Configure -Accflags=-DPERLIOBUF_DEFAULT_BUFSIZ=N | |
2256 | ||
2257 | where N is the desired size in bytes; it should probably be a multiple of | |
2258 | your page size. | |
2259 | ||
d430b8e7 FC |
2260 | =item * |
2261 | ||
2262 | An "incompatible operand types" error in ternary expressions when building | |
2263 | with C<clang> has been fixed (5.12.2). | |
2264 | ||
2265 | =item * | |
2266 | ||
2267 | Perl now skips setuid C<File::Copy> tests on partitions it detects to be mounted | |
2268 | as C<nosuid> (5.12.2). | |
2269 | ||
5076a392 FC |
2270 | =back |
2271 | ||
5076a392 FC |
2272 | =head1 Platform Support |
2273 | ||
5076a392 FC |
2274 | =head2 New Platforms |
2275 | ||
5076a392 FC |
2276 | =over 4 |
2277 | ||
2278 | =item AIX | |
2279 | ||
cdc10f43 | 2280 | Perl now builds on AIX 4.2 (5.12.1). |
5076a392 FC |
2281 | |
2282 | =back | |
2283 | ||
2284 | =head2 Discontinued Platforms | |
2285 | ||
2286 | =over 4 | |
2287 | ||
5076a392 FC |
2288 | =item Apollo DomainOS |
2289 | ||
2290 | The last vestiges of support for this platform have been excised from the | |
2291 | Perl distribution. It was officially discontinued in version 5.12.0. It had | |
2292 | not worked for years before that. | |
2293 | ||
2294 | =item MacOS Classic | |
2295 | ||
2296 | The last vestiges of support for this platform have been excised from the | |
2297 | Perl distribution. It was officially discontinued in an earlier version. | |
2298 | ||
2299 | =back | |
2300 | ||
2301 | =head2 Platform-Specific Notes | |
2302 | ||
d430b8e7 FC |
2303 | =head3 AIX |
2304 | ||
2305 | =over | |
2306 | ||
2307 | =item * | |
2308 | ||
2309 | F<README.aix> has been updated with information about the XL C/C++ V11 compiler | |
2310 | suite (5.12.2). | |
2311 | ||
2312 | =back | |
2313 | ||
2314 | =head3 ARM | |
2315 | ||
2316 | =over | |
2317 | ||
2318 | =item * | |
2319 | ||
2320 | The C<d_u32align> configuration probe on ARM has been fixed (5.12.2). | |
2321 | ||
2322 | =back | |
2323 | ||
554003a2 | 2324 | =head3 Cygwin |
5076a392 FC |
2325 | |
2326 | =over 4 | |
2327 | ||
2328 | =item * | |
2329 | ||
554003a2 | 2330 | MakeMaker has been updated to build man pages on cygwin. |
5076a392 FC |
2331 | |
2332 | =item * | |
2333 | ||
554003a2 FC |
2334 | Improved rebase behaviour |
2335 | ||
2336 | If a dll is updated on cygwin the old imagebase address is reused. | |
2337 | This solves most rebase errors, especially when updating on core dll's. | |
2338 | See L<http://www.tishler.net/jason/software/rebase/rebase-2.4.2.README> for more information. | |
5076a392 FC |
2339 | |
2340 | =item * | |
2341 | ||
554003a2 | 2342 | Support for the standard cygwin dll prefix, which is e.g. needed for FFI's |
5076a392 FC |
2343 | |
2344 | =item * | |
2345 | ||
554003a2 | 2346 | Updated build hints file |
5076a392 FC |
2347 | |
2348 | =back | |
2349 | ||
cdc10f43 FC |
2350 | =head3 FreeBSD 7 |
2351 | ||
2352 | =over | |
2353 | ||
2354 | =item * | |
2355 | ||
2356 | FreeBSD 7 no longer contains F</usr/bin/objformat>. At build time, | |
2357 | Perl now skips the F<objformat> check for versions 7 and higher and | |
2358 | assumes ELF (5.12.1). | |
2359 | ||
2360 | =back | |
2361 | ||
2362 | =head3 HP-UX | |
2363 | ||
2364 | =over | |
2365 | ||
2366 | =item * | |
2367 | ||
2368 | Perl now allows -Duse64bitint without promoting to use64bitall on HP-UX | |
2369 | (5.12.1). | |
2370 | ||
2371 | =back | |
2372 | ||
554003a2 | 2373 | =head3 IRIX |
5076a392 FC |
2374 | |
2375 | Conversion of strings to floating-point numbers is now more accurate on | |
2376 | IRIX systems [perl #32380]. | |
2377 | ||
554003a2 | 2378 | =head3 Mac OS X |
5076a392 FC |
2379 | |
2380 | Early versions of Mac OS X (Darwin) had buggy implementations of the | |
2381 | C<setregid>, C<setreuid>, C<setrgid> and C<setruid> functions, so perl | |
2382 | would pretend they did not exist. | |
2383 | ||
2384 | These functions are now recognised on Mac OS 10.5 (Leopard; Darwin 9) and | |
2385 | higher, as they have been fixed [perl #72990]. | |
2386 | ||
554003a2 | 2387 | =head3 MirBSD |
5076a392 | 2388 | |
554003a2 FC |
2389 | Previously if you built perl with a shared libperl.so on MirBSD (the |
2390 | default config), it would work up to the installation; however, once | |
2391 | installed, it would be unable to find libperl. So path handling is now | |
2392 | treated as in the other BSD dialects. | |
5076a392 | 2393 | |
554003a2 | 2394 | =head3 NetBSD |
5076a392 | 2395 | |
554003a2 FC |
2396 | The NetBSD hints file has been changed to make the system's malloc the |
2397 | default. | |
5076a392 | 2398 | |
554003a2 | 2399 | =head3 Recent OpenBSDs now use perl's malloc |
5076a392 | 2400 | |
554003a2 FC |
2401 | OpenBSD E<gt> 3.7 has a new malloc implementation which is mmap-based |
2402 | and as such can release memory back to the OS; however, perl's use of | |
2403 | this malloc causes a substantial slowdown so we now default to using | |
2404 | perl's malloc instead [perl #75742]. | |
5076a392 | 2405 | |
554003a2 | 2406 | =head3 OpenVOS |
5076a392 | 2407 | |
554003a2 | 2408 | perl now builds again with OpenVOS (formerly known as Stratus VOS) |
5a553547 | 2409 | [perl #78132] (5.12.3). |
5076a392 | 2410 | |
554003a2 | 2411 | =head3 Solaris |
5076a392 | 2412 | |
554003a2 | 2413 | DTrace is now supported on Solaris. There used to be build failures, but |
5a553547 | 2414 | these have been fixed [perl #73630] (5.12.3). |
5076a392 | 2415 | |
554003a2 | 2416 | =head3 VMS |
5076a392 FC |
2417 | |
2418 | =over | |
2419 | ||
2420 | =item * | |
2421 | ||
cdc10f43 FC |
2422 | It's now possible to build extensions on older (pre 7.3-2) VMS systems. |
2423 | ||
2424 | DCL symbol length was limited to 1K up until about seven years or | |
2425 | so ago, but there was no particularly deep reason to prevent those | |
2426 | older systems from configuring and building Perl (5.12.1). | |
2427 | ||
2428 | =item * | |
2429 | ||
2430 | We fixed the previously-broken C<-Uuseperlio> build on VMS. | |
2431 | ||
2432 | We were checking a variable that doesn't exist in the non-default | |
2433 | case of disabling perlio. Now we only look at it when it exists (5.12.1). | |
2434 | ||
2435 | =item * | |
2436 | ||
2437 | We fixed the -Uuseperlio command-line option in configure.com. | |
2438 | ||
2439 | Formerly it only worked if you went through all the questions | |
2440 | interactively and explicitly answered no (5.12.1). | |
2441 | ||
2442 | =item * | |
2443 | ||
554003a2 | 2444 | C<PerlIOUnix_open> now honours the default permissions on VMS. |
5076a392 | 2445 | |
554003a2 FC |
2446 | When C<perlio> became the default and C<unixio> became the default bottom layer, |
2447 | the most common path for creating files from Perl became C<PerlIOUnix_open>, | |
2448 | which has always explicitly used C<0666> as the permission mask. | |
5076a392 | 2449 | |
554003a2 FC |
2450 | To avoid this, C<0777> is now passed as the permissions to C<open()>. In the |
2451 | VMS CRTL, C<0777> has a special meaning over and above intersecting with the | |
2452 | current umask; specifically, it allows Unix syscalls to preserve native default | |
5a553547 FC |
2453 | permissions (5.12.3). |
2454 | ||
2455 | =item * | |
2456 | ||
2457 | Spurious record boundaries are no longer | |
2458 | introduced by the PerlIO layer during output (5.12.3). | |
5076a392 FC |
2459 | |
2460 | =item * | |
2461 | ||
554003a2 FC |
2462 | The shortening of symbols longer than 31 characters in the C sources is |
2463 | now done by the compiler rather than by xsubpp (which could only do so | |
2464 | for generated symbols in XS code). | |
5076a392 FC |
2465 | |
2466 | =item * | |
2467 | ||
554003a2 FC |
2468 | Record-oriented files (record format variable or variable with fixed control) |
2469 | opened for write by the perlio layer will now be line-buffered to prevent the | |
2470 | introduction of spurious line breaks whenever the perlio buffer fills up. | |
5076a392 | 2471 | |
d430b8e7 FC |
2472 | =item * |
2473 | ||
2474 | F<git_version.h> is now installed on VMS. This was an oversight in v5.12.0 which | |
2475 | caused some extensions to fail to build (5.12.2). | |
2476 | ||
2477 | =item * | |
2478 | ||
2479 | Several memory leaks in L<stat()|perlfunc/"stat FILEHANDLE"> have been fixed (5.12.2). | |
2480 | ||
2481 | =item * | |
2482 | ||
2483 | A memory leak in C<Perl_rename()> due to a double allocation has been | |
2484 | fixed (5.12.2). | |
2485 | ||
2486 | =item * | |
2487 | ||
2488 | A memory leak in C<vms_fid_to_name()> (used by C<realpath()> and | |
2489 | C<realname()>) has been fixed (5.12.2). | |
2490 | ||
5076a392 FC |
2491 | =back |
2492 | ||
554003a2 | 2493 | =head3 Windows |
5076a392 | 2494 | |
5a1f7719 FC |
2495 | See also L</"fork() emulation will not wait for signalled children"> and |
2496 | L</"Perl source code is read in text mode on Windows">, above. | |
2497 | ||
5076a392 FC |
2498 | =over 4 |
2499 | ||
2500 | =item * | |
2501 | ||
554003a2 | 2502 | Fixed build process for SDK2003SP1 compilers. |
5076a392 | 2503 | |
554003a2 | 2504 | =item * |
5076a392 | 2505 | |
01b1a9e4 FC |
2506 | Compilation with Visual Studio 2010 is now supported. |
2507 | ||
2508 | =item * | |
2509 | ||
554003a2 FC |
2510 | When using old 32-bit compilers, the define C<_USE_32BIT_TIME_T> will now |
2511 | be set in C<$Config{ccflags}>. This improves portability when compiling | |
2512 | XS extensions using new compilers, but for a perl compiled with old 32-bit | |
2513 | compilers. | |
5076a392 FC |
2514 | |
2515 | =item * | |
2516 | ||
554003a2 FC |
2517 | C<$Config{gccversion}> is now set correctly when perl is built using the |
2518 | mingw64 compiler from L<http://mingw64.org> [perl #73754]. | |
5076a392 | 2519 | |
554003a2 FC |
2520 | =item * |
2521 | ||
d430b8e7 FC |
2522 | When building Perl with the mingw64 x64 cross-compiler C<incpath>, |
2523 | C<libpth>, C<ldflags>, C<lddlflags> and C<ldflags_nolargefiles> values | |
2524 | in F<Config.pm> and F<Config_heavy.pl> were not previously being set | |
2525 | correctly because, with that compiler, the include and lib directories | |
2526 | are not immediately below C<$(CCHOME)> (5.12.2). | |
2527 | ||
2528 | =item * | |
2529 | ||
554003a2 FC |
2530 | The build process proceeds more smoothly with mingw and dmake when |
2531 | F<C:\MSYS\bin> is in the PATH, due to a C<Cwd> fix. | |
5076a392 FC |
2532 | |
2533 | =item * | |
2534 | ||
554003a2 FC |
2535 | Support for building with Visual C++ 2010 is now underway, but is not yet |
2536 | complete. See F<README.win32> or L<perlwin32> for more details. | |
5076a392 | 2537 | |
554003a2 FC |
2538 | =item * |
2539 | ||
2540 | The option to use an externally-supplied C<crypt()>, or to build with no | |
2541 | C<crypt()> at all, has been removed. Perl supplies its own C<crypt()> | |
2542 | implementation for Windows, and the political situation that required | |
2543 | this part of the distribution to sometimes be omitted is long gone. | |
5076a392 FC |
2544 | |
2545 | =back | |
2546 | ||
2547 | =head1 Internal Changes | |
2548 | ||
1e463951 | 2549 | =head2 New APIs |
5076a392 | 2550 | |
1e463951 | 2551 | =head3 CLONE_PARAMS structure added to ease correct thread creation |
5076a392 | 2552 | |
1e463951 FC |
2553 | Modules that create threads should now create C<CLONE_PARAMS> structures |
2554 | by calling the new function C<Perl_clone_params_new()>, and free them with | |
2555 | C<Perl_clone_params_del()>. This will ensure compatibility with any future | |
2556 | changes to the internals of the C<CLONE_PARAMS> structure layout, and that | |
2557 | it is correctly allocated and initialised. | |
5076a392 | 2558 | |
1e463951 | 2559 | =head3 New parsing functions |
5076a392 | 2560 | |
1e463951 FC |
2561 | Several functions have been added for parsing statements or multiple |
2562 | statements: | |
5076a392 | 2563 | |
1e463951 | 2564 | =over |
5076a392 FC |
2565 | |
2566 | =item * | |
2567 | ||
1e463951 | 2568 | C<parse_fullstmt> parses a complete Perl statement. |
5076a392 FC |
2569 | |
2570 | =item * | |
2571 | ||
1e463951 FC |
2572 | C<parse_stmtseq> parses a sequence of statements, up |
2573 | to closing brace or EOF. | |
5076a392 FC |
2574 | |
2575 | =item * | |
2576 | ||
1e463951 | 2577 | C<parse_block> parses a block [perl #78222]. |
5076a392 FC |
2578 | |
2579 | =item * | |
2580 | ||
1e463951 FC |
2581 | C<parse_barestmt> parses a statement |
2582 | without a label. | |
5076a392 FC |
2583 | |
2584 | =item * | |
2585 | ||
1e463951 | 2586 | C<parse_label> parses a statement label, separate from statements. |
5076a392 | 2587 | |
1e463951 | 2588 | =back |
5076a392 | 2589 | |
1e463951 FC |
2590 | The |
2591 | L<C<parse_fullexpr()>|perlapi/parse_fullexpr>, | |
2592 | L<C<parse_listexpr()>|perlapi/parse_listexpr>, | |
2593 | L<C<parse_termexpr()>|perlapi/parse_termexpr>, and | |
2594 | L<C<parse_arithexpr()>|perlapi/parse_arithexpr> | |
2595 | functions have been added to the API. They perform | |
2596 | recursive-descent parsing of expressions at various precedence levels. | |
2597 | They are expected to be used by syntax plugins. | |
5076a392 | 2598 | |
1e463951 | 2599 | See L<perlapi> for details. |
5076a392 | 2600 | |
1e463951 | 2601 | =head3 Hints hash API |
5076a392 | 2602 | |
1e463951 FC |
2603 | A new C API for introspecting the hinthash C<%^H> at runtime has been |
2604 | added. See C<cop_hints_2hv>, C<cop_hints_fetchpvn>, C<cop_hints_fetchpvs>, | |
2605 | C<cop_hints_fetchsv>, and C<hv_copy_hints_hv> in L<perlapi> for details. | |
5076a392 | 2606 | |
1e463951 FC |
2607 | A new, experimental API has been added for accessing the internal |
2608 | structure that Perl uses for C<%^H>. See the functions beginning with | |
2609 | C<cophh_> in L<perlapi>. | |
5076a392 | 2610 | |
1e463951 | 2611 | =head3 C interface to C<caller()> |
5076a392 | 2612 | |
1e463951 FC |
2613 | The C<caller_cx> function has been added as an XSUB-writer's equivalent of |
2614 | C<caller()>. See L<perlapi> for details. | |
5076a392 | 2615 | |
1e463951 | 2616 | =head3 Custom per-subroutine check hooks |
5076a392 | 2617 | |
1e463951 FC |
2618 | XS code in an extension module can now annotate a subroutine (whether |
2619 | implemented in XS or in Perl) so that nominated XS code will be called | |
2620 | at compile time (specifically as part of op checking) to change the op | |
2621 | tree of that subroutine. The compile-time check function (supplied by | |
2622 | the extension module) can implement argument processing that can't be | |
2623 | expressed as a prototype, generate customised compile-time warnings, | |
2624 | perform constant folding for a pure function, inline a subroutine | |
2625 | consisting of sufficiently simple ops, replace the whole call with a | |
2626 | custom op, and so on. This was previously all possible by hooking the | |
2627 | C<entersub> op checker, but the new mechanism makes it easy to tie the | |
2628 | hook to a specific subroutine. See L<perlapi/cv_set_call_checker>. | |
5076a392 | 2629 | |
1e463951 FC |
2630 | To help in writing custom check hooks, several subtasks within standard |
2631 | C<entersub> op checking have been separated out and exposed in the API. | |
5076a392 | 2632 | |
1e463951 | 2633 | =head3 Improved support for custom OPs |
5076a392 | 2634 | |
1e463951 FC |
2635 | Custom ops can now be registered with the new C<custom_op_register> C |
2636 | function and the C<XOP> structure. This will make it easier to add new | |
2637 | properties of custom ops in the future. Two new properties have been added | |
2638 | already, C<xop_class> and C<xop_peep>. | |
5076a392 | 2639 | |
1e463951 FC |
2640 | C<xop_class> is one of the OA_*OP constants, and allows L<B> and other |
2641 | introspection mechanisms to work with custom ops | |
2642 | that aren't BASEOPs. C<xop_peep> is a pointer to | |
2643 | a function that will be called for ops of this | |
2644 | type from C<Perl_rpeep>. | |
5076a392 | 2645 | |
1e463951 FC |
2646 | See L<perlguts/Custom Operators> and L<perlapi/Custom Operators> for more |
2647 | detail. | |
5076a392 | 2648 | |
1e463951 FC |
2649 | The old C<PL_custom_op_names>/C<PL_custom_op_descs> interface is still |
2650 | supported but discouraged. | |
5076a392 | 2651 | |
1e463951 | 2652 | =head3 Scope hooks |
5076a392 | 2653 | |
1e463951 FC |
2654 | It is now possible for XS code to hook into Perl's lexical scope |
2655 | mechanism at compile time, using the new C<Perl_blockhook_register> | |
2656 | function. See L<perlguts/"Compile-time scope hooks">. | |
5076a392 | 2657 | |
1e463951 | 2658 | =head3 The recursive part of the peephole optimizer is now hookable |
5076a392 FC |
2659 | |
2660 | In addition to C<PL_peepp>, for hooking into the toplevel peephole optimizer, a | |
2661 | C<PL_rpeepp> is now available to hook into the optimizer recursing into | |
2662 | side-chains of the optree. | |
2663 | ||
1e463951 | 2664 | =head3 New non-magical variants of existing functions |
5076a392 | 2665 | |
1e463951 FC |
2666 | The following functions/macros have been added to the API. The C<*_nomg> |
2667 | macros are equivalent to their non-_nomg variants, except that they ignore | |
2668 | get-magic. Those ending in C<_flags> allow one to specify whether | |
2669 | get-magic is processed. | |
5076a392 | 2670 | |
1e463951 FC |
2671 | sv_2bool_flags |
2672 | SvTRUE_nomg | |
2673 | sv_2nv_flags | |
2674 | SvNV_nomg | |
2675 | sv_cmp_flags | |
2676 | sv_cmp_locale_flags | |
2677 | sv_eq_flags | |
2678 | sv_collxfrm_flags | |
5076a392 | 2679 | |
1e463951 | 2680 | In some of these cases, the non-_flags functions have |
5076a392 FC |
2681 | been replaced with wrappers around the new functions. |
2682 | ||
1e463951 | 2683 | =head3 pv/pvs/sv versions of existing functions |
5076a392 | 2684 | |
1e463951 | 2685 | Many functions ending with pvn now have equivalent pv/pvs/sv versions. |
5076a392 | 2686 | |
1e463951 | 2687 | =head3 List op-building functions |
5076a392 | 2688 | |
1e463951 FC |
2689 | List op-building functions have been added to the |
2690 | API. See L<op_append_elem|perlapi/op_append_elem>, | |
2691 | L<op_append_list|perlapi/op_append_list>, and | |
2692 | L<op_prepend_elem|perlapi/op_prepend_elem> in L<perlapi>. | |
5076a392 | 2693 | |
1e463951 | 2694 | =head3 C<LINKLIST> |
5076a392 | 2695 | |
1e463951 FC |
2696 | The L<LINKLIST|perlapi/LINKLIST> macro, part of op building that |
2697 | constructs the execution-order op chain, has been added to the API. | |
5076a392 | 2698 | |
1e463951 | 2699 | =head3 Localisation functions |
5076a392 | 2700 | |
1e463951 FC |
2701 | The C<save_freeop>, C<save_op>, C<save_pushi32ptr> and C<save_pushptrptr> |
2702 | functions have been added to the API. | |
5076a392 | 2703 | |
1e463951 | 2704 | =head3 Stash names |
5076a392 | 2705 | |
1e463951 FC |
2706 | A stash can now have a list of effective names in addition to its usual |
2707 | name. The first effective name can be accessed via the C<HvENAME> macro, | |
2708 | which is now the recommended name to use in MRO linearisations (C<HvNAME> | |
2709 | being a fallback if there is no C<HvENAME>). | |
5076a392 | 2710 | |
1e463951 FC |
2711 | These names are added and deleted via C<hv_ename_add> and |
2712 | C<hv_ename_delete>. These two functions are I<not> part of the API. | |
5076a392 | 2713 | |
1e463951 | 2714 | =head3 New functions for finding and removing magic |
5076a392 | 2715 | |
1e463951 FC |
2716 | The L<C<mg_findext()>|perlapi/mg_findext> and |
2717 | L<C<sv_unmagicext()>|perlapi/sv_unmagicext> | |
2718 | functions have been added to the API. | |
2719 | They allow extension authors to find and remove magic attached to | |
2720 | scalars based on both the magic type and the magic virtual table, similar to how | |
2721 | C<sv_magicext()> attaches magic of a certain type and with a given virtual table | |
2722 | to a scalar. This eliminates the need for extensions to walk the list of | |
2723 | C<MAGIC> pointers of an C<SV> to find the magic that belongs to them. | |
5076a392 | 2724 | |
1e463951 | 2725 | =head3 C<find_rundefsv> |
5076a392 | 2726 | |
1e463951 FC |
2727 | This function returns the SV representing C<$_>, whether it's lexical |
2728 | or dynamic. | |
5076a392 | 2729 | |
1e463951 | 2730 | =head3 C<Perl_croak_no_modify> |
5076a392 | 2731 | |
1e463951 FC |
2732 | C<Perl_croak_no_modify()> is short-hand for |
2733 | C<Perl_croak("%s", PL_no_modify)>. | |
5076a392 | 2734 | |
1e463951 | 2735 | =head3 C<PERL_STATIC_INLINE> define |
5076a392 | 2736 | |
1e463951 FC |
2737 | The C<PERL_STATIC_INLINE> define has been added to provide the best-guess |
2738 | incantation to use for static inline functions, if the C compiler supports | |
2739 | C99-style static inline. If it doesn't, it'll give a plain C<static>. | |
5076a392 | 2740 | |
1e463951 FC |
2741 | C<HAS_STATIC_INLINE> can be used to check if the compiler actually supports |
2742 | inline functions. | |
5076a392 | 2743 | |
1e463951 | 2744 | =head3 New C<pv_escape> option for hexadecimal escapes |
5076a392 | 2745 | |
1e463951 FC |
2746 | A new option, C<PERL_PV_ESCAPE_NONASCII>, has been added to C<pv_escape> to |
2747 | dump all characters above ASCII in hexadecimal. Before, one could get all | |
2748 | characters as hexadecimal or the Latin1 non-ASCII as octal. | |
5076a392 | 2749 | |
1e463951 | 2750 | =head3 C<lex_start> |
5076a392 | 2751 | |
1e463951 | 2752 | C<lex_start> has been added to the API, but is considered experimental. |
5076a392 | 2753 | |
1e463951 | 2754 | =head3 C<op_scope()> and C<op_lvalue()> |
5076a392 | 2755 | |
1e463951 FC |
2756 | The C<op_scope()> and C<op_lvalue()> functions have been added to the API, |
2757 | but are considered experimental. | |
5076a392 | 2758 | |
1e463951 | 2759 | =head2 C API Changes |
5076a392 | 2760 | |
1e463951 | 2761 | =head3 C<PERL_POLLUTE> has been removed |
5076a392 | 2762 | |
1e463951 FC |
2763 | The option to define C<PERL_POLLUTE> to expose older 5.005 symbols for |
2764 | backwards compatibility has been removed. It's use was always discouraged, | |
2765 | and MakeMaker contains a more specific escape hatch: | |
5076a392 | 2766 | |
1e463951 | 2767 | perl Makefile.PL POLLUTE=1 |
5076a392 | 2768 | |
1e463951 FC |
2769 | This can be used for modules that have not been upgraded to 5.6 naming |
2770 | conventions (and really should be completely obsolete by now). | |
5076a392 | 2771 | |
1e463951 | 2772 | =head3 Check API compatibility when loading XS modules |
5076a392 | 2773 | |
1e463951 FC |
2774 | When perl's API changes in incompatible ways (which usually happens between |
2775 | major releases), XS modules compiled for previous versions of perl will not | |
2776 | work anymore. They will need to be recompiled against the new perl. | |
5076a392 | 2777 | |
1e463951 FC |
2778 | In order to ensure that modules are recompiled, and to prevent users from |
2779 | accidentally loading modules compiled for old perls into newer ones, the | |
2780 | C<XS_APIVERSION_BOOTCHECK> macro has been added. That macro, which is | |
2781 | called when loading every newly compiled extension, compares the API | |
2782 | version of the running perl with the version a module has been compiled for | |
2783 | and raises an exception if they don't match. | |
5076a392 | 2784 | |
1e463951 | 2785 | =head3 Perl_fetch_cop_label |
5076a392 | 2786 | |
1e463951 FC |
2787 | The first argument of the C API function C<Perl_fetch_cop_label> has changed |
2788 | from C<struct refcounted he *> to C<COP *>, to insulate the user from | |
2789 | implementation details. | |
5076a392 | 2790 | |
1e463951 FC |
2791 | This API function was marked as "may change", and likely isn't in use outside |
2792 | the core. (Neither an unpacked CPAN, nor Google's codesearch, finds any other | |
2793 | references to it.) | |
5076a392 | 2794 | |
1e463951 | 2795 | =head3 GvCV() and GvGP() are no longer lvalues |
5076a392 | 2796 | |
1e463951 FC |
2797 | The new GvCV_set() and GvGP_set() macros are now provided to replace |
2798 | assignment to those two macros. | |
5076a392 | 2799 | |
1e463951 FC |
2800 | This allows a future commit to eliminate some backref magic between GV |
2801 | and CVs, which will require complete control over assignment to the | |
2802 | gp_cv slot. | |
5076a392 | 2803 | |
1e463951 | 2804 | =head3 CvGV() is no longer an lvalue |
5076a392 | 2805 | |
1e463951 FC |
2806 | Under some circumstances, the C<CvGV()> field of a CV is now |
2807 | reference-counted. To ensure consistent behaviour, direct assignment to | |
2808 | it, for example C<CvGV(cv) = gv> is now a compile-time error. A new macro, | |
2809 | C<CvGV_set(cv,gv)> has been introduced to perform this operation | |
2810 | safely. Note that modification of this field is not part of the public | |
2811 | API, regardless of this new macro (and despite its being listed in this section). | |
5076a392 | 2812 | |
1e463951 | 2813 | =head3 CvSTASH() is no longer an lvalue |
5076a392 | 2814 | |
1e463951 FC |
2815 | The C<CvSTASH()> macro can now only be used as an rvalue. C<CvSTASH_set()> |
2816 | has been added to replace assignment to C<CvSTASH()>. This is to ensure | |
2817 | that backreferences are handled properly. These macros are not part of the | |
2818 | API. | |
5076a392 | 2819 | |
1e463951 | 2820 | =head3 Calling conventions for C<newFOROP> and C<newWHILEOP> |
5076a392 | 2821 | |
1e463951 FC |
2822 | The way the parser handles labels has been cleaned up and refactored. As a |
2823 | result, the C<newFOROP()> constructor function no longer takes a parameter | |
2824 | stating what label is to go in the state op. | |
5076a392 | 2825 | |
1e463951 FC |
2826 | The C<newWHILEOP()> and C<newFOROP()> functions no longer accept a line |
2827 | number as a parameter. | |
5076a392 | 2828 | |
1e463951 | 2829 | =head3 Flags passed to C<uvuni_to_utf8_flags> and C<utf8n_to_uvuni> |
5076a392 | 2830 | |
1e463951 FC |
2831 | Some of the flags parameters to uvuni_to_utf8_flags() and |
2832 | utf8n_to_uvuni() have changed. This is a result of Perl's now allowing | |
5076a392 FC |
2833 | internal storage and manipulation of code points that are problematic |
2834 | in some situations. Hence, the default actions for these functions has | |
2835 | been complemented to allow these code points. The new flags are | |
2836 | documented in L<perlapi>. Code that requires the problematic code | |
2837 | points to be rejected needs to change to use these flags. Some flag | |
2838 | names are retained for backward source compatibility, though they do | |
2839 | nothing, as they are now the default. However the flags | |
2840 | C<UNICODE_ALLOW_FDD0>, C<UNICODE_ALLOW_FFFF>, C<UNICODE_ILLEGAL>, and | |
2841 | C<UNICODE_IS_ILLEGAL> have been removed, as they stem from a | |
2842 | fundamentally broken model of how the Unicode non-character code points | |
2843 | should be handled, which is now described in | |
2844 | L<perlunicode/Non-character code points>. See also L</Selected Bug Fixes>. | |
2845 | ||
1e463951 FC |
2846 | XXX Which bugs in particular? Selected Bug Fixes is too long for this link |
2847 | to be meaningful right now. | |
5076a392 | 2848 | |
1e463951 | 2849 | =head2 Deprecated C APIs |
5076a392 | 2850 | |
1e463951 | 2851 | =over |
5076a392 | 2852 | |
1e463951 | 2853 | =item C<Perl_ptr_table_clear> |
5076a392 | 2854 | |
1e463951 FC |
2855 | C<Perl_ptr_table_clear> is no longer part of Perl's public API. Calling it |
2856 | now generates a deprecation warning, and it will be removed in a future | |
2857 | release. | |
5076a392 | 2858 | |
1e463951 | 2859 | =item C<sv_compile_2op> |
5076a392 | 2860 | |
1e463951 FC |
2861 | The C<sv_compile_2op()> API function is now deprecated. Searches suggest |
2862 | that nothing on CPAN is using it, so this should have zero impact. | |
5076a392 | 2863 | |
1e463951 FC |
2864 | It attempted to provide an API to compile code down to an optree, but failed |
2865 | to bind correctly to lexicals in the enclosing scope. It's not possible to | |
2866 | fix this problem within the constraints of its parameters and return value. | |
5076a392 | 2867 | |
1e463951 | 2868 | =item C<find_rundefsvoffset> |
5076a392 | 2869 | |
1e463951 FC |
2870 | The C<find_rundefsvoffset> function has been deprecated. It appeared that |
2871 | its design was insufficient for reliably getting the lexical C<$_> at | |
2872 | run-time. | |
5076a392 | 2873 | |
1e463951 FC |
2874 | Use the new C<find_rundefsv> function or the C<UNDERBAR> macro |
2875 | instead. They directly return the right SV representing C<$_>, whether it's | |
2876 | lexical or dynamic. | |
5076a392 | 2877 | |
1e463951 | 2878 | =item C<CALL_FPTR> and C<CPERLscope> |
5076a392 | 2879 | |
1e463951 FC |
2880 | Those are left from an old implementation of C<MULTIPLICITY> using C++ objects, |
2881 | which was removed in Perl 5.8. Nowadays these macros do exactly nothing, so | |
2882 | they shouldn't be used anymore. | |
5076a392 | 2883 | |
1e463951 FC |
2884 | For compatibility, they are still defined for external C<XS> code. Only |
2885 | extensions defining C<PERL_CORE> must be updated now. | |
5076a392 | 2886 | |
1e463951 | 2887 | =back |
5076a392 | 2888 | |
1e463951 | 2889 | =head2 Other Internal Changes |
5076a392 | 2890 | |
1e463951 | 2891 | =head3 Stack unwinding |
5076a392 | 2892 | |
1e463951 FC |
2893 | The protocol for unwinding the C stack at the last stage of a C<die> |
2894 | has changed how it identifies the target stack frame. This now uses | |
2895 | a separate variable C<PL_restartjmpenv>, where previously it relied on | |
2896 | the C<blk_eval.cur_top_env> pointer in the C<eval> context frame that | |
2897 | has nominally just been discarded. This change means that code running | |
2898 | during various stages of Perl-level unwinding no longer needs to take | |
2899 | care to avoid destroying the ghost frame. | |
5076a392 | 2900 | |
1e463951 | 2901 | =head3 Scope stack entries |
5076a392 | 2902 | |
1e463951 FC |
2903 | The format of entries on the scope stack has been changed, resulting in a |
2904 | reduction of memory usage of about 10%. In particular, the memory used by | |
2905 | the scope stack to record each active lexical variable has been halved. | |
5076a392 | 2906 | |
1e463951 | 2907 | =head3 Memory allocation for pointer tables |
5076a392 | 2908 | |
1e463951 FC |
2909 | Memory allocation for pointer tables has been changed. Previously |
2910 | C<Perl_ptr_table_store> allocated memory from the same arena system as | |
2911 | C<SV> bodies and C<HE>s, with freed memory remaining bound to those arenas | |
2912 | until interpreter exit. Now it allocates memory from arenas private to the | |
2913 | specific pointer table, and that memory is returned to the system when | |
2914 | C<Perl_ptr_table_free> is called. Additionally, allocation and release are | |
2915 | both less CPU intensive. | |
5076a392 | 2916 | |
1e463951 | 2917 | =head3 C<UNDERBAR> |
5076a392 | 2918 | |
1e463951 FC |
2919 | The C<UNDERBAR> macro now calls C<find_rundefsv>. C<dUNDERBAR> is now a |
2920 | noop but should still be used to ensure past and future compatibility. | |
5076a392 | 2921 | |
1e463951 | 2922 | =head3 String comparison routines renamed |
5076a392 | 2923 | |
1e463951 FC |
2924 | The ibcmp_* functions have been renamed and are now called foldEQ, |
2925 | foldEQ_locale and foldEQ_utf8. The old names are still available as | |
2926 | macros. | |
2927 | ||
2928 | =head3 C<chop> and C<chomp> implementations merged | |
2929 | ||
2930 | The opcode bodies for C<chop> and C<chomp> and for C<schop> and C<schomp> | |
2931 | have been merged. The implementation functions C<Perl_do_chop()> and | |
2932 | C<Perl_do_chomp()>, never part of the public API, have been merged and | |
2933 | moved to a static function in F<pp.c>. This shrinks the perl binary | |
2934 | slightly, and should not affect any code outside the core (unless it is | |
2935 | relying on the order of side effects when C<chomp> is passed a I<list> of | |
2936 | values). | |
5076a392 FC |
2937 | |
2938 | =head1 Selected Bug Fixes | |
2939 | ||
e8e35311 FC |
2940 | =head2 I/O |
2941 | ||
5076a392 FC |
2942 | =over 4 |
2943 | ||
2944 | =item * | |
2945 | ||
e8e35311 | 2946 | Perl no longer produces this warning: |
a593b319 FC |
2947 | |
2948 | $ perl -we 'open my $f, ">", \my $x; binmode $f, "scalar"' | |
2949 | Use of uninitialized value in binmode at -e line 1. | |
2950 | ||
2951 | =item * | |
2952 | ||
e8e35311 FC |
2953 | Opening a glob reference via C<< open $fh, "E<gt>", \*glob >> will no longer |
2954 | cause the glob to be corrupted when the filehandle is printed to. This would | |
2955 | cause perl to crash whenever the glob's contents were accessed | |
2956 | [perl #77492]. | |
4ed2cea4 FC |
2957 | |
2958 | =item * | |
2959 | ||
e8e35311 FC |
2960 | PerlIO no longer crashes when called recursively, e.g., from a signal |
2961 | handler. Now it just leaks memory [perl #75556]. | |
4ed2cea4 FC |
2962 | |
2963 | =item * | |
2964 | ||
e8e35311 FC |
2965 | Most I/O functions were not warning for unopened handles unless the |
2966 | 'closed' and 'unopened' warnings categories were both enabled. Now only | |
2967 | C<use warnings 'unopened'> is necessary to trigger these warnings (as was | |
438c239f | 2968 | always meant to be the case). |
4ed2cea4 FC |
2969 | |
2970 | =item * | |
2971 | ||
438c239f | 2972 | There have been several fixes to PerlIO layers: |
e8e35311 | 2973 | |
438c239f FC |
2974 | When C<binmode FH, ":crlf"> pushes the C<:crlf> layer on top of the stack, |
2975 | it no longer enables crlf layers lower in the stack, to avoid unexpected | |
2976 | results [perl #38456]. | |
4ed2cea4 | 2977 | |
438c239f FC |
2978 | Opening a file in C<:raw> mode now does what it advertises to do (first |
2979 | open the file, then binmode it), instead of simply leaving off the top | |
2980 | layer [perl #80764]. | |
5076a392 | 2981 | |
438c239f FC |
2982 | The three layers C<:pop>, C<:utf8> and C<:bytes> didn't allow stacking when |
2983 | opening a file. For example | |
e8e35311 | 2984 | this: |
5076a392 | 2985 | |
e8e35311 | 2986 | open FH, '>:pop:perlio', 'some.file' or die $!; |
5076a392 | 2987 | |
438c239f FC |
2988 | Would throw an error: "Invalid argument". This has been fixed in this |
2989 | release [perl #82484]. | |
5076a392 | 2990 | |
e8e35311 FC |
2991 | =back |
2992 | ||
2993 | =head2 Regular Expression Bug Fixes | |
2994 | ||
2995 | =over | |
5076a392 FC |
2996 | |
2997 | =item * | |
2998 | ||
e8e35311 FC |
2999 | The regular expression engine no longer loops when matching |
3000 | C<"\N{LATIN SMALL LIGATURE FF}" =~ /f+/i> and similar expressions | |
cdc10f43 | 3001 | [perl #72998] (5.12.1). |
5076a392 FC |
3002 | |
3003 | =item * | |
3004 | ||
e8e35311 FC |
3005 | The trie runtime code should no longer allocate massive amounts of memory, |
3006 | fixing #74484. | |
5076a392 FC |
3007 | |
3008 | =item * | |
3009 | ||
438c239f FC |
3010 | Syntax errors in C<< (?{...}) >> blocks no longer cause panic messages |
3011 | [perl #2353]. | |
5076a392 FC |
3012 | |
3013 | =item * | |
3014 | ||
438c239f FC |
3015 | A pattern like C<(?:(o){2})?> no longer causes a "panic" error |
3016 | [perl #39233]. | |
5076a392 FC |
3017 | |
3018 | =item * | |
3019 | ||
438c239f | 3020 | A fatal error in regular expressions containing C<(.*?)> when processing |
d430b8e7 | 3021 | UTF-8 data has been fixed [perl #75680] (5.12.2). |
5076a392 FC |
3022 | |
3023 | =item * | |
3024 | ||
e8e35311 | 3025 | An erroneous regular expression engine optimisation that caused regex verbs like |
438c239f | 3026 | C<*COMMIT> sometimes to be ignored has been removed. |
5076a392 FC |
3027 | |
3028 | =item * | |
3029 | ||
e8e35311 FC |
3030 | The regular expression bracketed character class C<[\8\9]> was effectively the |
3031 | same as C<[89\000]>, incorrectly matching a NULL character. It also gave | |
3032 | incorrect warnings that the C<8> and C<9> were ignored. Now C<[\8\9]> is the | |
3033 | same as C<[89]> and gives legitimate warnings that C<\8> and C<\9> are | |
3034 | unrecognized escape sequences, passed-through. | |
5076a392 FC |
3035 | |
3036 | =item * | |
3037 | ||
e8e35311 FC |
3038 | A regular expression match in the right-hand side of a global substitution |
3039 | (C<s///g>) that is in the same scope will no longer cause match variables | |
3040 | to have the wrong values on subsequent iterations. This can happen when an | |
3041 | array or hash subscript is interpolated in the right-hand side, as in | |
3042 | C<s|(.)|@a{ print($1), /./ }|g> [perl #19078]. | |
5076a392 FC |
3043 | |
3044 | =item * | |
3045 | ||
438c239f FC |
3046 | Several cases in which characters in the Latin-1 non-ASCII range (0x80 to |
3047 | 0xFF) used not to match themselves or used to match both a character class | |
3048 | and its complement have been fixed. For instance, U+00E2 could match both | |
3049 | C<\w> and C<\W> [perl #78464] [perl #18281] [perl #60156]. | |
5076a392 FC |
3050 | |
3051 | =item * | |
3052 | ||
e8e35311 FC |
3053 | Matching a Unicode character against an alternation containing characters |
3054 | that happened to match continuation bytes in the former's UTF8 | |
3055 | representation (C<qq{\x{30ab}} =~ /\xab|\xa9/>) would cause erroneous | |
3056 | warnings [perl #70998]. | |
5076a392 FC |
3057 | |
3058 | =item * | |
3059 | ||
e8e35311 FC |
3060 | The trie optimisation was not taking empty groups into account, preventing |
3061 | 'foo' from matching C</\A(?:(?:)foo|bar|zot)\z/> [perl #78356]. | |
5076a392 FC |
3062 | |
3063 | =item * | |
3064 | ||
e8e35311 FC |
3065 | A pattern containing a C<+> inside a lookahead would sometimes cause an |
3066 | incorrect match failure in a global match (e.g., C</(?=(\S+))/g>) | |
3067 | [perl #68564]. | |
5076a392 FC |
3068 | |
3069 | =item * | |
3070 | ||
e8e35311 FC |
3071 | A regular expression optimisation would sometimes cause a match with a |
3072 | C<{n,m}> quantifier to fail when it should match [perl #79152]. | |
5076a392 FC |
3073 | |
3074 | =item * | |
3075 | ||
e8e35311 | 3076 | Case insensitive matching in regular expressions compiled under C<use |
438c239f FC |
3077 | locale> now works much more sanely when the pattern or |
3078 | target string is encoded internally in | |
3079 | UTF8. Previously, under these conditions the localeness | |
e8e35311 FC |
3080 | was completely lost. Now, code points above 255 are treated as Unicode, |
3081 | but code points between 0 and 255 are treated using the current locale | |
438c239f FC |
3082 | rules, regardless of whether the pattern or the string is encoded in UTF8. |
3083 | The few case-insensitive matches that cross the 255/256 boundary are not | |
e8e35311 FC |
3084 | allowed. For example, 0xFF does not caselessly match the character at |
3085 | 0x178, LATIN CAPITAL LETTER Y WITH DIAERESIS, because 0xFF may not be | |
3086 | LATIN SMALL LETTER Y in the current locale, and Perl has no way of | |
3087 | knowing if that character even exists in the locale, much less what code | |
3088 | point it is. | |
5076a392 FC |
3089 | |
3090 | =item * | |
3091 | ||
e8e35311 FC |
3092 | The C<(?|...)> regular expression construct no longer crashes if the final |
3093 | branch has more sets of capturing parentheses than any other branch. This | |
3094 | was fixed in Perl 5.10.1 for the case of a single branch, but that fix did | |
3095 | not take multiple branches into account [perl #84746]. | |
5076a392 FC |
3096 | |
3097 | =item * | |
3098 | ||
e8e35311 FC |
3099 | A bug has been fixed in the implementation of C<{...}> quantifiers in |
3100 | regular expressions that prevented the code block in | |
3101 | C</((\w+)(?{ print $2 })){2}/> from seeing the C<$2> sometimes | |
3102 | [perl #84294]. | |
5076a392 | 3103 | |
e8e35311 | 3104 | =back |
5076a392 | 3105 | |
e8e35311 FC |
3106 | =head2 Syntax/Parsing Bugs |
3107 | ||
3108 | =over | |
5076a392 FC |
3109 | |
3110 | =item * | |
3111 | ||
e8e35311 | 3112 | C<when(scalar){...}> no longer crashes, but produces a syntax error |
cdc10f43 | 3113 | [perl #74114] (5.12.1). |
5076a392 FC |
3114 | |
3115 | =item * | |
3116 | ||
e8e35311 FC |
3117 | A label right before a string eval (C<foo: eval $string>) no longer causes |
3118 | the label to be associated also with the first statement inside the eval | |
3119 | [perl #74290] (5.12.1). | |
5076a392 FC |
3120 | |
3121 | =item * | |
3122 | ||
b2c076b5 | 3123 | The C<no 5.13.2;> form of C<no> no longer tries to turn on features or |
d430b8e7 | 3124 | pragmata (i.e., strict) [perl #70075] (5.12.2). |
5076a392 FC |
3125 | |
3126 | =item * | |
3127 | ||
b2c076b5 FC |
3128 | C<BEGIN {require 5.12.0}> now behaves as documented, rather than behaving |
3129 | identically to C<use 5.12.0;>. Previously, C<require> in a C<BEGIN> block | |
3130 | was erroneously executing the C<use feature ':5.12.0'> and | |
3131 | C<use strict;> behaviour, which only C<use> was documented to | |
3132 | provide [perl #69050]. | |
5076a392 FC |
3133 | |
3134 | =item * | |
3135 | ||
5076a392 FC |
3136 | A regression introduced in Perl 5.12.0, making |
3137 | C<< my $x = 3; $x = length(undef) >> result in C<$x> set to C<3> has been | |
d430b8e7 | 3138 | fixed. C<$x> will now be C<undef> [perl #85508] (5.12.2). |
b2c076b5 FC |
3139 | |
3140 | =item * | |
3141 | ||
3142 | When strict 'refs' mode is off, C<%{...}> in rvalue context returns | |
3143 | C<undef> if its argument is undefined. An optimisation introduced in perl | |
3144 | 5.12.0 to make C<keys %{...}> faster when used as a boolean did not take | |
3145 | this into account, causing C<keys %{+undef}> (and C<keys %$foo> when | |
3146 | C<$foo> is undefined) to be an error, which it should only be in strict | |
3147 | mode [perl #81750]. | |
5076a392 FC |
3148 | |
3149 | =item * | |
3150 | ||
e8e35311 | 3151 | Constant-folding used to cause |
5076a392 | 3152 | |
e8e35311 | 3153 | $text =~ ( 1 ? /phoo/ : /bear/) |
5076a392 | 3154 | |
e8e35311 FC |
3155 | to turn into |
3156 | ||
3157 | $text =~ /phoo/ | |
3158 | ||
3159 | at compile time. Now it correctly matches against C<$_> [perl #20444]. | |
5076a392 FC |
3160 | |
3161 | =item * | |
3162 | ||
e8e35311 FC |
3163 | Parsing Perl code (either with string C<eval> or by loading modules) from |
3164 | within a C<UNITCHECK> block no longer causes the interpreter to crash | |
3165 | [perl #70614]. | |
5076a392 FC |
3166 | |
3167 | =item * | |
3168 | ||
b2c076b5 FC |
3169 | String evals no longer fail after 2 billion scopes have been |
3170 | compiled [perl #83364]. | |
3171 | ||
3172 | =item * | |
3173 | ||
e8e35311 FC |
3174 | The parser no longer hangs when encountering certain Unicode characters, |
3175 | such as U+387 [perl #74022]. | |
5076a392 FC |
3176 | |
3177 | =item * | |
3178 | ||
b2c076b5 FC |
3179 | Several contexts no longer allow a Unicode character to begin a word |
3180 | that should never begin words, for an example an accent that must follow | |
3181 | another character previously could precede all other characters. | |
5076a392 FC |
3182 | |
3183 | =item * | |
3184 | ||
e8e35311 FC |
3185 | Defining a constant with the same name as one of perl's special blocks |
3186 | (e.g., INIT) stopped working in 5.12.0, but has now been fixed | |
3187 | [perl #78634]. | |
5076a392 FC |
3188 | |
3189 | =item * | |
3190 | ||
e8e35311 FC |
3191 | A reference to a literal value used as a hash key (C<$hash{\"foo"}>) used |
3192 | to be stringified, even if the hash was tied [perl #79178]. | |
5076a392 FC |
3193 | |
3194 | =item * | |
3195 | ||
e8e35311 FC |
3196 | A closure containing an C<if> statement followed by a constant or variable |
3197 | is no longer treated as a constant [perl #63540]. | |
5076a392 FC |
3198 | |
3199 | =item * | |
3200 | ||
e8e35311 FC |
3201 | C<state> can now be used with attributes. It used to mean the same thing as |
3202 | C<my> if attributes were present [perl #68658]. | |
5076a392 FC |
3203 | |
3204 | =item * | |
3205 | ||
e8e35311 FC |
3206 | Expressions like C<< @$a > 3 >> no longer cause C<$a> to be mentioned in |
3207 | the "Use of uninitialized value in numeric gt" warning when C<$a> is | |
3208 | undefined (since it is not part of the C<E<gt>> expression, but the operand | |
3209 | of the C<@>) [perl #72090]. | |
5076a392 FC |
3210 | |
3211 | =item * | |
3212 | ||
e8e35311 FC |
3213 | Accessing an element of a package array with a hard-coded number (as |
3214 | opposed to an arbitrary expression) would crash if the array did not exist. | |
3215 | Usually the array would be autovivified during compilation, but typeglob | |
3216 | manipulation could remove it, as in these two cases which used to crash: | |
5076a392 | 3217 | |
e8e35311 FC |
3218 | *d = *a; print $d[0]; |
3219 | undef *d; print $d[0]; | |
5076a392 | 3220 | |
2c389f6c FC |
3221 | =item * |
3222 | ||
3223 | The C<-C> command line option, when used on the shebang line, can now be | |
3224 | followed by other options [perl #72434]. | |
3225 | ||
3226 | =item * | |
3227 | ||
3228 | The C<B> module was returning C<B::OP>s instead of C<B::LOGOP>s for C<entertry> [perl #80622]. | |
3229 | This was due to a bug in the perl core, not in C<B> itself. | |
3230 | ||
e8e35311 | 3231 | =back |
5076a392 | 3232 | |
e262cb24 FC |
3233 | =head2 Stashes, Globs and Method Lookup |
3234 | ||
3235 | Perl 5.10.0 introduced a new internal mechanism for caching MROs (method | |
3236 | resolution orders, or lists of parent classes; aka "isa" caches) to make | |
3237 | method lookup faster (so @ISA arrays would not have to be searched | |
3238 | repeatedly). Unfortunately, this brought with it quite a few bugs. Almost | |
3239 | all of these have been fixed now, along with a few MRO-related bugs that | |
3240 | existed before 5.10.0: | |
3241 | ||
3242 | =over | |
3243 | ||
3244 | =item * | |
3245 | ||
3246 | The following used to have erratic effects on method resolution, because | |
3247 | the "isa" caches were not reset or otherwise ended up listing the wrong | |
3248 | classes. These have been fixed. | |
3249 | ||
3250 | =over | |
3251 | ||
3252 | =item Aliasing packages by assigning to globs [perl #77358] | |
3253 | ||
3254 | =item Deleting packages by deleting their containing stash elements | |
3255 | ||
3256 | =item Undefining the glob containing a package (C<undef *Foo::>) | |
3257 | ||
3258 | =item Undefining an ISA glob (C<undef *Foo::ISA>) | |
3259 | ||
3260 | =item Deleting an ISA stash element (C<delete $Foo::{ISA}>) | |
3261 | ||
3262 | =item Sharing @ISA arrays between classes (via C<*Foo::ISA = \@Bar::ISA> or | |
3263 | C<*Foo::ISA = *Bar::ISA>) [perl #77238] | |
3264 | ||
3265 | =back | |
3266 | ||
3267 | C<undef *Foo::ISA> would even stop a new C<@Foo::ISA> array from updating | |
3268 | caches. | |
3269 | ||
3270 | =item * | |
3271 | ||
3272 | Typeglob assignments would crash if the glob's stash no longer existed, so | |
3273 | long as the glob assigned to was named 'ISA' or the glob on either side of | |
3274 | the assignment contained a subroutine. | |
3275 | ||
3276 | =item * | |
3277 | ||
3278 | C<PL_isarev>, which is accessible to Perl via C<mro::get_isarev> is now | |
3279 | updated properly when packages are deleted or removed from the C<@ISA> of | |
3280 | other classes. This allows many packages to be created and deleted without | |
3281 | causing a memory leak [perl #75176]. | |
3282 | ||
3283 | =back | |
3284 | ||
3285 | In addition, various other bugs related to typeglobs and stashes have been | |
3286 | fixed: | |
5076a392 | 3287 | |
e8e35311 | 3288 | =over |
5076a392 FC |
3289 | |
3290 | =item * | |
3291 | ||
e8e35311 | 3292 | Some work has been done on the internal pointers that link between symbol |
e262cb24 | 3293 | tables (stashes), typeglobs and subroutines. This has the effect that |
e8e35311 FC |
3294 | various edge cases related to deleting stashes or stash entries (e.g. |
3295 | <%FOO:: = ()>), and complex typeglob or code reference aliasing, will no | |
3296 | longer crash the interpreter. | |
5076a392 FC |
3297 | |
3298 | =item * | |
3299 | ||
e262cb24 FC |
3300 | Assigning a reference to a glob copy now assigns to a glob slot instead of |
3301 | overwriting the glob with a scalar [perl #1804] [perl #77508]. | |
5076a392 FC |
3302 | |
3303 | =item * | |
3304 | ||
e8e35311 FC |
3305 | A bug when replacing the glob of a loop variable within the loop has been fixed |
3306 | [perl #21469]. This | |
3307 | means the following code will no longer crash: | |
5076a392 | 3308 | |
e8e35311 FC |
3309 | for $x (...) { |
3310 | *x = *y; | |
3311 | } | |
5076a392 FC |
3312 | |
3313 | =item * | |
3314 | ||
3315 | Assigning a glob to a PVLV used to convert it to a plain string. Now it | |
3316 | works correctly, and a PVLV can hold a glob. This would happen when a | |
3317 | nonexistent hash or array element was passed to a subroutine: | |
3318 | ||
3319 | sub { $_[0] = *foo }->($hash{key}); | |
3320 | # $_[0] would have been the string "*main::foo" | |
3321 | ||
3322 | It also happened when a glob was assigned to, or returned from, an element | |
3323 | of a tied array or hash [perl #36051]. | |
3324 | ||
3325 | =item * | |
44691e6f | 3326 | |
e8e35311 | 3327 | When trying to report C<Use of uninitialized value $Foo::BAR>, crashes could |
e262cb24 FC |
3328 | occur if the glob holding the global variable in question had been detached |
3329 | from its original stash by, for example, C<delete $::{'Foo::'}>. This has | |
3330 | been fixed by disabling the reporting of variable names in those | |
e8e35311 | 3331 | cases. |
44691e6f AB |
3332 | |
3333 | =item * | |
3334 | ||
e8e35311 FC |
3335 | During the restoration of a localised typeglob on scope exit, any |
3336 | destructors called as a result would be able to see the typeglob in an | |
3337 | inconsistent state, containing freed entries, which could result in a | |
3338 | crash. This would affect code like this: | |
3339 | ||
3340 | local *@; | |
3341 | eval { die bless [] }; # puts an object in $@ | |
3342 | sub DESTROY { | |
3343 | local $@; # boom | |
3344 | } | |
3345 | ||
3346 | Now the glob entries are cleared before any destructors are called. This | |
3347 | also means that destructors can vivify entries in the glob. So perl tries | |
3348 | again and, if the entries are re-created too many times, dies with a | |
3349 | 'panic: gp_free...' error message. | |
3350 | ||
3351 | =back | |
3352 | ||
3353 | =head2 Unicode | |
3354 | ||
3355 | =over | |
44691e6f | 3356 | |
5076a392 | 3357 | =item * |
44691e6f | 3358 | |
e8e35311 FC |
3359 | What has become known as the "Unicode Bug" is mostly resolved in this release. |
3360 | Under C<use feature 'unicode_strings'>, the internal storage format of a | |
3361 | string no longer affects the external semantics. There are two known | |
3362 | exceptions. User-defined case changing functions, which are planned to | |
3363 | be deprecated in 5.14, require utf8-encoded strings to function; and the | |
3364 | character C<LATIN SMALL LETTER SHARP S> in regular expression | |
3365 | case-insensitive matching has a somewhat different set of bugs depending | |
3366 | on the internal storage format. Case-insensitive matching of all | |
3367 | characters that have multi-character matches, as this one does, is | |
3368 | problematical in Perl [perl #58182]. | |
911a3729 | 3369 | |
5076a392 | 3370 | =item * |
c8c13991 | 3371 | |
e8e35311 FC |
3372 | The handling of Unicode non-characters has changed. |
3373 | Previously they were mostly considered illegal, except that only one of | |
3374 | the 66 of them was known about in places. The Unicode standard | |
3375 | considers them legal, but forbids the "open interchange" of them. | |
3376 | This is part of the change to allow the internal use of any code point | |
3377 | (see L</Core Enhancements>). Together, these changes resolve | |
9a5a48b7 FC |
3378 | [perl #38722], [perl #51918], [perl #51936], [perl #63446]. |
3379 | ||
3380 | =item * | |
3381 | ||
3382 | Naming a deprecated character in \N{...} no longer leaks memory. | |
3383 | ||
3384 | =item * | |
3385 | ||
cdc10f43 FC |
3386 | We fixed a bug that could cause \N{} constructs followed by a single . to |
3387 | be parsed incorrectly [perl #74978] (5.12.1). | |
3388 | ||
3389 | =item * | |
3390 | ||
9a5a48b7 FC |
3391 | C<chop> now correctly handles characters above "\x{7fffffff}" |
3392 | [perl #73246]. | |
3393 | ||
3394 | =item * | |
3395 | ||
3396 | Passing to C<index> an offset beyond the end of the string when the string | |
3397 | is encoded internally in UTF8 no longer causes panics [perl #75898]. | |
3398 | ||
3399 | =item * | |
3400 | ||
3401 | C<warn()> and C<die()> now respect utf8-encoded scalars [perl #45549]. | |
c8c13991 | 3402 | |
5076a392 FC |
3403 | =item * |
3404 | ||
9a5a48b7 | 3405 | Sometimes the UTF8 length cache would not be reset on a value |
e8e35311 | 3406 | returned by substr, causing C<length(substr($uni_string,...))> to give |
9a5a48b7 FC |
3407 | wrong answers. With C<${^UTF8CACHE}> set to -1, it would produce a 'panic' |
3408 | error message, too [perl #77692]. | |
e8e35311 FC |
3409 | |
3410 | =back | |
3411 | ||
e9784f55 | 3412 | =head2 Ties, Overloading and Other Magic |
e8e35311 FC |
3413 | |
3414 | =over | |
35cdccfc | 3415 | |
5076a392 FC |
3416 | =item * |
3417 | ||
e8e35311 | 3418 | Overloading now works properly in conjunction with tied |
e9784f55 | 3419 | variables. What formerly happened was that most ops checked their |
e8e35311 FC |
3420 | arguments for overloading I<before> checking for magic, so for example |
3421 | an overloaded object returned by a tied array access would usually be | |
e9784f55 | 3422 | treated as not overloaded [RT #57012]. |
911a3729 | 3423 | |
5076a392 | 3424 | =item * |
58f55cb3 | 3425 | |
e9784f55 FC |
3426 | Various cases of magic (e.g., tie methods) being called on tied variables |
3427 | too many or too few times have been fixed: | |
3428 | ||
3429 | =over | |
58f55cb3 | 3430 | |
5076a392 | 3431 | =item * |
6b3df227 | 3432 | |
e9784f55 | 3433 | FETCH is no longer called on tied variables in void context. |
6b3df227 | 3434 | |
5076a392 | 3435 | =item * |
c9989a74 | 3436 | |
e9784f55 | 3437 | C<$tied-E<gt>()> did not always call FETCH [perl #8438]. |
c9989a74 | 3438 | |
5076a392 FC |
3439 | =item * |
3440 | ||
e9784f55 FC |
3441 | Filetest operators and C<y///> and C<tr///> were calling FETCH too |
3442 | many times. | |
b7188eb5 FC |
3443 | |
3444 | =item * | |
3445 | ||
e9784f55 FC |
3446 | The C<=> operator used to ignore magic on its right-hand side if the |
3447 | scalar happened to hold a typeglob (if a typeglob was the last thing | |
3448 | returned from or assigned to a tied scalar) [perl #77498]. | |
911a3729 | 3449 | |
5076a392 | 3450 | =item * |
c8c13991 | 3451 | |
e9784f55 FC |
3452 | Dereference operators used to ignore magic if the argument was a |
3453 | reference already (e.g., from a previous FETCH) [perl #72144]. | |
c8c13991 | 3454 | |
e8e35311 | 3455 | =item * |
f00d3350 | 3456 | |
e9784f55 FC |
3457 | C<splice> now calls set-magic (so changes made |
3458 | by C<splice @ISA> are respected by method calls) [perl #78400]. | |
3459 | ||
d430b8e7 FC |
3460 | =item * |
3461 | ||
3462 | In-memory files created by C<open $fh, 'E<gt>' \$buffer> were not calling | |
3463 | FETCH/STORE at all [perl #43789] (5.12.2). | |
3464 | ||
e9784f55 | 3465 | =back |
c34a735e | 3466 | |
5076a392 | 3467 | =item * |
b7188eb5 | 3468 | |
e9784f55 FC |
3469 | String C<eval> now detects taintedness of overloaded or tied |
3470 | arguments [perl #75716]. | |
b7188eb5 | 3471 | |
5076a392 | 3472 | =item * |
b7188eb5 | 3473 | |
e9784f55 FC |
3474 | String C<eval> and regular expression matches against objects with string |
3475 | overloading no longer cause memory corruption or crashes [perl 77084]. | |
c34a735e | 3476 | |
05dbc6f8 KW |
3477 | =item * |
3478 | ||
e9784f55 FC |
3479 | L<readline|perlfunc/"readline EXPR"> now honors C<< <> >> overloading on tied |
3480 | arguments. | |
7b98b857 | 3481 | |
5076a392 | 3482 | =item * |
05dbc6f8 | 3483 | |
e9784f55 FC |
3484 | C<< E<lt>exprE<gt> >> always respects overloading now if the expression is |
3485 | overloaded. | |
3486 | ||
3487 | Due to the way that 'E<lt>E<gt> as glob' was parsed differently from | |
3488 | 'E<lt>E<gt> as filehandle' from 5.6 onwards, something like C<< E<lt>$foo[0]E<gt> >> did | |
3489 | not handle overloading, even if C<$foo[0]> was an overloaded object. This | |
3490 | was contrary to the documentation for overload, and meant that C<< E<lt>E<gt> >> | |
3491 | could not be used as a general overloaded iterator operator. | |
05dbc6f8 KW |
3492 | |
3493 | =item * | |
3494 | ||
e8e35311 FC |
3495 | The fallback behaviour of overloading on binary operators was asymmetric |
3496 | [perl #71286]. | |
05dbc6f8 | 3497 | |
5076a392 | 3498 | =item * |
05dbc6f8 | 3499 | |
e9784f55 FC |
3500 | Magic applied to variables in the main package no longer affects other packages. |
3501 | See L</Magic variables outside the main package> above [perl #76138]. | |
05dbc6f8 | 3502 | |
5076a392 | 3503 | =item * |
05dbc6f8 | 3504 | |
e9784f55 FC |
3505 | Sometimes magic (ties, taintedness, etc.) attached to variables could cause |
3506 | an object to last longer than it should, or cause a crash if a tied | |
3507 | variable were freed from within a tie method. These have been fixed | |
3508 | [perl #81230]. | |
05dbc6f8 KW |
3509 | |
3510 | =item * | |
3511 | ||
e8e35311 FC |
3512 | DESTROY methods of objects implementing ties are no longer able to crash by |
3513 | accessing the tied variable through a weak reference [perl #86328]. | |
3514 | ||
2c389f6c FC |
3515 | =item * |
3516 | ||
3517 | Fixed a regression of kill() when a match variable is used for the | |
3518 | process ID to kill [perl #75812]. | |
3519 | ||
3520 | =item * | |
3521 | ||
3522 | C<$AUTOLOAD> used to remain tainted forever if it ever became tainted. Now | |
3523 | it is correctly untainted if an autoloaded method is called and the method | |
3524 | name was not tainted. | |
3525 | ||
3526 | =item * | |
3527 | ||
3528 | C<sprintf> now dies when passed a tainted scalar for the format. It did | |
3529 | already die for arbitrary expressions, but not for simple scalars | |
3530 | [perl #82250]. | |
3531 | ||
cdc10f43 FC |
3532 | =item * |
3533 | ||
3534 | utf8::is_utf8 now respects get-magic (e.g. $1) (5.12.1). | |
3535 | ||
e8e35311 FC |
3536 | =back |
3537 | ||
3538 | =head2 The Debugger | |
3539 | ||
3540 | =over | |
05dbc6f8 | 3541 | |
5076a392 | 3542 | =item * |
05dbc6f8 | 3543 | |
bdb0cce8 | 3544 | The Perl debugger now also works in taint mode [perl #76872]. |
4d56cd4f | 3545 | |
5076a392 FC |
3546 | =item * |
3547 | ||
bdb0cce8 | 3548 | Subroutine redefinition works once more in the debugger [perl #48332]. |
05dbc6f8 | 3549 | |
911a3729 FC |
3550 | =item * |
3551 | ||
e8e35311 | 3552 | When C<-d> is used on the shebang (C<#!>) line, the debugger now has access |
bdb0cce8 | 3553 | to the lines of the main program. In the past, this sometimes worked and |
e8e35311 FC |
3554 | sometimes did not, depending on what order things happened to be arranged |
3555 | in memory [perl #71806]. | |
911a3729 | 3556 | |
5076a392 | 3557 | =item * |
44691e6f | 3558 | |
bdb0cce8 | 3559 | A possible memory leak when using L<caller()|perlfunc/"caller EXPR"> to set |
d430b8e7 | 3560 | C<@DB::args> has been fixed (5.12.2). |
bdb0cce8 FC |
3561 | |
3562 | =item * | |
3563 | ||
3564 | Perl no longer stomps on $DB::single, $DB::trace and $DB::signal if they | |
3565 | already have values when $^P is assigned to [perl #72422]. | |
44691e6f | 3566 | |
5076a392 | 3567 | =item * |
44691e6f | 3568 | |
e8e35311 FC |
3569 | C<#line> directives in string evals were not properly updating the arrays |
3570 | of lines of code (C<< @{"_<..."} >>) that the debugger (or any debugging or | |
3571 | profiling module) uses. In threaded builds, they were not being updated at | |
3572 | all. In non-threaded builds, the line number was ignored, so any change to | |
3573 | the existing line number would cause the lines to be misnumbered | |
3574 | [perl #79442]. | |
3575 | ||
3576 | =back | |
3577 | ||
2c389f6c | 3578 | =head2 Threads |
e8e35311 FC |
3579 | |
3580 | =over | |
9dc513c5 | 3581 | |
5076a392 FC |
3582 | =item * |
3583 | ||
2c389f6c FC |
3584 | Perl no longer accidentally clones lexicals in scope within active stack |
3585 | frames in the parent when creating a child thread [perl #73086]. | |
44691e6f | 3586 | |
5076a392 | 3587 | =item * |
6d96b0fe | 3588 | |
e8e35311 FC |
3589 | Several memory leaks in cloning and freeing threaded Perl interpreters have been |
3590 | fixed [perl #77352]. | |
6d96b0fe | 3591 | |
5076a392 | 3592 | =item * |
6d96b0fe | 3593 | |
e8e35311 FC |
3594 | Creating a new thread when directory handles were open used to cause a |
3595 | crash, because the handles were not cloned, but simply passed to the new | |
3596 | thread, resulting in a double free. | |
3597 | ||
3598 | Now directory handles are cloned properly, on systems that have a C<fchdir> | |
3599 | function. On other systems, new threads simply do not inherit directory | |
3600 | handles from their parent threads [perl #75154]. | |
6d96b0fe | 3601 | |
5076a392 | 3602 | =item * |
b7188eb5 | 3603 | |
e8e35311 FC |
3604 | The typeglob C<*,>, which holds the scalar variable C<$,> (output field |
3605 | separator), had the wrong reference count in child threads. | |
b7188eb5 | 3606 | |
5076a392 | 3607 | =item * |
b7188eb5 | 3608 | |
e8e35311 FC |
3609 | [perl #78494] When pipes are shared between threads, the C<close> function |
3610 | (and any implicit close, such as on thread exit) no longer blocks. | |
3611 | ||
2c389f6c FC |
3612 | =item * |
3613 | ||
3614 | Perl now does a timely cleanup of SVs that are cloned into a new thread but | |
3615 | then discovered to be orphaned (i.e., their owners are I<not> cloned). This | |
3616 | eliminates several "scalars leaked" warnings when joining threads. | |
3617 | ||
e8e35311 FC |
3618 | =back |
3619 | ||
2c389f6c | 3620 | =head2 Scoping and Subroutines |
e8e35311 FC |
3621 | |
3622 | =over | |
44691e6f | 3623 | |
5076a392 | 3624 | =item * |
44691e6f | 3625 | |
2c389f6c | 3626 | Lvalue subroutines are again able to return copy-on-write scalars. This |
5a553547 | 3627 | had been broken since version 5.10.0 [perl #75656] (5.12.2). |
44691e6f | 3628 | |
5076a392 | 3629 | =item * |
44691e6f | 3630 | |
2c389f6c FC |
3631 | C<require> no longer causes C<caller> to return the wrong file name for |
3632 | the scope that called C<require> and other scopes higher up that had the | |
3633 | same file name [perl #68712]. | |
44691e6f | 3634 | |
5076a392 | 3635 | =item * |
b7188eb5 | 3636 | |
2c389f6c FC |
3637 | C<sort> with a ($$)-prototyped comparison routine used to cause the value |
3638 | of @_ to leak out of the sort. Taking a reference to @_ within the | |
3639 | sorting routine could cause a crash [perl #72334]. | |
b7188eb5 | 3640 | |
5076a392 | 3641 | =item * |
b7188eb5 | 3642 | |
2c389f6c FC |
3643 | Match variables (e.g., C<$1>) no longer persist between calls to a sort |
3644 | subroutine [perl #76026]. | |
b7188eb5 | 3645 | |
5076a392 | 3646 | =item * |
44691e6f | 3647 | |
2c389f6c FC |
3648 | Iterating with C<foreach> over an array returned by an lvalue sub now works |
3649 | [perl #23790]. | |
6c9cd4a1 | 3650 | |
5076a392 | 3651 | =item * |
6c9cd4a1 | 3652 | |
2c389f6c FC |
3653 | C<$@> is now localised during calls to C<binmode> to prevent action at a |
3654 | distance [perl #78844]. | |
44691e6f | 3655 | |
5076a392 | 3656 | =item * |
44691e6f | 3657 | |
2c389f6c FC |
3658 | Calling a closure prototype (what is passed to an attribute handler for a |
3659 | closure) now results in a "Closure prototype called" error message instead | |
3660 | of a crash [perl #68560]. | |
44691e6f | 3661 | |
5076a392 | 3662 | =item * |
44691e6f | 3663 | |
2c389f6c FC |
3664 | Mentioning a read-only lexical variable from the enclosing scope in a |
3665 | string C<eval> no longer causes the variable to become writable | |
3666 | [perl #19135]. | |
3667 | ||
3668 | =back | |
3669 | ||
3670 | =head2 Signals | |
3671 | ||
3672 | =over | |
b7188eb5 FC |
3673 | |
3674 | =item * | |
3675 | ||
2c389f6c | 3676 | Within signal handlers, C<$!> is now implicitly localized. |
b7188eb5 | 3677 | |
5076a392 | 3678 | =item * |
b7188eb5 | 3679 | |
2c389f6c FC |
3680 | CHLD signals are no longer unblocked after a signal handler is called if |
3681 | they were blocked before by C<POSIX::sigprocmask> [perl #82040]. | |
b7188eb5 | 3682 | |
5076a392 | 3683 | =item * |
b7188eb5 | 3684 | |
2c389f6c FC |
3685 | A signal handler called within a signal handler could cause leaks or |
3686 | double-frees. Now fixed. [perl #76248]. | |
b7188eb5 | 3687 | |
e8e35311 | 3688 | =back |
5076a392 | 3689 | |
2c389f6c | 3690 | =head2 Miscellaneous Memory Leaks |
e8e35311 FC |
3691 | |
3692 | =over | |
b7188eb5 FC |
3693 | |
3694 | =item * | |
3695 | ||
d430b8e7 | 3696 | Several memory leaks when loading XS modules were fixed (5.12.2). |
5076a392 FC |
3697 | |
3698 | =item * | |
3699 | ||
2c389f6c FC |
3700 | L<substr()|perlfunc/"substr EXPR,OFFSET,LENGTH,REPLACEMENT">, |
3701 | L<pos()|perlfunc/"index STR,SUBSTR,POSITION">, L<keys()|perlfunc/"keys HASH">, | |
3702 | and L<vec()|perlfunc/"vec EXPR,OFFSET,BITS"> could, when used in combination | |
3703 | with lvalues, result in leaking the scalar value they operate on, and cause its | |
3704 | destruction to happen too late. This has now been fixed. | |
5076a392 FC |
3705 | |
3706 | =item * | |
3707 | ||
2c389f6c FC |
3708 | The postincrement and postdecrement operators, C<++> and C<-->, used to cause |
3709 | leaks when being used on references. This has now been fixed. | |
5076a392 FC |
3710 | |
3711 | =item * | |
3712 | ||
2c389f6c FC |
3713 | Nested C<map> and C<grep> blocks no longer leak memory when processing |
3714 | large lists [perl #48004]. | |
5076a392 FC |
3715 | |
3716 | =item * | |
3717 | ||
d430b8e7 | 3718 | C<use I<VERSION>> and C<no I<VERSION>> no longer leak memory [perl #78436] |
2c389f6c | 3719 | [perl #69050]. |
5076a392 | 3720 | |
2c389f6c | 3721 | =item * |
5076a392 | 3722 | |
2c389f6c FC |
3723 | C<.=> followed by C<< <> >> or C<readline> would leak memory if C<$/> |
3724 | contained characters beyond the octet range and the scalar assigned to | |
3725 | happened to be encoded as UTF8 internally [perl #72246]. | |
5076a392 FC |
3726 | |
3727 | =item * | |
3728 | ||
2c389f6c | 3729 | C<eval "BEGIN{die}"> no longer leaks memory on non-threaded builds. |
5076a392 | 3730 | |
2c389f6c | 3731 | =back |
e8e35311 | 3732 | |
2c389f6c FC |
3733 | =head2 Memory Corruption and Crashes |
3734 | ||
3735 | =over | |
5076a392 FC |
3736 | |
3737 | =item * | |
3738 | ||
2c389f6c | 3739 | glob() no longer crashes when %File::Glob:: is empty and |
d430b8e7 | 3740 | CORE::GLOBAL::glob isn't present [perl #75464] (5.12.2). |
5076a392 | 3741 | |
e8e35311 FC |
3742 | =item * |
3743 | ||
2c389f6c FC |
3744 | readline() has been fixed when interrupted by signals so it no longer |
3745 | returns the "same thing" as before or random memory. | |
5076a392 FC |
3746 | |
3747 | =item * | |
3748 | ||
2c389f6c FC |
3749 | When assigning a list with duplicated keys to a hash, the assignment used to |
3750 | return garbage and/or freed values: | |
3751 | ||
3752 | @a = %h = (list with some duplicate keys); | |
3753 | ||
3754 | This has now been fixed [perl #31865]. | |
5076a392 | 3755 | |
e8e35311 | 3756 | =item * |
5076a392 | 3757 | |
e8e35311 FC |
3758 | The mechanism for freeing objects in globs used to leave dangling |
3759 | pointers to freed SVs, meaning Perl users could see corrupted state | |
3760 | during destruction. | |
5076a392 | 3761 | |
e8e35311 | 3762 | Perl now only frees the affected slots of the GV, rather than freeing |
2c389f6c | 3763 | the GV itself. This makes sure that there are no dangling refs or |
e8e35311 | 3764 | corrupted state during destruction. |
5076a392 FC |
3765 | |
3766 | =item * | |
3767 | ||
2c389f6c FC |
3768 | The interpreter no longer crashes when freeing deeply-nested arrays of |
3769 | arrays. Hashes have not been fixed yet [perl #44225]. | |
5076a392 FC |
3770 | |
3771 | =item * | |
3772 | ||
e8e35311 FC |
3773 | Concatenating long strings under C<use encoding> no longer causes perl to |
3774 | crash [perl #78674]. | |
5076a392 FC |
3775 | |
3776 | =item * | |
3777 | ||
e8e35311 FC |
3778 | Calling C<< ->import >> on a class lacking an import method could corrupt |
3779 | the stack, resulting in strange behaviour. For instance, | |
3780 | ||
3781 | push @a, "foo", $b = bar->import; | |
3782 | ||
3783 | would assign 'foo' to C<$b> [perl #63790]. | |
5076a392 FC |
3784 | |
3785 | =item * | |
3786 | ||
e8e35311 FC |
3787 | The C<recv> function could crash when called with the MSG_TRUNC flag |
3788 | [perl #75082]. | |
5076a392 FC |
3789 | |
3790 | =item * | |
3791 | ||
e8e35311 FC |
3792 | C<formline> no longer crashes when passed a tainted format picture. It also |
3793 | taints C<$^A> now if its arguments are tainted [perl #79138]. | |
5076a392 | 3794 | |
cdc10f43 FC |
3795 | =item * |
3796 | ||
3797 | A bug in how we process filetest operations could cause a segfault. | |
3798 | Filetests don't always expect an op on the stack, so we now use | |
3799 | TOPs only if we're sure that we're not stat'ing the _ filehandle. | |
3800 | This is indicated by OPf_KIDS (as checked in ck_ftst) [perl #74542] | |
3801 | (5.12.1). | |
3802 | ||
d430b8e7 FC |
3803 | =item * |
3804 | ||
3805 | C<unpack()> now handles scalar context correctly for C<%32H> and C<%32u>, | |
3806 | fixing a potential crash. C<split()> would crash because the third item | |
3807 | on the stack wasn't the regular expression it expected. C<unpack("%2H", | |
3808 | ...)> would return both the unpacked result and the checksum on the stack, | |
3809 | as would C<unpack("%2u", ...)> [perl #73814] (5.12.2). | |
3810 | ||
2c389f6c | 3811 | =back |
5076a392 | 3812 | |
2c389f6c | 3813 | =head2 Fixes to Various Perl Operators |
5076a392 | 3814 | |
2c389f6c | 3815 | =over |
5076a392 FC |
3816 | |
3817 | =item * | |
3818 | ||
2c389f6c FC |
3819 | The C<&> C<|> C<^> bitwise operators no longer coerce read-only arguments |
3820 | [perl #20661]. | |
5076a392 FC |
3821 | |
3822 | =item * | |
3823 | ||
2c389f6c FC |
3824 | Stringifying a scalar containing -0.0 no longer has the affect of turning |
3825 | false into true [perl #45133]. | |
5076a392 | 3826 | |
e8e35311 FC |
3827 | =item * |
3828 | ||
3829 | Some numeric operators were converting integers to floating point, | |
3830 | resulting in loss of precision on 64-bit platforms [perl #77456]. | |
5076a392 FC |
3831 | |
3832 | =item * | |
3833 | ||
2c389f6c FC |
3834 | C<sprintf> was ignoring locales when called with constant arguments |
3835 | [perl #78632]. | |
e8e35311 FC |
3836 | |
3837 | =item * | |
3838 | ||
2c389f6c FC |
3839 | Combining the vector (%v) flag and dynamic precision would |
3840 | cause sprintf to confuse the order of its arguments, making it treat the | |
3841 | string as the precision and vice versa [perl #83194]. | |
1e463951 | 3842 | |
c71a852f | 3843 | =back |
b7188eb5 | 3844 | |
42a91c97 FC |
3845 | =head2 Bugs Relating to the C API |
3846 | ||
3847 | =over | |
3848 | ||
3849 | =item * | |
3850 | ||
3851 | The C-level C<lex_stuff_pvn> function would sometimes cause a spurious | |
3852 | syntax error on the last line of the file if it lacked a final semicolon | |
cdc10f43 | 3853 | [perl #74006] (5.12.1). |
42a91c97 FC |
3854 | |
3855 | =item * | |
3856 | ||
3857 | The C<eval_sv> and C<eval_pv> C functions now set C<$@> correctly when | |
3858 | there is a syntax error and no C<G_KEEPERR> flag, and never set it if the | |
3859 | C<G_KEEPERR> flag is present [perl #3719]. | |
3860 | ||
3861 | =item * | |
3862 | ||
3863 | The XS multicall API no longer causes subroutines to lose reference counts | |
3864 | if called via the multicall interface from within those very subroutines. | |
3865 | This affects modules like List::Util. Calling one of its functions with an | |
3866 | active subroutine as the first argument could cause a crash [perl #78070]. | |
3867 | ||
3868 | =item * | |
3869 | ||
3870 | The C<SvPVbyte> function available to XS modules now calls magic before | |
3871 | downgrading the SV, to avoid warnings about wide characters [perl #72398]. | |
3872 | ||
3873 | =item * | |
3874 | ||
3875 | The ref types in the typemap for XS bindings now support magical variables | |
3876 | [perl #72684]. | |
3877 | ||
3878 | =item * | |
3879 | ||
3880 | C<sv_catsv_flags> no longer calls C<mg_get> on its second argument (the | |
3881 | source string) if the flags passed to it do not include SV_GMAGIC. So it | |
3882 | now matches the documentation. | |
3883 | ||
2c389f6c FC |
3884 | =item * |
3885 | ||
3886 | C<my_strftime> no longer leaks memory. This fixes a memory leak in | |
3887 | C<POSIX::strftime> [perl #73520]. | |
3888 | ||
cdc10f43 FC |
3889 | =item * |
3890 | ||
3891 | XSUB.h now correctly redefines fgets under PERL_IMPLICIT_SYS [perl #55049] | |
3892 | (5.12.1). | |
3893 | ||
3894 | =item * | |
3895 | ||
3896 | XS code using C<fputc()> or C<fputs()>: on Windows could cause an error | |
3897 | due to their arguments being swapped [perl #72704] (5.12.1). | |
3898 | ||
d430b8e7 FC |
3899 | =item * |
3900 | ||
3901 | A possible segfault in the C<T_PRTOBJ> default typemap has been fixed | |
3902 | (5.12.2). | |
3903 | ||
3904 | =item * | |
3905 | ||
3906 | A bug that could cause "Unknown error" messages when | |
3907 | C<call_sv(code, G_EVAL)> is called from an XS destructor has been fixed | |
3908 | (5.12.2). | |
3909 | ||
42a91c97 FC |
3910 | =back |
3911 | ||
c71a852f | 3912 | =head1 Known Problems |
44691e6f | 3913 | |
7d43ecd2 FC |
3914 | XXX Many of these have probably already been solved. There are also |
3915 | unresolved BBC articles linked to #77718 that are awaiting CPAN | |
3916 | releases. These may need to be listed here. | |
3917 | ||
5076a392 | 3918 | =over 4 |
994ae753 | 3919 | |
5076a392 | 3920 | =item * |
994ae753 | 3921 | |
cdc10f43 FC |
3922 | C<List::Util::first> misbehaves in the presence of a lexical C<$_> |
3923 | (typically introduced by C<my $_> or implicitly by C<given>). The variable | |
3924 | which gets set for each iteration is the package variable C<$_>, not the | |
3925 | lexical C<$_>. | |
3926 | ||
3927 | A similar issue may occur in other modules that provide functions which | |
3928 | take a block as their first argument, like | |
3929 | ||
3930 | foo { ... $_ ...} list | |
3931 | ||
3932 | See also: L<http://rt.perl.org/rt3/Public/Bug/Display.html?id=67694> | |
3933 | ||
3934 | =item * | |
3935 | ||
5076a392 FC |
3936 | readline() returns an empty string instead of undef when it is |
3937 | interrupted by a signal | |
c094a73d | 3938 | |
ca767864 JD |
3939 | =item * |
3940 | ||
5076a392 FC |
3941 | Test-Harness was updated from 3.17 to 3.21 for this release. A rewrite |
3942 | in how it handles non-Perl tests (in 3.17_01) broke argument passing to | |
3943 | non-Perl tests with L<prove> (RT #59186), and required that non-Perl | |
3944 | tests be run as C<prove ./test.sh> instead of C<prove test.sh> These | |
3945 | issues are being solved upstream, but didn't make it into this release. | |
3946 | They're expected to be fixed in time for perl v5.13.4. (RT #59457) | |
3947 | ||
3948 | =item * | |
3949 | ||
3950 | C<version> now prevents object methods from being called as class methods | |
3951 | (d808b68) | |
3952 | ||
3953 | =item * | |
3954 | ||
3955 | The changes in L<substr()|perlfunc/"substr EXPR,OFFSET,LENGTH,REPLACEMENT"> | |
3956 | broke C<HTML::Parser> <= 3.66. A fixed C<HTML::Parser> is available as versions | |
3957 | 3.67 on CPAN. | |
3958 | ||
3959 | =item * | |
3960 | ||
3961 | The changes in prototype handling break C<Switch>. A patch has been sent | |
3962 | upstream and will hopefully appear on CPAN soon. | |
3963 | ||
3964 | =item * | |
3965 | ||
3966 | The upgrade to Encode-2.40 has caused some tests in the libwww-perl distribution | |
3967 | on CPAN to fail. (Specifically, F<base/message-charset.t> tests 33-36 in version | |
3968 | 5.836 of that distribution now fail.) | |
3969 | ||
3970 | =item * | |
3971 | ||
3972 | The upgrade to ExtUtils-MakeMaker-6.57_05 has caused some tests in the | |
3973 | Module-Install distribution on CPAN to fail. (Specifically, F<02_mymeta.t> tests | |
3974 | 5 and 21, F<18_all_from.t> tests 6 and 15, F<19_authors.t> tests 5, 13, 21 and | |
3975 | 29, and F<20_authors_with_special_characters.t> tests 6, 15 and 23 in version | |
3976 | 1.00 of that distribution now fail.) | |
ca767864 | 3977 | |
c71a852f | 3978 | =back |
014fb485 | 3979 | |
5076a392 FC |
3980 | =head1 Errata |
3981 | ||
c21445df | 3982 | =head2 C<keys>, C<values> and C<each> work on arrays |
df91d470 FC |
3983 | |
3984 | You can now use the C<keys>, C<values>, C<each> builtin functions on arrays | |
3985 | (previously you could only use them on hashes). See L<perlfunc> for details. | |
3986 | This is actually a change introduced in perl 5.12.0, but it was missed from | |
3987 | that release's perldelta. | |
5076a392 | 3988 | |
c71a852f | 3989 | =head1 Obituary |
014fb485 | 3990 | |
5076a392 FC |
3991 | Randy Kobes, creator of the kobesearch alternative to search.cpan.org and |
3992 | contributor/maintainer to several core Perl toolchain modules, passed away | |
3993 | on September 18, 2010 after a battle with lung cancer. His contributions | |
3994 | to the Perl community will be missed. | |
44691e6f | 3995 | |
44691e6f AB |
3996 | =head1 Acknowledgements |
3997 | ||
c71a852f | 3998 | XXX The list of people to thank goes here. |
44691e6f AB |
3999 | |
4000 | =head1 Reporting Bugs | |
4001 | ||
4002 | If you find what you think is a bug, you might check the articles | |
4003 | recently posted to the comp.lang.perl.misc newsgroup and the perl | |
4004 | bug database at http://rt.perl.org/perlbug/ . There may also be | |
4005 | information at http://www.perl.org/ , the Perl Home Page. | |
4006 | ||
4007 | If you believe you have an unreported bug, please run the L<perlbug> | |
4008 | program included with your release. Be sure to trim your bug down | |
4009 | to a tiny but sufficient test case. Your bug report, along with the | |
4010 | output of C<perl -V>, will be sent off to perlbug@perl.org to be | |
4011 | analysed by the Perl porting team. | |
4012 | ||
4013 | If the bug you are reporting has security implications, which make it | |
4014 | inappropriate to send to a publicly archived mailing list, then please send | |
4015 | it to perl5-security-report@perl.org. This points to a closed subscription | |
4016 | unarchived mailing list, which includes all the core committers, who be able | |
4017 | to help assess the impact of issues, figure out a resolution, and help | |
4018 | co-ordinate the release of patches to mitigate or fix the problem across all | |
4019 | platforms on which Perl is supported. Please only use this address for | |
4020 | security issues in the Perl core, not for modules independently | |
4021 | distributed on CPAN. | |
4022 | ||
4023 | =head1 SEE ALSO | |
4024 | ||
4025 | The F<Changes> file for an explanation of how to view exhaustive details | |
4026 | on what changed. | |
4027 | ||
4028 | The F<INSTALL> file for how to build Perl. | |
4029 | ||
4030 | The F<README> file for general stuff. | |
4031 | ||
4032 | The F<Artistic> and F<Copying> files for copyright information. | |
4033 | ||
4034 | =cut |