From fc22b3d6507c6745911b9dfcc68f1e665ae13dbc Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Mon, 15 Apr 2024 21:43:11 +0200 Subject: Adding upstream version 4.22.0. Signed-off-by: Daniel Baumann --- upstream/mageia-cauldron/man1/perl5140delta.1 | 3862 +++++++++++++++++++++++++ 1 file changed, 3862 insertions(+) create mode 100644 upstream/mageia-cauldron/man1/perl5140delta.1 (limited to 'upstream/mageia-cauldron/man1/perl5140delta.1') diff --git a/upstream/mageia-cauldron/man1/perl5140delta.1 b/upstream/mageia-cauldron/man1/perl5140delta.1 new file mode 100644 index 00000000..73af95f8 --- /dev/null +++ b/upstream/mageia-cauldron/man1/perl5140delta.1 @@ -0,0 +1,3862 @@ +.\" -*- mode: troff; coding: utf-8 -*- +.\" Automatically generated by Pod::Man 5.01 (Pod::Simple 3.43) +.\" +.\" Standard preamble: +.\" ======================================================================== +.de Sp \" Vertical space (when we can't use .PP) +.if t .sp .5v +.if n .sp +.. +.de Vb \" Begin verbatim text +.ft CW +.nf +.ne \\$1 +.. +.de Ve \" End verbatim text +.ft R +.fi +.. +.\" \*(C` and \*(C' are quotes in nroff, nothing in troff, for use with C<>. +.ie n \{\ +. ds C` "" +. ds C' "" +'br\} +.el\{\ +. ds C` +. ds C' +'br\} +.\" +.\" Escape single quotes in literal strings from groff's Unicode transform. +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" +.\" If the F register is >0, we'll generate index entries on stderr for +.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index +.\" entries marked with X<> in POD. Of course, you'll have to process the +.\" output yourself in some meaningful fashion. +.\" +.\" Avoid warning from groff about undefined register 'F'. +.de IX +.. +.nr rF 0 +.if \n(.g .if rF .nr rF 1 +.if (\n(rF:(\n(.g==0)) \{\ +. if \nF \{\ +. de IX +. tm Index:\\$1\t\\n%\t"\\$2" +.. +. if !\nF==2 \{\ +. nr % 0 +. nr F 2 +. \} +. \} +.\} +.rr rF +.\" ======================================================================== +.\" +.IX Title "PERL5140DELTA 1" +.TH PERL5140DELTA 1 2023-11-28 "perl v5.38.2" "Perl Programmers Reference Guide" +.\" For nroff, turn off justification. Always turn off hyphenation; it makes +.\" way too many mistakes in technical documents. +.if n .ad l +.nh +.SH NAME +perl5140delta \- what is new for perl v5.14.0 +.SH DESCRIPTION +.IX Header "DESCRIPTION" +This document describes differences between the 5.12.0 release and +the 5.14.0 release. +.PP +If you are upgrading from an earlier release such as 5.10.0, first read +perl5120delta, which describes differences between 5.10.0 and +5.12.0. +.PP +Some of the bug fixes in this release have been backported to subsequent +releases of 5.12.x. Those are indicated with the 5.12.x version in +parentheses. +.SH Notice +.IX Header "Notice" +As described in perlpolicy, the release of Perl 5.14.0 marks the +official end of support for Perl 5.10. Users of Perl 5.10 or earlier +should consider upgrading to a more recent release of Perl. +.SH "Core Enhancements" +.IX Header "Core Enhancements" +.SS Unicode +.IX Subsection "Unicode" +\fIUnicode Version 6.0 is now supported (mostly)\fR +.IX Subsection "Unicode Version 6.0 is now supported (mostly)" +.PP +Perl comes with the Unicode 6.0 data base updated with +Corrigendum #8 , +with one exception noted below. +See for details on the new +release. Perl does not support any Unicode provisional properties, +including the new ones for this release. +.PP +Unicode 6.0 has chosen to use the name \f(CW\*(C`BELL\*(C'\fR for the character at U+1F514, +which is a symbol that looks like a bell, and is used in Japanese cell +phones. This conflicts with the long-standing Perl usage of having +\&\f(CW\*(C`BELL\*(C'\fR mean the ASCII \f(CW\*(C`BEL\*(C'\fR character, U+0007. In Perl 5.14, +\&\f(CW\*(C`\eN{BELL}\*(C'\fR continues to mean U+0007, but its use generates a +deprecation warning message unless such warnings are turned off. The +new name for U+0007 in Perl is \f(CW\*(C`ALERT\*(C'\fR, which corresponds nicely +with the existing shorthand sequence for it, \f(CW"\ea"\fR. \f(CW\*(C`\eN{BEL}\*(C'\fR +means U+0007, with no warning given. The character at U+1F514 has no +name in 5.14, but can be referred to by \f(CW\*(C`\eN{U+1F514}\*(C'\fR. +In Perl 5.16, \f(CW\*(C`\eN{BELL}\*(C'\fR will refer to U+1F514; all code +that uses \f(CW\*(C`\eN{BELL}\*(C'\fR should be converted to use \f(CW\*(C`\eN{ALERT}\*(C'\fR, +\&\f(CW\*(C`\eN{BEL}\*(C'\fR, or \f(CW"\ea"\fR before upgrading. +.PP +\fIFull functionality for \fR\f(CI\*(C`use feature \*(Aqunicode_strings\*(Aq\*(C'\fR +.IX Subsection "Full functionality for use feature unicode_strings" +.PP +This release provides full functionality for \f(CWuse feature +\&\*(Aqunicode_strings\*(Aq\fR. Under its scope, all string operations executed and +regular expressions compiled (even if executed outside its scope) have +Unicode semantics. See "the 'unicode_strings' feature" in feature. +However, see "Inverted bracketed character classes and multi-character folds", +below. +.PP +This feature avoids most forms of the "Unicode Bug" (see +"The "Unicode Bug"" in perlunicode for details). If there is any +possibility that your code will process Unicode strings, you are +\&\fIstrongly\fR encouraged to use this subpragma to avoid nasty surprises. +.PP +\fR\f(CI\*(C`\eN{NAME}\*(C'\fR\fI and \fR\f(CI\*(C`charnames\*(C'\fR\fI enhancements\fR +.IX Subsection "N{NAME} and charnames enhancements" +.IP \(bu 4 +\&\f(CW\*(C`\eN{\fR\f(CINAME\fR\f(CW}\*(C'\fR and \f(CW\*(C`charnames::vianame\*(C'\fR now know about the abbreviated +character names listed by Unicode, such as NBSP, SHY, LRO, ZWJ, etc.; all +customary abbreviations for the C0 and C1 control characters (such as +ACK, BEL, CAN, etc.); and a few new variants of some C1 full names that +are in common usage. +.IP \(bu 4 +Unicode has several \fInamed character sequences\fR, in which particular sequences +of code points are given names. \f(CW\*(C`\eN{\fR\f(CINAME\fR\f(CW}\*(C'\fR now recognizes these. +.IP \(bu 4 +\&\f(CW\*(C`\eN{\fR\f(CINAME\fR\f(CW}\*(C'\fR, \f(CW\*(C`charnames::vianame\*(C'\fR, and \f(CW\*(C`charnames::viacode\*(C'\fR +now know about every character in Unicode. In earlier releases of +Perl, they didn't know about the Hangul syllables nor several +CJK (Chinese/Japanese/Korean) characters. +.IP \(bu 4 +It is now possible to override Perl's abbreviations with your own custom aliases. +.IP \(bu 4 +You can now create a custom alias of the ordinal of a +character, known by \f(CW\*(C`\eN{\fR\f(CINAME\fR\f(CW}\*(C'\fR, \f(CWcharnames::vianame()\fR, and +\&\f(CWcharnames::viacode()\fR. Previously, aliases had to be to official +Unicode character names. This made it impossible to create an alias for +unnamed code points, such as those reserved for private +use. +.IP \(bu 4 +The new function \fBcharnames::string_vianame()\fR is a run-time version +of \f(CW\*(C`\eN{\fR\f(CINAME\fR\f(CW}}\*(C'\fR, returning the string of characters whose Unicode +name is its parameter. It can handle Unicode named character +sequences, whereas the pre-existing \fBcharnames::vianame()\fR cannot, +as the latter returns a single code point. +.PP +See charnames for details on all these changes. +.PP +\fINew warnings categories for problematic (non\-)Unicode code points.\fR +.IX Subsection "New warnings categories for problematic (non-)Unicode code points." +.PP +Three new warnings subcategories of "utf8" have been added. These +allow you to turn off some "utf8" warnings, while allowing +other warnings to remain on. The three categories are: +\&\f(CW\*(C`surrogate\*(C'\fR when UTF\-16 surrogates are encountered; +\&\f(CW\*(C`nonchar\*(C'\fR when Unicode non-character code points are encountered; +and \f(CW\*(C`non_unicode\*(C'\fR when code points above the legal Unicode +maximum of 0x10FFFF are encountered. +.PP +\fIAny unsigned value can be encoded as a character\fR +.IX Subsection "Any unsigned value can be encoded as a character" +.PP +With this release, Perl is adopting a model that any unsigned value +can be treated as a code point and encoded internally (as utf8) +without warnings, not just the code points that are legal in Unicode. +However, unless utf8 or the corresponding sub-category (see previous +item) of lexical warnings have been explicitly turned off, outputting +or executing a Unicode-defined operation such as upper-casing +on such a code point generates a warning. Attempting to input these +using strict rules (such as with the \f(CW:encoding(UTF\-8)\fR layer) +will continue to fail. Prior to this release, handling was +inconsistent and in places, incorrect. +.PP +Unicode non-characters, some of which previously were erroneously +considered illegal in places by Perl, contrary to the Unicode Standard, +are now always legal internally. Inputting or outputting them +works the same as with the non-legal Unicode code points, because the Unicode +Standard says they are (only) illegal for "open interchange". +.PP +\fIUnicode database files not installed\fR +.IX Subsection "Unicode database files not installed" +.PP +The Unicode database files are no longer installed with Perl. This +doesn't affect any functionality in Perl and saves significant disk +space. If you need these files, you can download them from +. +.SS "Regular Expressions" +.IX Subsection "Regular Expressions" +\fR\f(CI\*(C`(?^...)\*(C'\fR\fI construct signifies default modifiers\fR +.IX Subsection "(?^...) construct signifies default modifiers" +.PP +An ASCII caret \f(CW"^"\fR immediately following a \f(CW"(?"\fR in a regular +expression now means that the subexpression does not inherit surrounding +modifiers such as \f(CW\*(C`/i\*(C'\fR, but reverts to the Perl defaults. Any modifiers +following the caret override the defaults. +.PP +Stringification of regular expressions now uses this notation. +For example, \f(CW\*(C`qr/hlagh/i\*(C'\fR would previously be stringified as +\&\f(CW\*(C`(?i\-xsm:hlagh)\*(C'\fR, but now it's stringified as \f(CW\*(C`(?^i:hlagh)\*(C'\fR. +.PP +The main purpose of this change is to allow tests that rely on the +stringification \fInot\fR to have to change whenever new modifiers are added. +See "Extended Patterns" in perlre. +.PP +This change is likely to break code that compares stringified regular +expressions with fixed strings containing \f(CW\*(C`?\-xism\*(C'\fR. +.PP +\fR\f(CI\*(C`/d\*(C'\fR\fI, \fR\f(CI\*(C`/l\*(C'\fR\fI, \fR\f(CI\*(C`/u\*(C'\fR\fI, and \fR\f(CI\*(C`/a\*(C'\fR\fI modifiers\fR +.IX Subsection "/d, /l, /u, and /a modifiers" +.PP +Four new regular expression modifiers have been added. These are mutually +exclusive: one only can be turned on at a time. +.IP \(bu 4 +The \f(CW\*(C`/l\*(C'\fR modifier says to compile the regular expression as if it were +in the scope of \f(CW\*(C`use locale\*(C'\fR, even if it is not. +.IP \(bu 4 +The \f(CW\*(C`/u\*(C'\fR modifier says to compile the regular expression as if it were +in the scope of a \f(CW\*(C`use feature \*(Aqunicode_strings\*(Aq\*(C'\fR pragma. +.IP \(bu 4 +The \f(CW\*(C`/d\*(C'\fR (default) modifier is used to override any \f(CW\*(C`use locale\*(C'\fR and +\&\f(CW\*(C`use feature \*(Aqunicode_strings\*(Aq\*(C'\fR pragmas in effect at the time +of compiling the regular expression. +.IP \(bu 4 +The \f(CW\*(C`/a\*(C'\fR regular expression modifier restricts \f(CW\*(C`\es\*(C'\fR, \f(CW\*(C`\ed\*(C'\fR and \f(CW\*(C`\ew\*(C'\fR and +the POSIX (\f(CW\*(C`[[:posix:]]\*(C'\fR) character classes to the ASCII range. Their +complements and \f(CW\*(C`\eb\*(C'\fR and \f(CW\*(C`\eB\*(C'\fR are correspondingly +affected. Otherwise, \f(CW\*(C`/a\*(C'\fR behaves like the \f(CW\*(C`/u\*(C'\fR modifier, in that +case-insensitive matching uses Unicode semantics. +.Sp +If the \f(CW\*(C`/a\*(C'\fR modifier is repeated, then additionally in case-insensitive +matching, no ASCII character can match a non-ASCII character. +For example, +.Sp +.Vb 2 +\& "k" =~ /\eN{KELVIN SIGN}/ai +\& "\exDF" =~ /ss/ai +.Ve +.Sp +match but +.Sp +.Vb 2 +\& "k" =~ /\eN{KELVIN SIGN}/aai +\& "\exDF" =~ /ss/aai +.Ve +.Sp +do not match. +.PP +See "Modifiers" in perlre for more detail. +.PP +\fINon-destructive substitution\fR +.IX Subsection "Non-destructive substitution" +.PP +The substitution (\f(CW\*(C`s///\*(C'\fR) and transliteration +(\f(CW\*(C`y///\*(C'\fR) operators now support an \f(CW\*(C`/r\*(C'\fR option that +copies the input variable, carries out the substitution on +the copy, and returns the result. The original remains unmodified. +.PP +.Vb 3 +\& my $old = "cat"; +\& my $new = $old =~ s/cat/dog/r; +\& # $old is "cat" and $new is "dog" +.Ve +.PP +This is particularly useful with \f(CW\*(C`map\*(C'\fR. See perlop for more examples. +.PP +\fIRe-entrant regular expression engine\fR +.IX Subsection "Re-entrant regular expression engine" +.PP +It is now safe to use regular expressions within \f(CW\*(C`(?{...})\*(C'\fR and +\&\f(CW\*(C`(??{...})\*(C'\fR code blocks inside regular expressions. +.PP +These blocks are still experimental, however, and still have problems with +lexical (\f(CW\*(C`my\*(C'\fR) variables and abnormal exiting. +.PP +\fR\f(CI\*(C`use re \*(Aq/flags\*(Aq\*(C'\fR\fI\fR +.IX Subsection "use re /flags" +.PP +The \f(CW\*(C`re\*(C'\fR pragma now has the ability to turn on regular expression flags +till the end of the lexical scope: +.PP +.Vb 2 +\& use re "/x"; +\& "foo" =~ / (.+) /; # /x implied +.Ve +.PP +See "'/flags' mode" in re for details. +.PP +\fI\eo{...} for octals\fR +.IX Subsection "o{...} for octals" +.PP +There is a new octal escape sequence, \f(CW"\eo"\fR, in doublequote-like +contexts. This construct allows large octal ordinals beyond the +current max of 0777 to be represented. It also allows you to specify a +character in octal which can safely be concatenated with other regex +snippets and which won't be confused with being a backreference to +a regex capture group. See "Capture groups" in perlre. +.PP +\fIAdd \fR\f(CI\*(C`\ep{Titlecase}\*(C'\fR\fI as a synonym for \fR\f(CI\*(C`\ep{Title}\*(C'\fR +.IX Subsection "Add p{Titlecase} as a synonym for p{Title}" +.PP +This synonym is added for symmetry with the Unicode property names +\&\f(CW\*(C`\ep{Uppercase}\*(C'\fR and \f(CW\*(C`\ep{Lowercase}\*(C'\fR. +.PP +\fIRegular expression debugging output improvement\fR +.IX Subsection "Regular expression debugging output improvement" +.PP +Regular expression debugging output (turned on by \f(CW\*(C`use re \*(Aqdebug\*(Aq\*(C'\fR) now +uses hexadecimal when escaping non-ASCII characters, instead of octal. +.PP +\fIReturn value of \fR\f(CI\*(C`delete $+{...}\*(C'\fR +.IX Subsection "Return value of delete $+{...}" +.PP +Custom regular expression engines can now determine the return value of +\&\f(CW\*(C`delete\*(C'\fR on an entry of \f(CW\*(C`%+\*(C'\fR or \f(CW\*(C`%\-\*(C'\fR. +.SS "Syntactical Enhancements" +.IX Subsection "Syntactical Enhancements" +\fIArray and hash container functions accept references\fR +.IX Subsection "Array and hash container functions accept references" +.PP +\&\fBWarning:\fR This feature is considered experimental, as the exact behaviour +may change in a future version of Perl. +.PP +All builtin functions that operate directly on array or hash +containers now also accept unblessed hard references to arrays +or hashes: +.PP +.Vb 10 +\& |\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-| +\& | Traditional syntax | Terse syntax | +\& |\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-| +\& | push @$arrayref, @stuff | push $arrayref, @stuff | +\& | unshift @$arrayref, @stuff | unshift $arrayref, @stuff | +\& | pop @$arrayref | pop $arrayref | +\& | shift @$arrayref | shift $arrayref | +\& | splice @$arrayref, 0, 2 | splice $arrayref, 0, 2 | +\& | keys %$hashref | keys $hashref | +\& | keys @$arrayref | keys $arrayref | +\& | values %$hashref | values $hashref | +\& | values @$arrayref | values $arrayref | +\& | ($k,$v) = each %$hashref | ($k,$v) = each $hashref | +\& | ($k,$v) = each @$arrayref | ($k,$v) = each $arrayref | +\& |\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-| +.Ve +.PP +This allows these builtin functions to act on long dereferencing chains +or on the return value of subroutines without needing to wrap them in +\&\f(CW\*(C`@{}\*(C'\fR or \f(CW\*(C`%{}\*(C'\fR: +.PP +.Vb 2 +\& push @{$obj\->tags}, $new_tag; # old way +\& push $obj\->tags, $new_tag; # new way +\& +\& for ( keys %{$hoh\->{genres}{artists}} ) {...} # old way +\& for ( keys $hoh\->{genres}{artists} ) {...} # new way +.Ve +.PP +\fISingle term prototype\fR +.IX Subsection "Single term prototype" +.PP +The \f(CW\*(C`+\*(C'\fR prototype is a special alternative to \f(CW\*(C`$\*(C'\fR that acts like +\&\f(CW\*(C`\e[@%]\*(C'\fR when given a literal array or hash variable, but will otherwise +force scalar context on the argument. See "Prototypes" in perlsub. +.PP +\fR\f(CI\*(C`package\*(C'\fR\fI block syntax\fR +.IX Subsection "package block syntax" +.PP +A package declaration can now contain a code block, in which case the +declaration is in scope inside that block only. So \f(CW\*(C`package Foo { ... }\*(C'\fR +is precisely equivalent to \f(CW\*(C`{ package Foo; ... }\*(C'\fR. It also works with +a version number in the declaration, as in \f(CW\*(C`package Foo 1.2 { ... }\*(C'\fR, +which is its most attractive feature. See perlfunc. +.PP +\fIStatement labels can appear in more places\fR +.IX Subsection "Statement labels can appear in more places" +.PP +Statement labels can now occur before any type of statement or declaration, +such as \f(CW\*(C`package\*(C'\fR. +.PP +\fIStacked labels\fR +.IX Subsection "Stacked labels" +.PP +Multiple statement labels can now appear before a single statement. +.PP +\fIUppercase X/B allowed in hexadecimal/binary literals\fR +.IX Subsection "Uppercase X/B allowed in hexadecimal/binary literals" +.PP +Literals may now use either upper case \f(CW\*(C`0X...\*(C'\fR or \f(CW\*(C`0B...\*(C'\fR prefixes, +in addition to the already supported \f(CW\*(C`0x...\*(C'\fR and \f(CW\*(C`0b...\*(C'\fR +syntax [perl #76296]. +.PP +C, Ruby, Python, and PHP already support this syntax, and it makes +Perl more internally consistent: a round-trip with \f(CW\*(C`eval sprintf +"%#X", 0x10\*(C'\fR now returns \f(CW16\fR, just like \f(CW\*(C`eval sprintf "%#x", 0x10\*(C'\fR. +.PP +\fIOverridable tie functions\fR +.IX Subsection "Overridable tie functions" +.PP +\&\f(CW\*(C`tie\*(C'\fR, \f(CW\*(C`tied\*(C'\fR and \f(CW\*(C`untie\*(C'\fR can now be overridden [perl #75902]. +.SS "Exception Handling" +.IX Subsection "Exception Handling" +To make them more reliable and consistent, several changes have been made +to how \f(CW\*(C`die\*(C'\fR, \f(CW\*(C`warn\*(C'\fR, and \f(CW$@\fR behave. +.IP \(bu 4 +When an exception is thrown inside an \f(CW\*(C`eval\*(C'\fR, the exception is no +longer at risk of being clobbered by destructor code running during unwinding. +Previously, the exception was written into \f(CW$@\fR +early in the throwing process, and would be overwritten if \f(CW\*(C`eval\*(C'\fR was +used internally in the destructor for an object that had to be freed +while exiting from the outer \f(CW\*(C`eval\*(C'\fR. Now the exception is written +into \f(CW$@\fR last thing before exiting the outer \f(CW\*(C`eval\*(C'\fR, so the code +running immediately thereafter can rely on the value in \f(CW$@\fR correctly +corresponding to that \f(CW\*(C`eval\*(C'\fR. (\f(CW$@\fR is still also set before exiting the +\&\f(CW\*(C`eval\*(C'\fR, for the sake of destructors that rely on this.) +.Sp +Likewise, a \f(CW\*(C`local $@\*(C'\fR inside an \f(CW\*(C`eval\*(C'\fR no longer clobbers any +exception thrown in its scope. Previously, the restoration of \f(CW$@\fR upon +unwinding would overwrite any exception being thrown. Now the exception +gets to the \f(CW\*(C`eval\*(C'\fR anyway. So \f(CW\*(C`local $@\*(C'\fR is safe before a \f(CW\*(C`die\*(C'\fR. +.Sp +Exceptions thrown from object destructors no longer modify the \f(CW$@\fR +of the surrounding context. (If the surrounding context was exception +unwinding, this used to be another way to clobber the exception being +thrown.) Previously such an exception was +sometimes emitted as a warning, and then either was +string-appended to the surrounding \f(CW$@\fR or completely replaced the +surrounding \f(CW$@\fR, depending on whether that exception and the surrounding +\&\f(CW$@\fR were strings or objects. Now, an exception in this situation is +always emitted as a warning, leaving the surrounding \f(CW$@\fR untouched. +In addition to object destructors, this also affects any function call +run by XS code using the \f(CW\*(C`G_KEEPERR\*(C'\fR flag. +.IP \(bu 4 +Warnings for \f(CW\*(C`warn\*(C'\fR can now be objects in the same way as exceptions +for \f(CW\*(C`die\*(C'\fR. If an object-based warning gets the default handling +of writing to standard error, it is stringified as before with the +filename and line number appended. But a \f(CW$SIG{_\|_WARN_\|_}\fR handler now +receives an object-based warning as an object, where previously it +was passed the result of stringifying the object. +.SS "Other Enhancements" +.IX Subsection "Other Enhancements" +\fIAssignment to \fR\f(CI$0\fR\fI sets the legacy process name with \fR\f(BIprctl()\fR\fI on Linux\fR +.IX Subsection "Assignment to $0 sets the legacy process name with prctl() on Linux" +.PP +On Linux the legacy process name is now set with \fBprctl\fR\|(2), in +addition to altering the POSIX name via \f(CW\*(C`argv[0]\*(C'\fR, as Perl has done +since version 4.000. Now system utilities that read the legacy process +name such as \fIps\fR, \fItop\fR, and \fIkillall\fR recognize the name you set when +assigning to \f(CW$0\fR. The string you supply is truncated at 16 bytes; +this limitation is imposed by Linux. +.PP +\fR\f(BIsrand()\fR\fI now returns the seed\fR +.IX Subsection "srand() now returns the seed" +.PP +This allows programs that need to have repeatable results not to have to come +up with their own seed-generating mechanism. Instead, they can use \fBsrand()\fR +and stash the return value for future use. One example is a test program with +too many combinations to test comprehensively in the time available for +each run. It can test a random subset each time and, should there be a failure, +log the seed used for that run so this can later be used to produce the same results. +.PP +\fIprintf-like functions understand post\-1980 size modifiers\fR +.IX Subsection "printf-like functions understand post-1980 size modifiers" +.PP +Perl's printf and sprintf operators, and Perl's internal printf replacement +function, now understand the C90 size modifiers "hh" (\f(CW\*(C`char\*(C'\fR), "z" +(\f(CW\*(C`size_t\*(C'\fR), and "t" (\f(CW\*(C`ptrdiff_t\*(C'\fR). Also, when compiled with a C99 +compiler, Perl now understands the size modifier "j" (\f(CW\*(C`intmax_t\*(C'\fR) +(but this is not portable). +.PP +So, for example, on any modern machine, \f(CW\*(C`sprintf("%hhd", 257)\*(C'\fR returns "1". +.PP +\fINew global variable \fR\f(CI\*(C`${^GLOBAL_PHASE}\*(C'\fR +.IX Subsection "New global variable ${^GLOBAL_PHASE}" +.PP +A new global variable, \f(CW\*(C`${^GLOBAL_PHASE}\*(C'\fR, has been added to allow +introspection of the current phase of the Perl interpreter. It's explained in +detail in "${^GLOBAL_PHASE}" in perlvar and in +"BEGIN, UNITCHECK, CHECK, INIT and END" in perlmod. +.PP +\fR\f(CI\*(C`\-d:\-foo\*(C'\fR\fI calls \fR\f(CI\*(C`Devel::foo::unimport\*(C'\fR\fI\fR +.IX Subsection "-d:-foo calls Devel::foo::unimport" +.PP +The syntax \fB\-d:foo\fR was extended in 5.6.1 to make \fB\-d:foo=bar\fR +equivalent to \fB\-MDevel::foo=bar\fR, which expands +internally to \f(CW\*(C`use Devel::foo \*(Aqbar\*(Aq\*(C'\fR. +Perl now allows prefixing the module name with \fB\-\fR, with the same +semantics as \fB\-M\fR; that is: +.ie n .IP """\-d:\-foo""" 4 +.el .IP \f(CW\-d:\-foo\fR 4 +.IX Item "-d:-foo" +Equivalent to \fB\-M\-Devel::foo\fR: expands to +\&\f(CW\*(C`no Devel::foo\*(C'\fR and calls \f(CW\*(C`Devel::foo\->unimport()\*(C'\fR +if that method exists. +.ie n .IP """\-d:\-foo=bar""" 4 +.el .IP \f(CW\-d:\-foo=bar\fR 4 +.IX Item "-d:-foo=bar" +Equivalent to \fB\-M\-Devel::foo=bar\fR: expands to \f(CW\*(C`no Devel::foo \*(Aqbar\*(Aq\*(C'\fR, +and calls \f(CW\*(C`Devel::foo\->unimport("bar")\*(C'\fR if that method exists. +.PP +This is particularly useful for suppressing the default actions of a +\&\f(CW\*(C`Devel::*\*(C'\fR module's \f(CW\*(C`import\*(C'\fR method whilst still loading it for debugging. +.PP +\fIFilehandle method calls load IO::File on demand\fR +.IX Subsection "Filehandle method calls load IO::File on demand" +.PP +When a method call on a filehandle would die because the method cannot +be resolved and IO::File has not been loaded, Perl now loads IO::File +via \f(CW\*(C`require\*(C'\fR and attempts method resolution again: +.PP +.Vb 2 +\& open my $fh, ">", $file; +\& $fh\->binmode(":raw"); # loads IO::File and succeeds +.Ve +.PP +This also works for globs like \f(CW\*(C`STDOUT\*(C'\fR, \f(CW\*(C`STDERR\*(C'\fR, and \f(CW\*(C`STDIN\*(C'\fR: +.PP +.Vb 1 +\& STDOUT\->autoflush(1); +.Ve +.PP +Because this on-demand load happens only if method resolution fails, the +legacy approach of manually loading an IO::File parent class for partial +method support still works as expected: +.PP +.Vb 3 +\& use IO::Handle; +\& open my $fh, ">", $file; +\& $fh\->autoflush(1); # IO::File not loaded +.Ve +.PP +\fIImproved IPv6 support\fR +.IX Subsection "Improved IPv6 support" +.PP +The \f(CW\*(C`Socket\*(C'\fR module provides new affordances for IPv6, +including implementations of the \f(CWSocket::getaddrinfo()\fR and +\&\f(CWSocket::getnameinfo()\fR functions, along with related constants and a +handful of new functions. See Socket. +.PP +\fIDTrace probes now include package name\fR +.IX Subsection "DTrace probes now include package name" +.PP +The \f(CW\*(C`DTrace\*(C'\fR probes now include an additional argument, \f(CW\*(C`arg3\*(C'\fR, which contains +the package the subroutine being entered or left was compiled in. +.PP +For example, using the following DTrace script: +.PP +.Vb 4 +\& perl$target:::sub\-entry +\& { +\& printf("%s::%s\en", copyinstr(arg0), copyinstr(arg3)); +\& } +.Ve +.PP +and then running: +.PP +.Vb 1 +\& $ perl \-e \*(Aqsub test { }; test\*(Aq +.Ve +.PP +\&\f(CW\*(C`DTrace\*(C'\fR will print: +.PP +.Vb 1 +\& main::test +.Ve +.SS "New C APIs" +.IX Subsection "New C APIs" +See "Internal Changes". +.SH Security +.IX Header "Security" +.SS "User-defined regular expression properties" +.IX Subsection "User-defined regular expression properties" +"User-Defined Character Properties" in perlunicode documented that you can +create custom properties by defining subroutines whose names begin with +"In" or "Is". However, Perl did not actually enforce that naming +restriction, so \f(CW\*(C`\ep{foo::bar}\*(C'\fR could call \fBfoo::bar()\fR if it existed. The documented +convention is now enforced. +.PP +Also, Perl no longer allows tainted regular expressions to invoke a +user-defined property. It simply dies instead [perl #82616]. +.SH "Incompatible Changes" +.IX Header "Incompatible Changes" +Perl 5.14.0 is not binary-compatible with any previous stable release. +.PP +In addition to the sections that follow, see "C API Changes". +.SS "Regular Expressions and String Escapes" +.IX Subsection "Regular Expressions and String Escapes" +\fIInverted bracketed character classes and multi-character folds\fR +.IX Subsection "Inverted bracketed character classes and multi-character folds" +.PP +Some characters match a sequence of two or three characters in \f(CW\*(C`/i\*(C'\fR +regular expression matching under Unicode rules. One example is +\&\f(CW\*(C`LATIN SMALL LETTER SHARP S\*(C'\fR which matches the sequence \f(CW\*(C`ss\*(C'\fR. +.PP +.Vb 1 +\& \*(Aqss\*(Aq =~ /\eA[\eN{LATIN SMALL LETTER SHARP S}]\ez/i # Matches +.Ve +.PP +This, however, can lead to very counter-intuitive results, especially +when inverted. Because of this, Perl 5.14 does not use multi-character \f(CW\*(C`/i\*(C'\fR +matching in inverted character classes. +.PP +.Vb 1 +\& \*(Aqss\*(Aq =~ /\eA[^\eN{LATIN SMALL LETTER SHARP S}]+\ez/i # ??? +.Ve +.PP +This should match any sequences of characters that aren't the \f(CW\*(C`SHARP S\*(C'\fR +nor what \f(CW\*(C`SHARP S\*(C'\fR matches under \f(CW\*(C`/i\*(C'\fR. \f(CW"s"\fR isn't \f(CW\*(C`SHARP S\*(C'\fR, but +Unicode says that \f(CW"ss"\fR is what \f(CW\*(C`SHARP S\*(C'\fR matches under \f(CW\*(C`/i\*(C'\fR. So +which one "wins"? Do you fail the match because the string has \f(CW\*(C`ss\*(C'\fR or +accept it because it has an \f(CW\*(C`s\*(C'\fR followed by another \f(CW\*(C`s\*(C'\fR? +.PP +Earlier releases of Perl did allow this multi-character matching, +but due to bugs, it mostly did not work. +.PP +\fI\e400\-\e777\fR +.IX Subsection "400-777" +.PP +In certain circumstances, \f(CW\*(C`\e400\*(C'\fR\-\f(CW\*(C`\e777\*(C'\fR in regexes have behaved +differently than they behave in all other doublequote-like contexts. +Since 5.10.1, Perl has issued a deprecation warning when this happens. +Now, these literals behave the same in all doublequote-like contexts, +namely to be equivalent to \f(CW\*(C`\ex{100}\*(C'\fR\-\f(CW\*(C`\ex{1FF}\*(C'\fR, with no deprecation +warning. +.PP +Use of \f(CW\*(C`\e400\*(C'\fR\-\f(CW\*(C`\e777\*(C'\fR in the command-line option \fB\-0\fR retain their +conventional meaning. They slurp whole input files; previously, this +was documented only for \fB\-0777\fR. +.PP +Because of various ambiguities, you should use the new +\&\f(CW\*(C`\eo{...}\*(C'\fR construct to represent characters in octal instead. +.PP +\fIMost \fR\f(CI\*(C`\ep{}\*(C'\fR\fI properties are now immune to case-insensitive matching\fR +.IX Subsection "Most p{} properties are now immune to case-insensitive matching" +.PP +For most Unicode properties, it doesn't make sense to have them match +differently under \f(CW\*(C`/i\*(C'\fR case-insensitive matching. Doing so can lead +to unexpected results and potential security holes. For example +.PP +.Vb 1 +\& m/\ep{ASCII_Hex_Digit}+/i +.Ve +.PP +could previously match non-ASCII characters because of the Unicode +matching rules (although there were several bugs with this). Now +matching under \f(CW\*(C`/i\*(C'\fR gives the same results as non\-\f(CW\*(C`/i\*(C'\fR matching except +for those few properties where people have come to expect differences, +namely the ones where casing is an integral part of their meaning, such +as \f(CW\*(C`m/\ep{Uppercase}/i\*(C'\fR and \f(CW\*(C`m/\ep{Lowercase}/i\*(C'\fR, both of which match +the same code points as matched by \f(CW\*(C`m/\ep{Cased}/i\*(C'\fR. +Details are in "Unicode Properties" in perlrecharclass. +.PP +User-defined property handlers that need to match differently under \f(CW\*(C`/i\*(C'\fR +must be changed to read the new boolean parameter passed to them, which +is non-zero if case-insensitive matching is in effect and 0 otherwise. +See "User-Defined Character Properties" in perlunicode. +.PP +\fI\ep{} implies Unicode semantics\fR +.IX Subsection "p{} implies Unicode semantics" +.PP +Specifying a Unicode property in the pattern indicates +that the pattern is meant for matching according to Unicode rules, the way +\&\f(CW\*(C`\eN{\fR\f(CINAME\fR\f(CW}\*(C'\fR does. +.PP +\fIRegular expressions retain their localeness when interpolated\fR +.IX Subsection "Regular expressions retain their localeness when interpolated" +.PP +Regular expressions compiled under \f(CW\*(C`use locale\*(C'\fR now retain this when +interpolated into a new regular expression compiled outside a +\&\f(CW\*(C`use locale\*(C'\fR, and vice-versa. +.PP +Previously, one regular expression interpolated into another inherited +the localeness of the surrounding regex, losing whatever state it +originally had. This is considered a bug fix, but may trip up code that +has come to rely on the incorrect behaviour. +.PP +\fIStringification of regexes has changed\fR +.IX Subsection "Stringification of regexes has changed" +.PP +Default regular expression modifiers are now notated using +\&\f(CW\*(C`(?^...)\*(C'\fR. Code relying on the old stringification will fail. +This is so that when new modifiers are added, such code won't +have to keep changing each time this happens, because the stringification +will automatically incorporate the new modifiers. +.PP +Code that needs to work properly with both old\- and new-style regexes +can avoid the whole issue by using (for perls since 5.9.5; see re): +.PP +.Vb 2 +\& use re qw(regexp_pattern); +\& my ($pat, $mods) = regexp_pattern($re_ref); +.Ve +.PP +If the actual stringification is important or older Perls need to be +supported, you can use something like the following: +.PP +.Vb 2 +\& # Accept both old and new\-style stringification +\& my $modifiers = (qr/foobar/ =~ /\eQ(?^/) ? "^" : "\-xism"; +.Ve +.PP +And then use \f(CW$modifiers\fR instead of \f(CW\*(C`\-xism\*(C'\fR. +.PP +\fIRun-time code blocks in regular expressions inherit pragmata\fR +.IX Subsection "Run-time code blocks in regular expressions inherit pragmata" +.PP +Code blocks in regular expressions (\f(CW\*(C`(?{...})\*(C'\fR and \f(CW\*(C`(??{...})\*(C'\fR) previously +did not inherit pragmata (strict, warnings, etc.) if the regular expression +was compiled at run time as happens in cases like these two: +.PP +.Vb 3 +\& use re "eval"; +\& $foo =~ $bar; # when $bar contains (?{...}) +\& $foo =~ /$bar(?{ $finished = 1 })/; +.Ve +.PP +This bug has now been fixed, but code that relied on the buggy behaviour +may need to be fixed to account for the correct behaviour. +.SS "Stashes and Package Variables" +.IX Subsection "Stashes and Package Variables" +\fILocalised tied hashes and arrays are no longed tied\fR +.IX Subsection "Localised tied hashes and arrays are no longed tied" +.PP +In the following: +.PP +.Vb 6 +\& tie @a, ...; +\& { +\& local @a; +\& # here, @a is a now a new, untied array +\& } +\& # here, @a refers again to the old, tied array +.Ve +.PP +Earlier versions of Perl incorrectly tied the new local array. This has +now been fixed. This fix could however potentially cause a change in +behaviour of some code. +.PP +\fIStashes are now always defined\fR +.IX Subsection "Stashes are now always defined" +.PP +\&\f(CW\*(C`defined %Foo::\*(C'\fR now always returns true, even when no symbols have yet been +defined in that package. +.PP +This is a side-effect of removing a special-case kludge in the tokeniser, +added for 5.10.0, to hide side-effects of changes to the internal storage of +hashes. The fix drastically reduces hashes' memory overhead. +.PP +Calling defined on a stash has been deprecated since 5.6.0, warned on +lexicals since 5.6.0, and warned for stashes and other package +variables since 5.12.0. \f(CW\*(C`defined %hash\*(C'\fR has always exposed an +implementation detail: emptying a hash by deleting all entries from it does +not make \f(CW\*(C`defined %hash\*(C'\fR false. Hence \f(CW\*(C`defined %hash\*(C'\fR is not valid code to +determine whether an arbitrary hash is empty. Instead, use the behaviour +of an empty \f(CW%hash\fR always returning false in scalar context. +.PP +\fIClearing stashes\fR +.IX Subsection "Clearing stashes" +.PP +Stash list assignment \f(CW\*(C`%foo:: = ()\*(C'\fR used to make the stash temporarily +anonymous while it was being emptied. Consequently, any of its +subroutines referenced elsewhere would become anonymous, showing up as +"(unknown)" in \f(CW\*(C`caller\*(C'\fR. They now retain their package names such that +\&\f(CW\*(C`caller\*(C'\fR returns the original sub name if there is still a reference +to its typeglob and "foo::_\|_ANON_\|_" otherwise [perl #79208]. +.PP +\fIDereferencing typeglobs\fR +.IX Subsection "Dereferencing typeglobs" +.PP +If you assign a typeglob to a scalar variable: +.PP +.Vb 1 +\& $glob = *foo; +.Ve +.PP +the glob that is copied to \f(CW$glob\fR is marked with a special flag +indicating that the glob is just a copy. This allows subsequent +assignments to \f(CW$glob\fR to overwrite the glob. The original glob, +however, is immutable. +.PP +Some Perl operators did not distinguish between these two types of globs. +This would result in strange behaviour in edge cases: \f(CW\*(C`untie $scalar\*(C'\fR +would not untie the scalar if the last thing assigned to it was a glob +(because it treated it as \f(CW\*(C`untie *$scalar\*(C'\fR, which unties a handle). +Assignment to a glob slot (such as \f(CW\*(C`*$glob = \e@some_array\*(C'\fR) would simply +assign \f(CW\*(C`\e@some_array\*(C'\fR to \f(CW$glob\fR. +.PP +To fix this, the \f(CW\*(C`*{}\*(C'\fR operator (including its \f(CW*foo\fR and \f(CW*$foo\fR forms) +has been modified to make a new immutable glob if its operand is a glob +copy. This allows operators that make a distinction between globs and +scalars to be modified to treat only immutable globs as globs. (\f(CW\*(C`tie\*(C'\fR, +\&\f(CW\*(C`tied\*(C'\fR and \f(CW\*(C`untie\*(C'\fR have been left as they are for compatibility's sake, +but will warn. See "Deprecations".) +.PP +This causes an incompatible change in code that assigns a glob to the +return value of \f(CW\*(C`*{}\*(C'\fR when that operator was passed a glob copy. Take the +following code, for instance: +.PP +.Vb 2 +\& $glob = *foo; +\& *$glob = *bar; +.Ve +.PP +The \f(CW*$glob\fR on the second line returns a new immutable glob. That new +glob is made an alias to \f(CW*bar\fR. Then it is discarded. So the second +assignment has no effect. +.PP +See for +more detail. +.PP +\fIMagic variables outside the main package\fR +.IX Subsection "Magic variables outside the main package" +.PP +In previous versions of Perl, magic variables like \f(CW$!\fR, \f(CW%SIG\fR, etc. would +"leak" into other packages. So \f(CW%foo::SIG\fR could be used to access signals, +\&\f(CW\*(C`${"foo::!"}\*(C'\fR (with strict mode off) to access C's \f(CW\*(C`errno\*(C'\fR, etc. +.PP +This was a bug, or an "unintentional" feature, which caused various ill effects, +such as signal handlers being wiped when modules were loaded, etc. +.PP +This has been fixed (or the feature has been removed, depending on how you see +it). +.PP +\fIlocal($_) strips all magic from \fR\f(CI$_\fR +.IX Subsection "local($_) strips all magic from $_" +.PP +\&\fBlocal()\fR on scalar variables gives them a new value but keeps all +their magic intact. This has proven problematic for the default +scalar variable \f(CW$_\fR, where perlsub recommends that any subroutine +that assigns to \f(CW$_\fR should first localize it. This would throw an +exception if \f(CW$_\fR is aliased to a read-only variable, and could in general have +various unintentional side-effects. +.PP +Therefore, as an exception to the general rule, local($_) will not +only assign a new value to \f(CW$_\fR, but also remove all existing magic from +it as well. +.PP +\fIParsing of package and variable names\fR +.IX Subsection "Parsing of package and variable names" +.PP +Parsing the names of packages and package variables has changed: +multiple adjacent pairs of colons, as in \f(CW\*(C`foo::::bar\*(C'\fR, are now all +treated as package separators. +.PP +Regardless of this change, the exact parsing of package separators has +never been guaranteed and is subject to change in future Perl versions. +.SS "Changes to Syntax or to Perl Operators" +.IX Subsection "Changes to Syntax or to Perl Operators" +\fR\f(CI\*(C`given\*(C'\fR\fI return values\fR +.IX Subsection "given return values" +.PP +\&\f(CW\*(C`given\*(C'\fR blocks now return the last evaluated +expression, or an empty list if the block was exited by \f(CW\*(C`break\*(C'\fR. Thus you +can now write: +.PP +.Vb 8 +\& my $type = do { +\& given ($num) { +\& break when undef; +\& "integer" when /^[+\-]?[0\-9]+$/; +\& "float" when /^[+\-]?[0\-9]+(?:\e.[0\-9]+)?$/; +\& "unknown"; +\& } +\& }; +.Ve +.PP +See "Return value" in perlsyn for details. +.PP +\fIChange in parsing of certain prototypes\fR +.IX Subsection "Change in parsing of certain prototypes" +.PP +Functions declared with the following prototypes now behave correctly as unary +functions: +.PP +.Vb 6 +\& * +\& \e$ \e% \e@ \e* \e& +\& \e[...] +\& ;$ ;* +\& ;\e$ ;\e% etc. +\& ;\e[...] +.Ve +.PP +Due to this bug fix [perl #75904], functions +using the \f(CW\*(C`(*)\*(C'\fR, \f(CW\*(C`(;$)\*(C'\fR and \f(CW\*(C`(;*)\*(C'\fR prototypes +are parsed with higher precedence than before. So +in the following example: +.PP +.Vb 2 +\& sub foo(;$); +\& foo $a < $b; +.Ve +.PP +the second line is now parsed correctly as \f(CW\*(C`foo($a) < $b\*(C'\fR, rather than +\&\f(CW\*(C`foo($a < $b)\*(C'\fR. This happens when one of these operators is used in +an unparenthesised argument: +.PP +.Vb 10 +\& < > <= >= lt gt le ge +\& == != <=> eq ne cmp ~~ +\& & +\& | ^ +\& && +\& || // +\& .. ... +\& ?: +\& = += \-= *= etc. +\& , => +.Ve +.PP +\fISmart-matching against array slices\fR +.IX Subsection "Smart-matching against array slices" +.PP +Previously, the following code resulted in a successful match: +.PP +.Vb 3 +\& my @a = qw(a y0 z); +\& my @b = qw(a x0 z); +\& @a[0 .. $#b] ~~ @b; +.Ve +.PP +This odd behaviour has now been fixed [perl #77468]. +.PP +\fINegation treats strings differently from before\fR +.IX Subsection "Negation treats strings differently from before" +.PP +The unary negation operator, \f(CW\*(C`\-\*(C'\fR, now treats strings that look like numbers +as numbers [perl #57706]. +.PP +\fINegative zero\fR +.IX Subsection "Negative zero" +.PP +Negative zero (\-0.0), when converted to a string, now becomes "0" on all +platforms. It used to become "\-0" on some, but "0" on others. +.PP +If you still need to determine whether a zero is negative, use +\&\f(CW\*(C`sprintf("%g", $zero) =~ /^\-/\*(C'\fR or the Data::Float module on CPAN. +.PP +\fR\f(CI\*(C`:=\*(C'\fR\fI is now a syntax error\fR +.IX Subsection ":= is now a syntax error" +.PP +Previously \f(CW\*(C`my $pi := 4\*(C'\fR was exactly equivalent to \f(CW\*(C`my $pi : = 4\*(C'\fR, +with the \f(CW\*(C`:\*(C'\fR being treated as the start of an attribute list, ending before +the \f(CW\*(C`=\*(C'\fR. The use of \f(CW\*(C`:=\*(C'\fR to mean \f(CW\*(C`: =\*(C'\fR was deprecated in 5.12.0, and is +now a syntax error. This allows future use of \f(CW\*(C`:=\*(C'\fR as a new token. +.PP +Outside the core's tests for it, we find no Perl 5 code on CPAN +using this construction, so we believe that this change will have +little impact on real-world codebases. +.PP +If it is absolutely necessary to have empty attribute lists (for example, +because of a code generator), simply avoid the error by adding a space before +the \f(CW\*(C`=\*(C'\fR. +.PP +\fIChange in the parsing of identifiers\fR +.IX Subsection "Change in the parsing of identifiers" +.PP +Characters outside the Unicode "XIDStart" set are no longer allowed at the +beginning of an identifier. This means that certain accents and marks +that normally follow an alphabetic character may no longer be the first +character of an identifier. +.SS "Threads and Processes" +.IX Subsection "Threads and Processes" +\fIDirectory handles not copied to threads\fR +.IX Subsection "Directory handles not copied to threads" +.PP +On systems other than Windows that do not have +a \f(CW\*(C`fchdir\*(C'\fR function, newly-created threads no +longer inherit directory handles from their parent threads. Such programs +would usually have crashed anyway [perl #75154]. +.PP +\fR\f(CI\*(C`close\*(C'\fR\fI on shared pipes\fR +.IX Subsection "close on shared pipes" +.PP +To avoid deadlocks, the \f(CW\*(C`close\*(C'\fR function no longer waits for the +child process to exit if the underlying file descriptor is still +in use by another thread. It returns true in such cases. +.PP +\fR\f(BIfork()\fR\fI emulation will not wait for signalled children\fR +.IX Subsection "fork() emulation will not wait for signalled children" +.PP +On Windows parent processes would not terminate until all forked +children had terminated first. However, \f(CW\*(C`kill("KILL", ...)\*(C'\fR is +inherently unstable on pseudo-processes, and \f(CW\*(C`kill("TERM", ...)\*(C'\fR +might not get delivered if the child is blocked in a system call. +.PP +To avoid the deadlock and still provide a safe mechanism to terminate +the hosting process, Perl now no longer waits for children that +have been sent a SIGTERM signal. It is up to the parent process to +\&\fBwaitpid()\fR for these children if child-cleanup processing must be +allowed to finish. However, it is also then the responsibility of the +parent to avoid the deadlock by making sure the child process +can't be blocked on I/O. +.PP +See perlfork for more information about the \fBfork()\fR emulation on +Windows. +.SS Configuration +.IX Subsection "Configuration" +\fINaming fixes in Policy_sh.SH may invalidate Policy.sh\fR +.IX Subsection "Naming fixes in Policy_sh.SH may invalidate Policy.sh" +.PP +Several long-standing typos and naming confusions in \fIPolicy_sh.SH\fR have +been fixed, standardizing on the variable names used in \fIconfig.sh\fR. +.PP +This will change the behaviour of \fIPolicy.sh\fR if you happen to have been +accidentally relying on its incorrect behaviour. +.PP +\fIPerl source code is read in text mode on Windows\fR +.IX Subsection "Perl source code is read in text mode on Windows" +.PP +Perl scripts used to be read in binary mode on Windows for the benefit +of the ByteLoader module (which is no longer part of core Perl). This +had the side-effect of breaking various operations on the \f(CW\*(C`DATA\*(C'\fR filehandle, +including \fBseek()\fR/\fBtell()\fR, and even simply reading from \f(CW\*(C`DATA\*(C'\fR after filehandles +have been flushed by a call to \fBsystem()\fR, backticks, \fBfork()\fR etc. +.PP +The default build options for Windows have been changed to read Perl source +code on Windows in text mode now. ByteLoader will (hopefully) be updated on +CPAN to automatically handle this situation [perl #28106]. +.SH Deprecations +.IX Header "Deprecations" +See also "Deprecated C APIs". +.SS "Omitting a space between a regular expression and subsequent word" +.IX Subsection "Omitting a space between a regular expression and subsequent word" +Omitting the space between a regular expression operator or +its modifiers and the following word is deprecated. For +example, \f(CW\*(C`m/foo/sand $bar\*(C'\fR is for now still parsed +as \f(CW\*(C`m/foo/s and $bar\*(C'\fR, but will now issue a warning. +.ie n .SS """\ec\fIX\fP""" +.el .SS \f(CW\ec\fP\f(CIX\fP\f(CW\fP +.IX Subsection "cX" +The backslash-c construct was designed as a way of specifying +non-printable characters, but there were no restrictions (on ASCII +platforms) on what the character following the \f(CW\*(C`c\*(C'\fR could be. Now, +a deprecation warning is raised if that character isn't an ASCII character. +Also, a deprecation warning is raised for \f(CW"\ec{"\fR (which is the same +as simply saying \f(CW";"\fR). +.ie n .SS """\eb{"" and ""\eB{""" +.el .SS "\f(CW""\eb{""\fP and \f(CW""\eB{""\fP" +.IX Subsection """b{"" and ""B{""" +In regular expressions, a literal \f(CW"{"\fR immediately following a \f(CW"\eb"\fR +(not in a bracketed character class) or a \f(CW"\eB{"\fR is now deprecated +to allow for its future use by Perl itself. +.SS "Perl 4\-era .pl libraries" +.IX Subsection "Perl 4-era .pl libraries" +Perl bundles a handful of library files that predate Perl 5. +This bundling is now deprecated for most of these files, which are now +available from CPAN. The affected files now warn when run, if they were +installed as part of the core. +.PP +This is a mandatory warning, not obeying \fB\-X\fR or lexical warning bits. +The warning is modelled on that supplied by \fIdeprecate.pm\fR for +deprecated-in-core \fI.pm\fR libraries. It points to the specific CPAN +distribution that contains the \fI.pl\fR libraries. The CPAN versions, of +course, do not generate the warning. +.ie n .SS "List assignment to $[" +.el .SS "List assignment to \f(CW$[\fP" +.IX Subsection "List assignment to $[" +Assignment to \f(CW$[\fR was deprecated and started to give warnings in +Perl version 5.12.0. This version of Perl (5.14) now also emits a warning +when assigning to \f(CW$[\fR in list context. This fixes an oversight in 5.12.0. +.SS "Use of qw(...) as parentheses" +.IX Subsection "Use of qw(...) as parentheses" +Historically the parser fooled itself into thinking that \f(CWqw(...)\fR literals +were always enclosed in parentheses, and as a result you could sometimes omit +parentheses around them: +.PP +.Vb 1 +\& for $x qw(a b c) { ... } +.Ve +.PP +The parser no longer lies to itself in this way. Wrap the list literal in +parentheses like this: +.PP +.Vb 1 +\& for $x (qw(a b c)) { ... } +.Ve +.PP +This is being deprecated because the parentheses in \f(CW\*(C`for $i (1,2,3) { ... }\*(C'\fR +are not part of expression syntax. They are part of the statement +syntax, with the \f(CW\*(C`for\*(C'\fR statement wanting literal parentheses. +The synthetic parentheses that a \f(CW\*(C`qw\*(C'\fR expression acquired were only +intended to be treated as part of expression syntax. +.PP +Note that this does not change the behaviour of cases like: +.PP +.Vb 2 +\& use POSIX qw(setlocale localeconv); +\& our @EXPORT = qw(foo bar baz); +.Ve +.PP +where parentheses were never required around the expression. +.ie n .SS """\eN{BELL}""" +.el .SS \f(CW\eN{BELL}\fP +.IX Subsection "N{BELL}" +This is because Unicode is using that name for a different character. +See "Unicode Version 6.0 is now supported (mostly)" for more +explanation. +.ie n .SS """?PATTERN?""" +.el .SS \f(CW?PATTERN?\fP +.IX Subsection "?PATTERN?" +\&\f(CW\*(C`?PATTERN?\*(C'\fR (without the initial \f(CW\*(C`m\*(C'\fR) has been deprecated and now produces +a warning. This is to allow future use of \f(CW\*(C`?\*(C'\fR in new operators. +The match-once functionality is still available as \f(CW\*(C`m?PATTERN?\*(C'\fR. +.SS "Tie functions on scalars holding typeglobs" +.IX Subsection "Tie functions on scalars holding typeglobs" +Calling a tie function (\f(CW\*(C`tie\*(C'\fR, \f(CW\*(C`tied\*(C'\fR, \f(CW\*(C`untie\*(C'\fR) with a scalar argument +acts on a filehandle if the scalar happens to hold a typeglob. +.PP +This is a long-standing bug that will be removed in Perl 5.16, as +there is currently no way to tie the scalar itself when it holds +a typeglob, and no way to untie a scalar that has had a typeglob +assigned to it. +.PP +Now there is a deprecation warning whenever a tie +function is used on a handle without an explicit \f(CW\*(C`*\*(C'\fR. +.SS "User-defined case-mapping" +.IX Subsection "User-defined case-mapping" +This feature is being deprecated due to its many issues, as documented in +"User-Defined Case Mappings (for serious hackers only)" in perlunicode. +This feature will be removed in Perl 5.16. Instead use the CPAN module +Unicode::Casing, which provides improved functionality. +.SS "Deprecated modules" +.IX Subsection "Deprecated modules" +The following module will be removed from the core distribution in a +future release, and should be installed from CPAN instead. Distributions +on CPAN that require this should add it to their prerequisites. The +core version of these module now issues a deprecation warning. +.PP +If you ship a packaged version of Perl, either alone or as part of a +larger system, then you should carefully consider the repercussions of +core module deprecations. You may want to consider shipping your default +build of Perl with a package for the deprecated module that +installs into \f(CW\*(C`vendor\*(C'\fR or \f(CW\*(C`site\*(C'\fR Perl library directories. This will +inhibit the deprecation warnings. +.PP +Alternatively, you may want to consider patching \fIlib/deprecate.pm\fR +to provide deprecation warnings specific to your packaging system +or distribution of Perl, consistent with how your packaging system +or distribution manages a staged transition from a release where the +installation of a single package provides the given functionality, to +a later release where the system administrator needs to know to install +multiple packages to get that same functionality. +.PP +You can silence these deprecation warnings by installing the module +in question from CPAN. To install the latest version of it by role +rather than by name, just install \f(CW\*(C`Task::Deprecations::5_14\*(C'\fR. +.IP Devel::DProf 4 +.IX Item "Devel::DProf" +We strongly recommend that you install and use Devel::NYTProf instead +of Devel::DProf, as Devel::NYTProf offers significantly +improved profiling and reporting. +.SH "Performance Enhancements" +.IX Header "Performance Enhancements" +.SS """Safe signals"" optimisation" +.IX Subsection """Safe signals"" optimisation" +Signal dispatch has been moved from the runloop into control ops. +This should give a few percent speed increase, and eliminates nearly +all the speed penalty caused by the introduction of "safe signals" +in 5.8.0. Signals should still be dispatched within the same +statement as they were previously. If this does \fInot\fR happen, or +if you find it possible to create uninterruptible loops, this is a +bug, and reports are encouraged of how to recreate such issues. +.SS "Optimisation of \fBshift()\fP and \fBpop()\fP calls without arguments" +.IX Subsection "Optimisation of shift() and pop() calls without arguments" +Two fewer OPs are used for \fBshift()\fR and \fBpop()\fR calls with no argument (with +implicit \f(CW@_\fR). This change makes \fBshift()\fR 5% faster than \f(CW\*(C`shift @_\*(C'\fR +on non-threaded perls, and 25% faster on threaded ones. +.SS "Optimisation of regexp engine string comparison work" +.IX Subsection "Optimisation of regexp engine string comparison work" +The \f(CW\*(C`foldEQ_utf8\*(C'\fR API function for case-insensitive comparison of strings (which +is used heavily by the regexp engine) was substantially refactored and +optimised \-\- and its documentation much improved as a free bonus. +.SS "Regular expression compilation speed-up" +.IX Subsection "Regular expression compilation speed-up" +Compiling regular expressions has been made faster when upgrading +the regex to utf8 is necessary but this isn't known when the compilation begins. +.SS "String appending is 100 times faster" +.IX Subsection "String appending is 100 times faster" +When doing a lot of string appending, perls built to use the system's +\&\f(CW\*(C`malloc\*(C'\fR could end up allocating a lot more memory than needed in a +inefficient way. +.PP +\&\f(CW\*(C`sv_grow\*(C'\fR, the function used to allocate more memory if necessary +when appending to a string, has been taught to round up the memory +it requests to a certain geometric progression, making it much faster on +certain platforms and configurations. On Win32, it's now about 100 times +faster. +.ie n .SS "Eliminate ""PL_*"" accessor functions under ithreads" +.el .SS "Eliminate \f(CWPL_*\fP accessor functions under ithreads" +.IX Subsection "Eliminate PL_* accessor functions under ithreads" +When \f(CW\*(C`MULTIPLICITY\*(C'\fR was first developed, and interpreter state moved into +an interpreter struct, thread\- and interpreter-local \f(CW\*(C`PL_*\*(C'\fR variables +were defined as macros that called accessor functions (returning the +address of the value) outside the Perl core. The intent was to allow +members within the interpreter struct to change size without breaking +binary compatibility, so that bug fixes could be merged to a maintenance +branch that necessitated such a size change. This mechanism was redundant +and penalised well-behaved code. It has been removed. +.SS "Freeing weak references" +.IX Subsection "Freeing weak references" +When there are many weak references to an object, freeing that object +can under some circumstances take O(\fIN*N\fR) time to free, where +\&\fIN\fR is the number of references. The circumstances in which this can happen +have been reduced [perl #75254] +.SS "Lexical array and hash assignments" +.IX Subsection "Lexical array and hash assignments" +An earlier optimisation to speed up \f(CW\*(C`my @array = ...\*(C'\fR and +\&\f(CW\*(C`my %hash = ...\*(C'\fR assignments caused a bug and was disabled in Perl 5.12.0. +.PP +Now we have found another way to speed up these assignments [perl #82110]. +.ie n .SS "@_ uses less memory" +.el .SS "\f(CW@_\fP uses less memory" +.IX Subsection "@_ uses less memory" +Previously, \f(CW@_\fR was allocated for every subroutine at compile time with +enough space for four entries. Now this allocation is done on demand when +the subroutine is called [perl #72416]. +.SS "Size optimisations to SV and HV structures" +.IX Subsection "Size optimisations to SV and HV structures" +\&\f(CW\*(C`xhv_fill\*(C'\fR has been eliminated from \f(CW\*(C`struct xpvhv\*(C'\fR, saving 1 IV per hash and +on some systems will cause \f(CW\*(C`struct xpvhv\*(C'\fR to become cache-aligned. To avoid +this memory saving causing a slowdown elsewhere, boolean use of \f(CW\*(C`HvFILL\*(C'\fR +now calls \f(CW\*(C`HvTOTALKEYS\*(C'\fR instead (which is equivalent), so while the fill +data when actually required are now calculated on demand, cases when +this needs to be done should be rare. +.PP +The order of structure elements in SV bodies has changed. Effectively, +the NV slot has swapped location with STASH and MAGIC. As all access to +SV members is via macros, this should be completely transparent. This +change allows the space saving for PVHVs documented above, and may reduce +the memory allocation needed for PVIVs on some architectures. +.PP +\&\f(CW\*(C`XPV\*(C'\fR, \f(CW\*(C`XPVIV\*(C'\fR, and \f(CW\*(C`XPVNV\*(C'\fR now allocate only the parts of the \f(CW\*(C`SV\*(C'\fR body +they actually use, saving some space. +.PP +Scalars containing regular expressions now allocate only the part of the \f(CW\*(C`SV\*(C'\fR +body they actually use, saving some space. +.SS "Memory consumption improvements to Exporter" +.IX Subsection "Memory consumption improvements to Exporter" +The \f(CW@EXPORT_FAIL\fR AV is no longer created unless needed, hence neither is +the typeglob backing it. This saves about 200 bytes for every package that +uses Exporter but doesn't use this functionality. +.SS "Memory savings for weak references" +.IX Subsection "Memory savings for weak references" +For weak references, the common case of just a single weak reference +per referent has been optimised to reduce the storage required. In this +case it saves the equivalent of one small Perl array per referent. +.ie n .SS """%+"" and ""%\-"" use less memory" +.el .SS "\f(CW%+\fP and \f(CW%\-\fP use less memory" +.IX Subsection "%+ and %- use less memory" +The bulk of the \f(CW\*(C`Tie::Hash::NamedCapture\*(C'\fR module used to be in the Perl +core. It has now been moved to an XS module to reduce overhead for +programs that do not use \f(CW\*(C`%+\*(C'\fR or \f(CW\*(C`%\-\*(C'\fR. +.SS "Multiple small improvements to threads" +.IX Subsection "Multiple small improvements to threads" +The internal structures of threading now make fewer API calls and fewer +allocations, resulting in noticeably smaller object code. Additionally, +many thread context checks have been deferred so they're done only +as needed (although this is only possible for non-debugging builds). +.SS "Adjacent pairs of nextstate opcodes are now optimized away" +.IX Subsection "Adjacent pairs of nextstate opcodes are now optimized away" +Previously, in code such as +.PP +.Vb 1 +\& use constant DEBUG => 0; +\& +\& sub GAK { +\& warn if DEBUG; +\& print "stuff\en"; +\& } +.Ve +.PP +the ops for \f(CW\*(C`warn if DEBUG\*(C'\fR would be folded to a \f(CW\*(C`null\*(C'\fR op (\f(CW\*(C`ex\-const\*(C'\fR), but +the \f(CW\*(C`nextstate\*(C'\fR op would remain, resulting in a runtime op dispatch of +\&\f(CW\*(C`nextstate\*(C'\fR, \f(CW\*(C`nextstate\*(C'\fR, etc. +.PP +The execution of a sequence of \f(CW\*(C`nextstate\*(C'\fR ops is indistinguishable from just +the last \f(CW\*(C`nextstate\*(C'\fR op so the peephole optimizer now eliminates the first of +a pair of \f(CW\*(C`nextstate\*(C'\fR ops except when the first carries a label, since labels +must not be eliminated by the optimizer, and label usage isn't conclusively known +at compile time. +.SH "Modules and Pragmata" +.IX Header "Modules and Pragmata" +.SS "New Modules and Pragmata" +.IX Subsection "New Modules and Pragmata" +.IP \(bu 4 +CPAN::Meta::YAML 0.003 has been added as a dual-life module. It supports a +subset of YAML sufficient for reading and writing \fIMETA.yml\fR and \fIMYMETA.yml\fR files +included with CPAN distributions or generated by the module installation +toolchain. It should not be used for any other general YAML parsing or +generation task. +.IP \(bu 4 +CPAN::Meta version 2.110440 has been added as a dual-life module. It +provides a standard library to read, interpret and write CPAN distribution +metadata files (like \fIMETA.json\fR and \fIMETA.yml\fR) that describe a +distribution, its contents, and the requirements for building it and +installing it. The latest CPAN distribution metadata specification is +included as CPAN::Meta::Spec and notes on changes in the specification +over time are given in CPAN::Meta::History. +.IP \(bu 4 +HTTP::Tiny 0.012 has been added as a dual-life module. It is a very +small, simple HTTP/1.1 client designed for simple GET requests and file +mirroring. It has been added so that \fICPAN.pm\fR and CPANPLUS can +"bootstrap" HTTP access to CPAN using pure Perl without relying on external +binaries like \fBcurl\fR\|(1) or \fBwget\fR\|(1). +.IP \(bu 4 +JSON::PP 2.27105 has been added as a dual-life module to allow CPAN +clients to read \fIMETA.json\fR files in CPAN distributions. +.IP \(bu 4 +Module::Metadata 1.000004 has been added as a dual-life module. It gathers +package and POD information from Perl module files. It is a standalone module +based on Module::Build::ModuleInfo for use by other module installation +toolchain components. Module::Build::ModuleInfo has been deprecated in +favor of this module instead. +.IP \(bu 4 +Perl::OSType 1.002 has been added as a dual-life module. It maps Perl +operating system names (like "dragonfly" or "MSWin32") to more generic types +with standardized names (like "Unix" or "Windows"). It has been refactored +out of Module::Build and ExtUtils::CBuilder and consolidates such mappings into +a single location for easier maintenance. +.IP \(bu 4 +The following modules were added by the Unicode::Collate +upgrade. See below for details. +.Sp +Unicode::Collate::CJK::Big5 +.Sp +Unicode::Collate::CJK::GB2312 +.Sp +Unicode::Collate::CJK::JISX0208 +.Sp +Unicode::Collate::CJK::Korean +.Sp +Unicode::Collate::CJK::Pinyin +.Sp +Unicode::Collate::CJK::Stroke +.IP \(bu 4 +Version::Requirements version 0.101020 has been added as a dual-life +module. It provides a standard library to model and manipulates module +prerequisites and version constraints defined in CPAN::Meta::Spec. +.SS "Updated Modules and Pragma" +.IX Subsection "Updated Modules and Pragma" +.IP \(bu 4 +attributes has been upgraded from version 0.12 to 0.14. +.IP \(bu 4 +Archive::Extract has been upgraded from version 0.38 to 0.48. +.Sp +Updates since 0.38 include: a safe print method that guards +Archive::Extract from changes to \f(CW\*(C`$\e\*(C'\fR; a fix to the tests when run in core +Perl; support for TZ files; a modification for the lzma +logic to favour IO::Uncompress::Unlzma; and a fix +for an issue with NetBSD-current and its new \fBunzip\fR\|(1) +executable. +.IP \(bu 4 +Archive::Tar has been upgraded from version 1.54 to 1.76. +.Sp +Important changes since 1.54 include the following: +.RS 4 +.IP \(bu 4 +Compatibility with busybox implementations of \fBtar\fR\|(1). +.IP \(bu 4 +A fix so that \fBwrite()\fR and \fBcreate_archive()\fR +close only filehandles they themselves opened. +.IP \(bu 4 +A bug was fixed regarding the exit code of extract_archive. +.IP \(bu 4 +The \fBptar\fR\|(1) utility has a new option to allow safe creation of +tarballs without world-writable files on Windows, allowing those +archives to be uploaded to CPAN. +.IP \(bu 4 +A new \fBptargrep\fR\|(1) utility for using regular expressions against +the contents of files in a tar archive. +.IP \(bu 4 +pax extended headers are now skipped. +.RE +.RS 4 +.RE +.IP \(bu 4 +Attribute::Handlers has been upgraded from version 0.87 to 0.89. +.IP \(bu 4 +autodie has been upgraded from version 2.06_01 to 2.1001. +.IP \(bu 4 +AutoLoader has been upgraded from version 5.70 to 5.71. +.IP \(bu 4 +The B module has been upgraded from version 1.23 to 1.29. +.Sp +It no longer crashes when taking apart a \f(CW\*(C`y///\*(C'\fR containing characters +outside the octet range or compiled in a \f(CW\*(C`use utf8\*(C'\fR scope. +.Sp +The size of the shared object has been reduced by about 40%, with no +reduction in functionality. +.IP \(bu 4 +B::Concise has been upgraded from version 0.78 to 0.83. +.Sp +B::Concise marks \fBrv2sv()\fR, \fBrv2av()\fR, and \fBrv2hv()\fR ops with the new +\&\f(CW\*(C`OPpDEREF\*(C'\fR flag as "DREFed". +.Sp +It no longer produces mangled output with the \fB\-tree\fR option +[perl #80632]. +.IP \(bu 4 +B::Debug has been upgraded from version 1.12 to 1.16. +.IP \(bu 4 +B::Deparse has been upgraded from version 0.96 to 1.03. +.Sp +The deparsing of a \f(CW\*(C`nextstate\*(C'\fR op has changed when it has both a +change of package relative to the previous nextstate, or a change of +\&\f(CW\*(C`%^H\*(C'\fR or other state and a label. The label was previously emitted +first, but is now emitted last (5.12.1). +.Sp +The \f(CW\*(C`no 5.13.2\*(C'\fR or similar form is now correctly handled by B::Deparse +(5.12.3). +.Sp +B::Deparse now properly handles the code that applies a conditional +pattern match against implicit \f(CW$_\fR as it was fixed in [perl #20444]. +.Sp +Deparsing of \f(CW\*(C`our\*(C'\fR followed by a variable with funny characters +(as permitted under the \f(CW\*(C`use utf8\*(C'\fR pragma) has also been fixed [perl #33752]. +.IP \(bu 4 +B::Lint has been upgraded from version 1.11_01 to 1.13. +.IP \(bu 4 +base has been upgraded from version 2.15 to 2.16. +.IP \(bu 4 +Benchmark has been upgraded from version 1.11 to 1.12. +.IP \(bu 4 +bignum has been upgraded from version 0.23 to 0.27. +.IP \(bu 4 +Carp has been upgraded from version 1.15 to 1.20. +.Sp +Carp now detects incomplete \fBcaller()\fR +overrides and avoids using bogus \f(CW@DB::args\fR. To provide backtraces, +Carp relies on particular behaviour of the \fBcaller()\fR builtin. +Carp now detects if other code has overridden this with an +incomplete implementation, and modifies its backtrace accordingly. +Previously incomplete overrides would cause incorrect values in +backtraces (best case), or obscure fatal errors (worst case). +.Sp +This fixes certain cases of "Bizarre copy of ARRAY" caused by modules +overriding \fBcaller()\fR incorrectly (5.12.2). +.Sp +It now also avoids using regular expressions that cause Perl to +load its Unicode tables, so as to avoid the "BEGIN not safe after +errors" error that ensue if there has been a syntax error +[perl #82854]. +.IP \(bu 4 +CGI has been upgraded from version 3.48 to 3.52. +.Sp +This provides the following security fixes: the MIME boundary in +\&\fBmultipart_init()\fR is now random and the handling of +newlines embedded in header values has been improved. +.IP \(bu 4 +Compress::Raw::Bzip2 has been upgraded from version 2.024 to 2.033. +.Sp +It has been updated to use \fBbzip2\fR\|(1) 1.0.6. +.IP \(bu 4 +Compress::Raw::Zlib has been upgraded from version 2.024 to 2.033. +.IP \(bu 4 +constant has been upgraded from version 1.20 to 1.21. +.Sp +Unicode constants work once more. They have been broken since Perl 5.10.0 +[CPAN RT #67525]. +.IP \(bu 4 +CPAN has been upgraded from version 1.94_56 to 1.9600. +.Sp +Major highlights: +.RS 4 +.IP \(bu 4 +much less configuration dialog hassle +.IP \(bu 4 +support for \fIMETA/MYMETA.json\fR +.IP \(bu 4 +support for local::lib +.IP \(bu 4 +support for HTTP::Tiny to reduce the dependency on FTP sites +.IP \(bu 4 +automatic mirror selection +.IP \(bu 4 +iron out all known bugs in configure_requires +.IP \(bu 4 +support for distributions compressed with \fBbzip2\fR\|(1) +.IP \(bu 4 +allow \fIFoo/Bar.pm\fR on the command line to mean \f(CW\*(C`Foo::Bar\*(C'\fR +.RE +.RS 4 +.RE +.IP \(bu 4 +CPANPLUS has been upgraded from version 0.90 to 0.9103. +.Sp +A change to \fIcpanp-run-perl\fR +resolves RT #55964 +and RT #57106 , both +of which related to failures to install distributions that use +\&\f(CW\*(C`Module::Install::DSL\*(C'\fR (5.12.2). +.Sp +A dependency on Config was not recognised as a +core module dependency. This has been fixed. +.Sp +CPANPLUS now includes support for \fIMETA.json\fR and \fIMYMETA.json\fR. +.IP \(bu 4 +CPANPLUS::Dist::Build has been upgraded from version 0.46 to 0.54. +.IP \(bu 4 +Data::Dumper has been upgraded from version 2.125 to 2.130_02. +.Sp +The indentation used to be off when \f(CW$Data::Dumper::Terse\fR was set. This +has been fixed [perl #73604]. +.Sp +This upgrade also fixes a crash when using custom sort functions that might +cause the stack to change [perl #74170]. +.Sp +Dumpxs no longer crashes with globs returned by \f(CW*$io_ref\fR +[perl #72332]. +.IP \(bu 4 +DB_File has been upgraded from version 1.820 to 1.821. +.IP \(bu 4 +DBM_Filter has been upgraded from version 0.03 to 0.04. +.IP \(bu 4 +Devel::DProf has been upgraded from version 20080331.00 to 20110228.00. +.Sp +Merely loading Devel::DProf now no longer triggers profiling to start. +Both \f(CW\*(C`use Devel::DProf\*(C'\fR and \f(CW\*(C`perl \-d:DProf ...\*(C'\fR behave as before and start +the profiler. +.Sp +\&\fBNOTE\fR: Devel::DProf is deprecated and will be removed from a future +version of Perl. We strongly recommend that you install and use +Devel::NYTProf instead, as it offers significantly improved +profiling and reporting. +.IP \(bu 4 +Devel::Peek has been upgraded from version 1.04 to 1.07. +.IP \(bu 4 +Devel::SelfStubber has been upgraded from version 1.03 to 1.05. +.IP \(bu 4 +diagnostics has been upgraded from version 1.19 to 1.22. +.Sp +It now renders pod links slightly better, and has been taught to find +descriptions for messages that share their descriptions with other +messages. +.IP \(bu 4 +Digest::MD5 has been upgraded from version 2.39 to 2.51. +.Sp +It is now safe to use this module in combination with threads. +.IP \(bu 4 +Digest::SHA has been upgraded from version 5.47 to 5.61. +.Sp +\&\f(CW\*(C`shasum\*(C'\fR now more closely mimics \fBsha1sum\fR\|(1)/\fBmd5sum\fR\|(1). +.Sp +\&\f(CW\*(C`addfile\*(C'\fR accepts all POSIX filenames. +.Sp +New SHA\-512/224 and SHA\-512/256 transforms (ref. NIST Draft FIPS 180\-4 +[February 2011]) +.IP \(bu 4 +DirHandle has been upgraded from version 1.03 to 1.04. +.IP \(bu 4 +Dumpvalue has been upgraded from version 1.13 to 1.16. +.IP \(bu 4 +DynaLoader has been upgraded from version 1.10 to 1.13. +.Sp +It fixes a buffer overflow when passed a very long file name. +.Sp +It no longer inherits from AutoLoader; hence it no longer +produces weird error messages for unsuccessful method calls on classes that +inherit from DynaLoader [perl #84358]. +.IP \(bu 4 +Encode has been upgraded from version 2.39 to 2.42. +.Sp +Now, all 66 Unicode non-characters are treated the same way U+FFFF has +always been treated: in cases when it was disallowed, all 66 are +disallowed, and in cases where it warned, all 66 warn. +.IP \(bu 4 +Env has been upgraded from version 1.01 to 1.02. +.IP \(bu 4 +Errno has been upgraded from version 1.11 to 1.13. +.Sp +The implementation of Errno has been refactored to use about 55% less memory. +.Sp +On some platforms with unusual header files, like Win32 \fBgcc\fR\|(1) using \f(CW\*(C`mingw64\*(C'\fR +headers, some constants that weren't actually error numbers have been exposed +by Errno. This has been fixed [perl #77416]. +.IP \(bu 4 +Exporter has been upgraded from version 5.64_01 to 5.64_03. +.Sp +Exporter no longer overrides \f(CW$SIG{_\|_WARN_\|_}\fR [perl #74472] +.IP \(bu 4 +ExtUtils::CBuilder has been upgraded from version 0.27 to 0.280203. +.IP \(bu 4 +ExtUtils::Command has been upgraded from version 1.16 to 1.17. +.IP \(bu 4 +ExtUtils::Constant has been upgraded from 0.22 to 0.23. +.Sp +The AUTOLOAD helper code generated by \f(CW\*(C`ExtUtils::Constant::ProxySubs\*(C'\fR +can now \fBcroak()\fR for missing constants, or generate a complete \f(CW\*(C`AUTOLOAD\*(C'\fR +subroutine in XS, allowing simplification of many modules that use it +(Fcntl, File::Glob, GDBM_File, I18N::Langinfo, POSIX, +Socket). +.Sp +ExtUtils::Constant::ProxySubs can now optionally push the names of all +constants onto the package's \f(CW@EXPORT_OK\fR. +.IP \(bu 4 +ExtUtils::Install has been upgraded from version 1.55 to 1.56. +.IP \(bu 4 +ExtUtils::MakeMaker has been upgraded from version 6.56 to 6.57_05. +.IP \(bu 4 +ExtUtils::Manifest has been upgraded from version 1.57 to 1.58. +.IP \(bu 4 +ExtUtils::ParseXS has been upgraded from version 2.21 to 2.2210. +.IP \(bu 4 +Fcntl has been upgraded from version 1.06 to 1.11. +.IP \(bu 4 +File::Basename has been upgraded from version 2.78 to 2.82. +.IP \(bu 4 +File::CheckTree has been upgraded from version 4.4 to 4.41. +.IP \(bu 4 +File::Copy has been upgraded from version 2.17 to 2.21. +.IP \(bu 4 +File::DosGlob has been upgraded from version 1.01 to 1.04. +.Sp +It allows patterns containing literal parentheses: they no longer need to +be escaped. On Windows, it no longer +adds an extra \fI./\fR to file names +returned when the pattern is a relative glob with a drive specification, +like \fIC:*.pl\fR [perl #71712]. +.IP \(bu 4 +File::Fetch has been upgraded from version 0.24 to 0.32. +.Sp +HTTP::Lite is now supported for the "http" scheme. +.Sp +The \fBfetch\fR\|(1) utility is supported on FreeBSD, NetBSD, and +Dragonfly BSD for the \f(CW\*(C`http\*(C'\fR and \f(CW\*(C`ftp\*(C'\fR schemes. +.IP \(bu 4 +File::Find has been upgraded from version 1.15 to 1.19. +.Sp +It improves handling of backslashes on Windows, so that paths like +\&\fIC:\edir\e/file\fR are no longer generated [perl #71710]. +.IP \(bu 4 +File::Glob has been upgraded from version 1.07 to 1.12. +.IP \(bu 4 +File::Spec has been upgraded from version 3.31 to 3.33. +.Sp +Several portability fixes were made in File::Spec::VMS: a colon is now +recognized as a delimiter in native filespecs; caret-escaped delimiters are +recognized for better handling of extended filespecs; \fBcatpath()\fR returns +an empty directory rather than the current directory if the input directory +name is empty; and \fBabs2rel()\fR properly handles Unix-style input (5.12.2). +.IP \(bu 4 +File::stat has been upgraded from 1.02 to 1.05. +.Sp +The \f(CW\*(C`\-x\*(C'\fR and \f(CW\*(C`\-X\*(C'\fR file test operators now work correctly when run +by the superuser. +.IP \(bu 4 +Filter::Simple has been upgraded from version 0.84 to 0.86. +.IP \(bu 4 +GDBM_File has been upgraded from 1.10 to 1.14. +.Sp +This fixes a memory leak when DBM filters are used. +.IP \(bu 4 +Hash::Util has been upgraded from 0.07 to 0.11. +.Sp +Hash::Util no longer emits spurious "uninitialized" warnings when +recursively locking hashes that have undefined values [perl #74280]. +.IP \(bu 4 +Hash::Util::FieldHash has been upgraded from version 1.04 to 1.09. +.IP \(bu 4 +I18N::Collate has been upgraded from version 1.01 to 1.02. +.IP \(bu 4 +I18N::Langinfo has been upgraded from version 0.03 to 0.08. +.Sp +\&\fBlanginfo()\fR now defaults to using \f(CW$_\fR if there is no argument given, just +as the documentation has always claimed. +.IP \(bu 4 +I18N::LangTags has been upgraded from version 0.35 to 0.35_01. +.IP \(bu 4 +if has been upgraded from version 0.05 to 0.0601. +.IP \(bu 4 +IO has been upgraded from version 1.25_02 to 1.25_04. +.Sp +This version of IO includes a new IO::Select, which now allows IO::Handle +objects (and objects in derived classes) to be removed from an IO::Select set +even if the underlying file descriptor is closed or invalid. +.IP \(bu 4 +IPC::Cmd has been upgraded from version 0.54 to 0.70. +.Sp +Resolves an issue with splitting Win32 command lines. An argument +consisting of the single character "0" used to be omitted (CPAN RT #62961). +.IP \(bu 4 +IPC::Open3 has been upgraded from 1.05 to 1.09. +.Sp +\&\fBopen3()\fR now produces an error if the \f(CW\*(C`exec\*(C'\fR call fails, allowing this +condition to be distinguished from a child process that exited with a +non-zero status [perl #72016]. +.Sp +The internal \fBxclose()\fR routine now knows how to handle file descriptors as +documented, so duplicating \f(CW\*(C`STDIN\*(C'\fR in a child process using its file +descriptor now works [perl #76474]. +.IP \(bu 4 +IPC::SysV has been upgraded from version 2.01 to 2.03. +.IP \(bu 4 +lib has been upgraded from version 0.62 to 0.63. +.IP \(bu 4 +Locale::Maketext has been upgraded from version 1.14 to 1.19. +.Sp +Locale::Maketext now supports external caches. +.Sp +This upgrade also fixes an infinite loop in +\&\f(CWLocale::Maketext::Guts::_compile()\fR when +working with tainted values (CPAN RT #40727). +.Sp +\&\f(CW\*(C`\->maketext\*(C'\fR calls now back up and restore \f(CW$@\fR so error +messages are not suppressed (CPAN RT #34182). +.IP \(bu 4 +Log::Message has been upgraded from version 0.02 to 0.04. +.IP \(bu 4 +Log::Message::Simple has been upgraded from version 0.06 to 0.08. +.IP \(bu 4 +Math::BigInt has been upgraded from version 1.89_01 to 1.994. +.Sp +This fixes, among other things, incorrect results when computing binomial +coefficients [perl #77640]. +.Sp +It also prevents \f(CWsqrt($int)\fR from crashing under \f(CW\*(C`use bigrat\*(C'\fR. +[perl #73534]. +.IP \(bu 4 +Math::BigInt::FastCalc has been upgraded from version 0.19 to 0.28. +.IP \(bu 4 +Math::BigRat has been upgraded from version 0.24 to 0.26_02. +.IP \(bu 4 +Memoize has been upgraded from version 1.01_03 to 1.02. +.IP \(bu 4 +MIME::Base64 has been upgraded from 3.08 to 3.13. +.Sp +Includes new functions to calculate the length of encoded and decoded +base64 strings. +.Sp +Now provides \fBencode_base64url()\fR and \fBdecode_base64url()\fR functions to process +the base64 scheme for "URL applications". +.IP \(bu 4 +Module::Build has been upgraded from version 0.3603 to 0.3800. +.Sp +A notable change is the deprecation of several modules. +Module::Build::Version has been deprecated and Module::Build now +relies on the version pragma directly. Module::Build::ModuleInfo has +been deprecated in favor of a standalone copy called Module::Metadata. +Module::Build::YAML has been deprecated in favor of CPAN::Meta::YAML. +.Sp +Module::Build now also generates \fIMETA.json\fR and \fIMYMETA.json\fR files +in accordance with version 2 of the CPAN distribution metadata specification, +CPAN::Meta::Spec. The older format \fIMETA.yml\fR and \fIMYMETA.yml\fR files are +still generated. +.IP \(bu 4 +Module::CoreList has been upgraded from version 2.29 to 2.47. +.Sp +Besides listing the updated core modules of this release, it also stops listing +the \f(CW\*(C`Filespec\*(C'\fR module. That module never existed in core. The scripts +generating Module::CoreList confused it with VMS::Filespec, which actually +is a core module as of Perl 5.8.7. +.IP \(bu 4 +Module::Load has been upgraded from version 0.16 to 0.18. +.IP \(bu 4 +Module::Load::Conditional has been upgraded from version 0.34 to 0.44. +.IP \(bu 4 +The mro pragma has been upgraded from version 1.02 to 1.07. +.IP \(bu 4 +NDBM_File has been upgraded from version 1.08 to 1.12. +.Sp +This fixes a memory leak when DBM filters are used. +.IP \(bu 4 +Net::Ping has been upgraded from version 2.36 to 2.38. +.IP \(bu 4 +NEXT has been upgraded from version 0.64 to 0.65. +.IP \(bu 4 +Object::Accessor has been upgraded from version 0.36 to 0.38. +.IP \(bu 4 +ODBM_File has been upgraded from version 1.07 to 1.10. +.Sp +This fixes a memory leak when DBM filters are used. +.IP \(bu 4 +Opcode has been upgraded from version 1.15 to 1.18. +.IP \(bu 4 +The overload pragma has been upgraded from 1.10 to 1.13. +.Sp +\&\f(CW\*(C`overload::Method\*(C'\fR can now handle subroutines that are themselves blessed +into overloaded classes [perl #71998]. +.Sp +The documentation has greatly improved. See "Documentation" below. +.IP \(bu 4 +Params::Check has been upgraded from version 0.26 to 0.28. +.IP \(bu 4 +The parent pragma has been upgraded from version 0.223 to 0.225. +.IP \(bu 4 +Parse::CPAN::Meta has been upgraded from version 1.40 to 1.4401. +.Sp +The latest Parse::CPAN::Meta can now read YAML and JSON files using +CPAN::Meta::YAML and JSON::PP, which are now part of the Perl core. +.IP \(bu 4 +PerlIO::encoding has been upgraded from version 0.12 to 0.14. +.IP \(bu 4 +PerlIO::scalar has been upgraded from 0.07 to 0.11. +.Sp +A \fBread()\fR after a \fBseek()\fR beyond the end of the string no longer thinks it +has data to read [perl #78716]. +.IP \(bu 4 +PerlIO::via has been upgraded from version 0.09 to 0.11. +.IP \(bu 4 +Pod::Html has been upgraded from version 1.09 to 1.11. +.IP \(bu 4 +Pod::LaTeX has been upgraded from version 0.58 to 0.59. +.IP \(bu 4 +Pod::Perldoc has been upgraded from version 3.15_02 to 3.15_03. +.IP \(bu 4 +Pod::Simple has been upgraded from version 3.13 to 3.16. +.IP \(bu 4 +POSIX has been upgraded from 1.19 to 1.24. +.Sp +It now includes constants for POSIX signal constants. +.IP \(bu 4 +The re pragma has been upgraded from version 0.11 to 0.18. +.Sp +The \f(CW\*(C`use re \*(Aq/flags\*(Aq\*(C'\fR subpragma is new. +.Sp +The \fBregmust()\fR function used to crash when called on a regular expression +belonging to a pluggable engine. Now it croaks instead. +.Sp +\&\fBregmust()\fR no longer leaks memory. +.IP \(bu 4 +Safe has been upgraded from version 2.25 to 2.29. +.Sp +Coderefs returned by \fBreval()\fR and \fBrdo()\fR are now wrapped via +\&\fBwrap_code_refs()\fR (5.12.1). +.Sp +This fixes a possible infinite loop when looking for coderefs. +.Sp +It adds several \f(CW\*(C`version::vxs::*\*(C'\fR routines to the default share. +.IP \(bu 4 +SDBM_File has been upgraded from version 1.06 to 1.09. +.IP \(bu 4 +SelfLoader has been upgraded from 1.17 to 1.18. +.Sp +It now works in taint mode [perl #72062]. +.IP \(bu 4 +The sigtrap pragma has been upgraded from version 1.04 to 1.05. +.Sp +It no longer tries to modify read-only arguments when generating a +backtrace [perl #72340]. +.IP \(bu 4 +Socket has been upgraded from version 1.87 to 1.94. +.Sp +See "Improved IPv6 support" above. +.IP \(bu 4 +Storable has been upgraded from version 2.22 to 2.27. +.Sp +Includes performance improvement for overloaded classes. +.Sp +This adds support for serialising code references that contain UTF\-8 strings +correctly. The Storable minor version +number changed as a result, meaning that +Storable users who set \f(CW$Storable::accept_future_minor\fR to a \f(CW\*(C`FALSE\*(C'\fR value +will see errors (see "FORWARD COMPATIBILITY" in Storable for more details). +.Sp +Freezing no longer gets confused if the Perl stack gets reallocated +during freezing [perl #80074]. +.IP \(bu 4 +Sys::Hostname has been upgraded from version 1.11 to 1.16. +.IP \(bu 4 +Term::ANSIColor has been upgraded from version 2.02 to 3.00. +.IP \(bu 4 +Term::UI has been upgraded from version 0.20 to 0.26. +.IP \(bu 4 +Test::Harness has been upgraded from version 3.17 to 3.23. +.IP \(bu 4 +Test::Simple has been upgraded from version 0.94 to 0.98. +.Sp +Among many other things, subtests without a \f(CW\*(C`plan\*(C'\fR or \f(CW\*(C`no_plan\*(C'\fR now have an +implicit \fBdone_testing()\fR added to them. +.IP \(bu 4 +Thread::Semaphore has been upgraded from version 2.09 to 2.12. +.Sp +It provides two new methods that give more control over the decrementing of +semaphores: \f(CW\*(C`down_nb\*(C'\fR and \f(CW\*(C`down_force\*(C'\fR. +.IP \(bu 4 +Thread::Queue has been upgraded from version 2.11 to 2.12. +.IP \(bu 4 +The threads pragma has been upgraded from version 1.75 to 1.83. +.IP \(bu 4 +The threads::shared pragma has been upgraded from version 1.32 to 1.37. +.IP \(bu 4 +Tie::Hash has been upgraded from version 1.03 to 1.04. +.Sp +Calling \f(CW\*(C`Tie::Hash\->TIEHASH()\*(C'\fR used to loop forever. Now it \f(CW\*(C`croak\*(C'\fRs. +.IP \(bu 4 +Tie::Hash::NamedCapture has been upgraded from version 0.06 to 0.08. +.IP \(bu 4 +Tie::RefHash has been upgraded from version 1.38 to 1.39. +.IP \(bu 4 +Time::HiRes has been upgraded from version 1.9719 to 1.9721_01. +.IP \(bu 4 +Time::Local has been upgraded from version 1.1901_01 to 1.2000. +.IP \(bu 4 +Time::Piece has been upgraded from version 1.15_01 to 1.20_01. +.IP \(bu 4 +Unicode::Collate has been upgraded from version 0.52_01 to 0.73. +.Sp +Unicode::Collate has been updated to use Unicode 6.0.0. +.Sp +Unicode::Collate::Locale now supports a plethora of new locales: \fIar, be, +bg, de_\|_phonebook, hu, hy, kk, mk, nso, om, tn, vi, hr, ig, ja, ko, ru, sq, +se, sr, to, uk, zh, zh_\|_big5han, zh_\|_gb2312han, zh_\|_pinyin\fR, and \fIzh_\|_stroke\fR. +.Sp +The following modules have been added: +.Sp +Unicode::Collate::CJK::Big5 for \f(CW\*(C`zh_\|_big5han\*(C'\fR which makes +tailoring of CJK Unified Ideographs in the order of CLDR's big5han ordering. +.Sp +Unicode::Collate::CJK::GB2312 for \f(CW\*(C`zh_\|_gb2312han\*(C'\fR which makes +tailoring of CJK Unified Ideographs in the order of CLDR's gb2312han ordering. +.Sp +Unicode::Collate::CJK::JISX0208 which makes tailoring of 6355 kanji +(CJK Unified Ideographs) in the JIS X 0208 order. +.Sp +Unicode::Collate::CJK::Korean which makes tailoring of CJK Unified Ideographs +in the order of CLDR's Korean ordering. +.Sp +Unicode::Collate::CJK::Pinyin for \f(CW\*(C`zh_\|_pinyin\*(C'\fR which makes +tailoring of CJK Unified Ideographs in the order of CLDR's pinyin ordering. +.Sp +Unicode::Collate::CJK::Stroke for \f(CW\*(C`zh_\|_stroke\*(C'\fR which makes +tailoring of CJK Unified Ideographs in the order of CLDR's stroke ordering. +.Sp +This also sees the switch from using the pure-Perl version of this +module to the XS version. +.IP \(bu 4 +Unicode::Normalize has been upgraded from version 1.03 to 1.10. +.IP \(bu 4 +Unicode::UCD has been upgraded from version 0.27 to 0.32. +.Sp +A new function, \fBUnicode::UCD::num()\fR, has been added. This function +returns the numeric value of the string passed it or \f(CW\*(C`undef\*(C'\fR if the string +in its entirety has no "safe" numeric value. (For more detail, and for the +definition of "safe", see "\fBnum()\fR" in Unicode::UCD.) +.Sp +This upgrade also includes several bug fixes: +.RS 4 +.IP \fBcharinfo()\fR 4 +.IX Item "charinfo()" +.RS 4 +.PD 0 +.IP \(bu 4 +.PD +It is now updated to Unicode Version 6.0.0 with \fICorrigendum #8\fR, +excepting that, just as with Perl 5.14, the code point at U+1F514 has no name. +.IP \(bu 4 +Hangul syllable code points have the correct names, and their +decompositions are always output without requiring Lingua::KO::Hangul::Util +to be installed. +.IP \(bu 4 +CJK (Chinese-Japanese-Korean) code points U+2A700 to U+2B734 +and U+2B740 to U+2B81D are now properly handled. +.IP \(bu 4 +Numeric values are now output for those CJK code points that have them. +.IP \(bu 4 +Names output for code points with multiple aliases are now the +corrected ones. +.RE +.RS 4 +.RE +.IP \fBcharscript()\fR 4 +.IX Item "charscript()" +This now correctly returns "Unknown" instead of \f(CW\*(C`undef\*(C'\fR for the script +of a code point that hasn't been assigned another one. +.IP \fBcharblock()\fR 4 +.IX Item "charblock()" +This now correctly returns "No_Block" instead of \f(CW\*(C`undef\*(C'\fR for the block +of a code point that hasn't been assigned to another one. +.RE +.RS 4 +.RE +.IP \(bu 4 +The version pragma has been upgraded from 0.82 to 0.88. +.Sp +Because of a bug, now fixed, the \fBis_strict()\fR and \fBis_lax()\fR functions did not +work when exported (5.12.1). +.IP \(bu 4 +The warnings pragma has been upgraded from version 1.09 to 1.12. +.Sp +Calling \f(CW\*(C`use warnings\*(C'\fR without arguments is now significantly more efficient. +.IP \(bu 4 +The warnings::register pragma has been upgraded from version 1.01 to 1.02. +.Sp +It is now possible to register warning categories other than the names of +packages using warnings::register. See \fBperllexwarn\fR\|(1) for more information. +.IP \(bu 4 +XSLoader has been upgraded from version 0.10 to 0.13. +.IP \(bu 4 +VMS::DCLsym has been upgraded from version 1.03 to 1.05. +.Sp +Two bugs have been fixed [perl #84086]: +.Sp +The symbol table name was lost when tying a hash, due to a thinko in +\&\f(CW\*(C`TIEHASH\*(C'\fR. The result was that all tied hashes interacted with the +local symbol table. +.Sp +Unless a symbol table name had been explicitly specified in the call +to the constructor, querying the special key \f(CW\*(C`:LOCAL\*(C'\fR failed to +identify objects connected to the local symbol table. +.IP \(bu 4 +The Win32 module has been upgraded from version 0.39 to 0.44. +.Sp +This release has several new functions: \fBWin32::GetSystemMetrics()\fR, +\&\fBWin32::GetProductInfo()\fR, \fBWin32::GetOSDisplayName()\fR. +.Sp +The names returned by \fBWin32::GetOSName()\fR and \fBWin32::GetOSDisplayName()\fR +have been corrected. +.IP \(bu 4 +XS::Typemap has been upgraded from version 0.03 to 0.05. +.SS "Removed Modules and Pragmata" +.IX Subsection "Removed Modules and Pragmata" +As promised in Perl 5.12.0's release notes, the following modules have +been removed from the core distribution, and if needed should be installed +from CPAN instead. +.IP \(bu 4 +Class::ISA has been removed from the Perl core. Prior version was 0.36. +.IP \(bu 4 +Pod::Plainer has been removed from the Perl core. Prior version was 1.02. +.IP \(bu 4 +Switch has been removed from the Perl core. Prior version was 2.16. +.PP +The removal of Shell has been deferred until after 5.14, as the +implementation of Shell shipped with 5.12.0 did not correctly issue the +warning that it was to be removed from core. +.SH Documentation +.IX Header "Documentation" +.SS "New Documentation" +.IX Subsection "New Documentation" +\fIperlgpl\fR +.IX Subsection "perlgpl" +.PP +perlgpl has been updated to contain GPL version 1, as is included in the +\&\fIREADME\fR distributed with Perl (5.12.1). +.PP +\fIPerl 5.12.x delta files\fR +.IX Subsection "Perl 5.12.x delta files" +.PP +The perldelta files for Perl 5.12.1 to 5.12.3 have been added from the +maintenance branch: perl5121delta, perl5122delta, perl5123delta. +.PP +\fIperlpodstyle\fR +.IX Subsection "perlpodstyle" +.PP +New style guide for POD documentation, +split mostly from the NOTES section of the \fBpod2man\fR\|(1) manpage. +.PP +\fIperlsource, perlinterp, perlhacktut, and perlhacktips\fR +.IX Subsection "perlsource, perlinterp, perlhacktut, and perlhacktips" +.PP +See "perlhack and perlrepository revamp", below. +.SS "Changes to Existing Documentation" +.IX Subsection "Changes to Existing Documentation" +\fIperlmodlib is now complete\fR +.IX Subsection "perlmodlib is now complete" +.PP +The perlmodlib manpage that came with Perl 5.12.0 was missing several +modules due to a bug in the script that generates the list. This has been +fixed [perl #74332] (5.12.1). +.PP +\fIReplace incorrect tr/// table in perlebcdic\fR +.IX Subsection "Replace incorrect tr/// table in perlebcdic" +.PP +perlebcdic contains a helpful table to use in \f(CW\*(C`tr///\*(C'\fR to convert +between EBCDIC and Latin1/ASCII. The table was the inverse of the one +it describes, though the code that used the table worked correctly for +the specific example given. +.PP +The table has been corrected and the sample code changed to correspond. +.PP +The table has also been changed to hex from octal, and the recipes in the +pod have been altered to print out leading zeros to make all values +the same length. +.PP +\fITricks for user-defined casing\fR +.IX Subsection "Tricks for user-defined casing" +.PP +perlunicode now contains an explanation of how to override, mangle +and otherwise tweak the way Perl handles upper\-, lower\- and other-case +conversions on Unicode data, and how to provide scoped changes to alter +one's own code's behaviour without stomping on anybody else's. +.PP +\fIINSTALL explicitly states that Perl requires a C89 compiler\fR +.IX Subsection "INSTALL explicitly states that Perl requires a C89 compiler" +.PP +This was already true, but it's now Officially Stated For The Record +(5.12.2). +.PP +\fIExplanation of \fR\f(CI\*(C`\exHH\*(C'\fR\fI and \fR\f(CI\*(C`\eoOOO\*(C'\fR\fI escapes\fR +.IX Subsection "Explanation of xHH and oOOO escapes" +.PP +perlop has been updated with more detailed explanation of these two +character escapes. +.PP +\fR\f(BI\-0NNN\fR\fI switch\fR +.IX Subsection "-0NNN switch" +.PP +In perlrun, the behaviour of the \fB\-0NNN\fR switch for \fB\-0400\fR or higher +has been clarified (5.12.2). +.PP +\fIMaintenance policy\fR +.IX Subsection "Maintenance policy" +.PP +perlpolicy now contains the policy on what patches are acceptable for +maintenance branches (5.12.1). +.PP +\fIDeprecation policy\fR +.IX Subsection "Deprecation policy" +.PP +perlpolicy now contains the policy on compatibility and deprecation +along with definitions of terms like "deprecation" (5.12.2). +.PP +\fINew descriptions in perldiag\fR +.IX Subsection "New descriptions in perldiag" +.PP +The following existing diagnostics are now documented: +.IP \(bu 4 +Ambiguous use of \f(CW%c\fR resolved as operator \f(CW%c\fR +.IP \(bu 4 +Ambiguous use of \f(CW%c\fR{%s} resolved to \f(CW%c\fR%s +.IP \(bu 4 +Ambiguous use of \f(CW%c\fR{%s[...]} resolved to \f(CW%c\fR%s[...] +.IP \(bu 4 +Ambiguous use of \f(CW%c\fR{%s{...}} resolved to \f(CW%c\fR%s{...} +.IP \(bu 4 +Ambiguous use of \-%s resolved as \-&%s() +.IP \(bu 4 +Invalid strict version format (%s) +.IP \(bu 4 +Invalid version format (%s) +.IP \(bu 4 +Invalid version object +.PP +\fIperlbook\fR +.IX Subsection "perlbook" +.PP +perlbook has been expanded to cover many more popular books. +.PP +\fR\f(CI\*(C`SvTRUE\*(C'\fR\fI macro\fR +.IX Subsection "SvTRUE macro" +.PP +The documentation for the \f(CW\*(C`SvTRUE\*(C'\fR macro in +perlapi was simply wrong in stating that +get-magic is not processed. It has been corrected. +.PP +\fIop manipulation functions\fR +.IX Subsection "op manipulation functions" +.PP +Several API functions that process optrees have been newly documented. +.PP +\fIperlvar revamp\fR +.IX Subsection "perlvar revamp" +.PP +perlvar reorders the variables and groups them by topic. Each variable +introduced after Perl 5.000 notes the first version in which it is +available. perlvar also has a new section for deprecated variables to +note when they were removed. +.PP +\fIArray and hash slices in scalar context\fR +.IX Subsection "Array and hash slices in scalar context" +.PP +These are now documented in perldata. +.PP +\fR\f(CI\*(C`use locale\*(C'\fR\fI and formats\fR +.IX Subsection "use locale and formats" +.PP +perlform and perllocale have been corrected to state that +\&\f(CW\*(C`use locale\*(C'\fR affects formats. +.PP +\fIoverload\fR +.IX Subsection "overload" +.PP +overload's documentation has practically undergone a rewrite. It +is now much more straightforward and clear. +.PP +\fIperlhack and perlrepository revamp\fR +.IX Subsection "perlhack and perlrepository revamp" +.PP +The perlhack document is now much shorter, and focuses on the Perl 5 +development process and submitting patches to Perl. The technical content +has been moved to several new documents, perlsource, perlinterp, +perlhacktut, and perlhacktips. This technical content has +been only lightly edited. +.PP +The perlrepository document has been renamed to perlgit. This new +document is just a how-to on using git with the Perl source code. +Any other content that used to be in perlrepository has been moved +to perlhack. +.PP +\fITime::Piece examples\fR +.IX Subsection "Time::Piece examples" +.PP +Examples in perlfaq4 have been updated to show the use of +Time::Piece. +.SH Diagnostics +.IX Header "Diagnostics" +The following additions or changes have been made to diagnostic output, +including warnings and fatal error messages. For the complete list of +diagnostic messages, see perldiag. +.SS "New Diagnostics" +.IX Subsection "New Diagnostics" +\fINew Errors\fR +.IX Subsection "New Errors" +.IP "Closure prototype called" 4 +.IX Item "Closure prototype called" +This error occurs when a subroutine reference passed to an attribute +handler is called, if the subroutine is a closure [perl #68560]. +.ie n .IP "Insecure user-defined property %s" 4 +.el .IP "Insecure user-defined property \f(CW%s\fR" 4 +.IX Item "Insecure user-defined property %s" +Perl detected tainted data when trying to compile a regular +expression that contains a call to a user-defined character property +function, meaning \f(CW\*(C`\ep{IsFoo}\*(C'\fR or \f(CW\*(C`\ep{InFoo}\*(C'\fR. +See "User-Defined Character Properties" in perlunicode and perlsec. +.IP "panic: gp_free failed to free glob pointer \- something is repeatedly re-creating entries" 4 +.IX Item "panic: gp_free failed to free glob pointer - something is repeatedly re-creating entries" +This new error is triggered if a destructor called on an object in a +typeglob that is being freed creates a new typeglob entry containing an +object with a destructor that creates a new entry containing an object etc. +.IP "Parsing code internal error (%s)" 4 +.IX Item "Parsing code internal error (%s)" +This new fatal error is produced when parsing +code supplied by an extension violates the +parser's API in a detectable way. +.ie n .IP "refcnt: fd %d%s" 4 +.el .IP "refcnt: fd \f(CW%d\fR%s" 4 +.IX Item "refcnt: fd %d%s" +This new error only occurs if an internal consistency check fails when a +pipe is about to be closed. +.IP "Regexp modifier ""/%c"" may not appear twice" 4 +.IX Item "Regexp modifier ""/%c"" may not appear twice" +The regular expression pattern has one of the +mutually exclusive modifiers repeated. +.IP "Regexp modifiers ""/%c"" and ""/%c"" are mutually exclusive" 4 +.IX Item "Regexp modifiers ""/%c"" and ""/%c"" are mutually exclusive" +The regular expression pattern has more than one of the mutually +exclusive modifiers. +.ie n .IP "Using !~ with %s doesn't make sense" 4 +.el .IP "Using !~ with \f(CW%s\fR doesn't make sense" 4 +.IX Item "Using !~ with %s doesn't make sense" +This error occurs when \f(CW\*(C`!~\*(C'\fR is used with \f(CW\*(C`s///r\*(C'\fR or \f(CW\*(C`y///r\*(C'\fR. +.PP +\fINew Warnings\fR +.IX Subsection "New Warnings" +.IP """\eb{"" is deprecated; use ""\eb\e{"" instead" 4 +.IX Item """b{"" is deprecated; use ""b{"" instead" +.PD 0 +.IP """\eB{"" is deprecated; use ""\eB\e{"" instead" 4 +.IX Item """B{"" is deprecated; use ""B{"" instead" +.PD +Use of an unescaped "{" immediately following a \f(CW\*(C`\eb\*(C'\fR or \f(CW\*(C`\eB\*(C'\fR is now +deprecated in order to reserve its use for Perl itself in a future release. +.IP "Operation ""%s"" returns its argument for ..." 4 +.IX Item "Operation ""%s"" returns its argument for ..." +Performing an operation requiring Unicode semantics (such as case-folding) +on a Unicode surrogate or a non-Unicode character now triggers this +warning. +.IP "Use of qw(...) as parentheses is deprecated" 4 +.IX Item "Use of qw(...) as parentheses is deprecated" +See "Use of qw(...) as parentheses", above, for details. +.SS "Changes to Existing Diagnostics" +.IX Subsection "Changes to Existing Diagnostics" +.IP \(bu 4 +The "Variable \f(CW$foo\fR is not imported" warning that precedes a +\&\f(CW\*(C`strict \*(Aqvars\*(Aq\*(C'\fR error has now been assigned the "misc" category, so that +\&\f(CW\*(C`no warnings\*(C'\fR will suppress it [perl #73712]. +.IP \(bu 4 +\&\fBwarn()\fR and \fBdie()\fR now produce "Wide character" warnings when fed a +character outside the byte range if \f(CW\*(C`STDERR\*(C'\fR is a byte-sized handle. +.IP \(bu 4 +The "Layer does not match this perl" error message has been replaced with +these more helpful messages [perl #73754]: +.RS 4 +.IP \(bu 4 +PerlIO layer function table size (%d) does not match size expected by this +perl (%d) +.IP \(bu 4 +PerlIO layer instance size (%d) does not match size expected by this perl +(%d) +.RE +.RS 4 +.RE +.IP \(bu 4 +The "Found = in conditional" warning that is emitted when a constant is +assigned to a variable in a condition is now withheld if the constant is +actually a subroutine or one generated by \f(CW\*(C`use constant\*(C'\fR, since the value +of the constant may not be known at the time the program is written +[perl #77762]. +.IP \(bu 4 +Previously, if none of the \fBgethostbyaddr()\fR, \fBgethostbyname()\fR and +\&\fBgethostent()\fR functions were implemented on a given platform, they would +all die with the message "Unsupported socket function 'gethostent' called", +with analogous messages for getnet*() and getserv*(). This has been +corrected. +.IP \(bu 4 +The warning message about unrecognized regular expression escapes passed +through has been changed to include any literal "{" following the +two-character escape. For example, "\eq{" is now emitted instead of "\eq". +.SH "Utility Changes" +.IX Header "Utility Changes" +\fR\f(BIperlbug\fR\fI\|(1)\fR +.IX Subsection "perlbug" +.IP \(bu 4 +perlbug now looks in the EMAIL environment variable for a return address +if the REPLY-TO and REPLYTO variables are empty. +.IP \(bu 4 +perlbug did not previously generate a "From:" header, potentially +resulting in dropped mail; it now includes that header. +.IP \(bu 4 +The user's address is now used as the Return-Path. +.Sp +Many systems these days don't have a valid Internet domain name, and +perlbug@perl.org does not accept email with a return-path that does +not resolve. So the user's address is now passed to sendmail so it's +less likely to get stuck in a mail queue somewhere [perl #82996]. +.IP \(bu 4 +perlbug now always gives the reporter a chance to change the email +address it guesses for them (5.12.2). +.IP \(bu 4 +perlbug should no longer warn about uninitialized values when using the \fB\-d\fR +and \fB\-v\fR options (5.12.2). +.PP +\fIperl5db.pl\fR +.IX Subsection "perl5db.pl" +.IP \(bu 4 +The remote terminal works after forking and spawns new sessions, one +per forked process. +.PP +\fIptargrep\fR +.IX Subsection "ptargrep" +.IP \(bu 4 +ptargrep is a new utility to apply pattern matching to the contents of +files in a tar archive. It comes with \f(CW\*(C`Archive::Tar\*(C'\fR. +.SH "Configuration and Compilation" +.IX Header "Configuration and Compilation" +See also "Naming fixes in Policy_sh.SH may invalidate Policy.sh", +above. +.IP \(bu 4 +CCINCDIR and CCLIBDIR for the mingw64 cross-compiler are now correctly +under \fI$(CCHOME)\emingw\einclude\fR and \fI\elib\fR rather than immediately below +\&\fI$(CCHOME)\fR. +.Sp +This means the "incpath", "libpth", "ldflags", "lddlflags" and +"ldflags_nolargefiles" values in \fIConfig.pm\fR and \fIConfig_heavy.pl\fR are now +set correctly. +.IP \(bu 4 +\&\f(CW\*(C`make test.valgrind\*(C'\fR has been adjusted to account for \fIcpan/dist/ext\fR +separation. +.IP \(bu 4 +On compilers that support it, \fB\-Wwrite\-strings\fR is now added to cflags by +default. +.IP \(bu 4 +The Encode module can now (once again) be included in a static Perl +build. The special-case handling for this situation got broken in Perl +5.11.0, and has now been repaired. +.IP \(bu 4 +The previous default size of a PerlIO buffer (4096 bytes) has been increased +to the larger of 8192 bytes and your local BUFSIZ. Benchmarks show that doubling +this decade-old default increases read and write performance by around +25% to 50% when using the default layers of perlio on top of unix. To choose +a non-default size, such as to get back the old value or to obtain an even +larger value, configure with: +.Sp +.Vb 1 +\& ./Configure \-Accflags=\-DPERLIOBUF_DEFAULT_BUFSIZ=N +.Ve +.Sp +where N is the desired size in bytes; it should probably be a multiple of +your page size. +.IP \(bu 4 +An "incompatible operand types" error in ternary expressions when building +with \f(CW\*(C`clang\*(C'\fR has been fixed (5.12.2). +.IP \(bu 4 +Perl now skips setuid File::Copy tests on partitions it detects mounted +as \f(CW\*(C`nosuid\*(C'\fR (5.12.2). +.SH "Platform Support" +.IX Header "Platform Support" +.SS "New Platforms" +.IX Subsection "New Platforms" +.IP AIX 4 +.IX Item "AIX" +Perl now builds on AIX 4.2 (5.12.1). +.SS "Discontinued Platforms" +.IX Subsection "Discontinued Platforms" +.IP "Apollo DomainOS" 4 +.IX Item "Apollo DomainOS" +The last vestiges of support for this platform have been excised from +the Perl distribution. It was officially discontinued in version 5.12.0. +It had not worked for years before that. +.IP "MacOS Classic" 4 +.IX Item "MacOS Classic" +The last vestiges of support for this platform have been excised from the +Perl distribution. It was officially discontinued in an earlier version. +.SS "Platform-Specific Notes" +.IX Subsection "Platform-Specific Notes" +\fIAIX\fR +.IX Subsection "AIX" +.IP \(bu 4 +\&\fIREADME.aix\fR has been updated with information about the XL C/C++ V11 compiler +suite (5.12.2). +.PP +\fIARM\fR +.IX Subsection "ARM" +.IP \(bu 4 +The \f(CW\*(C`d_u32align\*(C'\fR configuration probe on ARM has been fixed (5.12.2). +.PP +\fICygwin\fR +.IX Subsection "Cygwin" +.IP \(bu 4 +MakeMaker has been updated to build manpages on cygwin. +.IP \(bu 4 +Improved rebase behaviour +.Sp +If a DLL is updated on cygwin the old imagebase address is reused. +This solves most rebase errors, especially when updating on core DLL's. +See +for more information. +.IP \(bu 4 +Support for the standard cygwin dll prefix (needed for FFIs) +.IP \(bu 4 +Updated build hints file +.PP +\fIFreeBSD 7\fR +.IX Subsection "FreeBSD 7" +.IP \(bu 4 +FreeBSD 7 no longer contains \fI/usr/bin/objformat\fR. At build time, +Perl now skips the \fIobjformat\fR check for versions 7 and higher and +assumes ELF (5.12.1). +.PP +\fIHP-UX\fR +.IX Subsection "HP-UX" +.IP \(bu 4 +Perl now allows \fB\-Duse64bitint\fR without promoting to \f(CW\*(C`use64bitall\*(C'\fR on HP-UX +(5.12.1). +.PP +\fIIRIX\fR +.IX Subsection "IRIX" +.IP \(bu 4 +Conversion of strings to floating-point numbers is now more accurate on +IRIX systems [perl #32380]. +.PP +\fIMac OS X\fR +.IX Subsection "Mac OS X" +.IP \(bu 4 +Early versions of Mac OS X (Darwin) had buggy implementations of the +\&\fBsetregid()\fR, \fBsetreuid()\fR, setrgid(,) and \fBsetruid()\fR functions, so Perl +would pretend they did not exist. +.Sp +These functions are now recognised on Mac OS 10.5 (Leopard; Darwin 9) and +higher, as they have been fixed [perl #72990]. +.PP +\fIMirBSD\fR +.IX Subsection "MirBSD" +.IP \(bu 4 +Previously if you built Perl with a shared \fIlibperl.so\fR on MirBSD (the +default config), it would work up to the installation; however, once +installed, it would be unable to find \fIlibperl\fR. Path handling is now +treated as in the other BSD dialects. +.PP +\fINetBSD\fR +.IX Subsection "NetBSD" +.IP \(bu 4 +The NetBSD hints file has been changed to make the system malloc the +default. +.PP +\fIOpenBSD\fR +.IX Subsection "OpenBSD" +.IP \(bu 4 +OpenBSD > 3.7 has a new malloc implementation which is \fImmap\fR\-based, +and as such can release memory back to the OS; however, Perl's use of +this malloc causes a substantial slowdown, so we now default to using +Perl's malloc instead [perl #75742]. +.PP +\fIOpenVOS\fR +.IX Subsection "OpenVOS" +.IP \(bu 4 +Perl now builds again with OpenVOS (formerly known as Stratus VOS) +[perl #78132] (5.12.3). +.PP +\fISolaris\fR +.IX Subsection "Solaris" +.IP \(bu 4 +DTrace is now supported on Solaris. There used to be build failures, but +these have been fixed [perl #73630] (5.12.3). +.PP +\fIVMS\fR +.IX Subsection "VMS" +.IP \(bu 4 +Extension building on older (pre 7.3\-2) VMS systems was broken because +configure.com hit the DCL symbol length limit of 1K. We now work within +this limit when assembling the list of extensions in the core build (5.12.1). +.IP \(bu 4 +We fixed configuring and building Perl with \fB\-Uuseperlio\fR (5.12.1). +.IP \(bu 4 +\&\f(CW\*(C`PerlIOUnix_open\*(C'\fR now honours the default permissions on VMS. +.Sp +When \f(CW\*(C`perlio\*(C'\fR became the default and \f(CW\*(C`unix\*(C'\fR became the default bottom layer, +the most common path for creating files from Perl became \f(CW\*(C`PerlIOUnix_open\*(C'\fR, +which has always explicitly used \f(CW0666\fR as the permission mask. This prevents +inheriting permissions from RMS defaults and ACLs, so to avoid that problem, +we now pass \f(CW0777\fR to \fBopen()\fR. In the VMS CRTL, \f(CW0777\fR has a special +meaning over and above intersecting with the current umask; specifically, it +allows Unix syscalls to preserve native default permissions (5.12.3). +.IP \(bu 4 +The shortening of symbols longer than 31 characters in the core C sources +and in extensions is now by default done by the C compiler rather than by +xsubpp (which could only do so for generated symbols in XS code). You can +reenable xsubpp's symbol shortening by configuring with \-Uuseshortenedsymbols, +but you'll have some work to do to get the core sources to compile. +.IP \(bu 4 +Record-oriented files (record format variable or variable with fixed control) +opened for write by the \f(CW\*(C`perlio\*(C'\fR layer will now be line-buffered to prevent the +introduction of spurious line breaks whenever the perlio buffer fills up. +.IP \(bu 4 +\&\fIgit_version.h\fR is now installed on VMS. This was an oversight in v5.12.0 which +caused some extensions to fail to build (5.12.2). +.IP \(bu 4 +Several memory leaks in \fBstat()\fR have been fixed (5.12.2). +.IP \(bu 4 +A memory leak in \fBPerl_rename()\fR due to a double allocation has been +fixed (5.12.2). +.IP \(bu 4 +A memory leak in \fBvms_fid_to_name()\fR (used by \fBrealpath()\fR and +\&\fBrealname()\fR> has been fixed (5.12.2). +.PP +\fIWindows\fR +.IX Subsection "Windows" +.PP +See also "\fBfork()\fR emulation will not wait for signalled children" and +"Perl source code is read in text mode on Windows", above. +.IP \(bu 4 +Fixed build process for SDK2003SP1 compilers. +.IP \(bu 4 +Compilation with Visual Studio 2010 is now supported. +.IP \(bu 4 +When using old 32\-bit compilers, the define \f(CW\*(C`_USE_32BIT_TIME_T\*(C'\fR is now +set in \f(CW$Config{ccflags}\fR. This improves portability when compiling +XS extensions using new compilers, but for a Perl compiled with old 32\-bit +compilers. +.IP \(bu 4 +\&\f(CW$Config{gccversion}\fR is now set correctly when Perl is built using the +mingw64 compiler from [perl #73754]. +.IP \(bu 4 +When building Perl with the mingw64 x64 cross-compiler \f(CW\*(C`incpath\*(C'\fR, +\&\f(CW\*(C`libpth\*(C'\fR, \f(CW\*(C`ldflags\*(C'\fR, \f(CW\*(C`lddlflags\*(C'\fR and \f(CW\*(C`ldflags_nolargefiles\*(C'\fR values +in \fIConfig.pm\fR and \fIConfig_heavy.pl\fR were not previously being set +correctly because, with that compiler, the include and lib directories +are not immediately below \f(CW\*(C`$(CCHOME)\*(C'\fR (5.12.2). +.IP \(bu 4 +The build process proceeds more smoothly with mingw and dmake when +\&\fIC:\eMSYS\ebin\fR is in the PATH, due to a \f(CW\*(C`Cwd\*(C'\fR fix. +.IP \(bu 4 +Support for building with Visual C++ 2010 is now underway, but is not yet +complete. See \fIREADME.win32\fR or perlwin32 for more details. +.IP \(bu 4 +The option to use an externally-supplied \fBcrypt()\fR, or to build with no +\&\fBcrypt()\fR at all, has been removed. Perl supplies its own \fBcrypt()\fR +implementation for Windows, and the political situation that required +this part of the distribution to sometimes be omitted is long gone. +.SH "Internal Changes" +.IX Header "Internal Changes" +.SS "New APIs" +.IX Subsection "New APIs" +\fICLONE_PARAMS structure added to ease correct thread creation\fR +.IX Subsection "CLONE_PARAMS structure added to ease correct thread creation" +.PP +Modules that create threads should now create \f(CW\*(C`CLONE_PARAMS\*(C'\fR structures +by calling the new function \fBPerl_clone_params_new()\fR, and free them with +\&\fBPerl_clone_params_del()\fR. This will ensure compatibility with any future +changes to the internals of the \f(CW\*(C`CLONE_PARAMS\*(C'\fR structure layout, and that +it is correctly allocated and initialised. +.PP +\fINew parsing functions\fR +.IX Subsection "New parsing functions" +.PP +Several functions have been added for parsing Perl statements and +expressions. These functions are meant to be used by XS code invoked +during Perl parsing, in a recursive-descent manner, to allow modules to +augment the standard Perl syntax. +.IP \(bu 4 +\&\fBparse_stmtseq()\fR +parses a sequence of statements, up to closing brace or EOF. +.IP \(bu 4 +\&\fBparse_fullstmt()\fR +parses a complete Perl statement, including optional label. +.IP \(bu 4 +\&\fBparse_barestmt()\fR +parses a statement without a label. +.IP \(bu 4 +\&\fBparse_block()\fR +parses a code block. +.IP \(bu 4 +\&\fBparse_label()\fR +parses a statement label, separate from statements. +.IP \(bu 4 +\&\f(CWparse_fullexpr()\fR, +\&\f(CWparse_listexpr()\fR, +\&\f(CWparse_termexpr()\fR, and +\&\f(CWparse_arithexpr()\fR +parse expressions at various precedence levels. +.PP +\fIHints hash API\fR +.IX Subsection "Hints hash API" +.PP +A new C API for introspecting the hinthash \f(CW\*(C`%^H\*(C'\fR at runtime has been +added. See \f(CW\*(C`cop_hints_2hv\*(C'\fR, \f(CW\*(C`cop_hints_fetchpvn\*(C'\fR, \f(CW\*(C`cop_hints_fetchpvs\*(C'\fR, +\&\f(CW\*(C`cop_hints_fetchsv\*(C'\fR, and \f(CW\*(C`hv_copy_hints_hv\*(C'\fR in perlapi for details. +.PP +A new, experimental API has been added for accessing the internal +structure that Perl uses for \f(CW\*(C`%^H\*(C'\fR. See the functions beginning with +\&\f(CW\*(C`cophh_\*(C'\fR in perlapi. +.PP +\fIC interface to \fR\f(BIcaller()\fR +.IX Subsection "C interface to caller()" +.PP +The \f(CW\*(C`caller_cx\*(C'\fR function has been added as an XSUB-writer's equivalent of +\&\fBcaller()\fR. See perlapi for details. +.PP +\fICustom per-subroutine check hooks\fR +.IX Subsection "Custom per-subroutine check hooks" +.PP +XS code in an extension module can now annotate a subroutine (whether +implemented in XS or in Perl) so that nominated XS code will be called +at compile time (specifically as part of op checking) to change the op +tree of that subroutine. The compile-time check function (supplied by +the extension module) can implement argument processing that can't be +expressed as a prototype, generate customised compile-time warnings, +perform constant folding for a pure function, inline a subroutine +consisting of sufficiently simple ops, replace the whole call with a +custom op, and so on. This was previously all possible by hooking the +\&\f(CW\*(C`entersub\*(C'\fR op checker, but the new mechanism makes it easy to tie the +hook to a specific subroutine. See "cv_set_call_checker" in perlapi. +.PP +To help in writing custom check hooks, several subtasks within standard +\&\f(CW\*(C`entersub\*(C'\fR op checking have been separated out and exposed in the API. +.PP +\fIImproved support for custom OPs\fR +.IX Subsection "Improved support for custom OPs" +.PP +Custom ops can now be registered with the new \f(CW\*(C`custom_op_register\*(C'\fR C +function and the \f(CW\*(C`XOP\*(C'\fR structure. This will make it easier to add new +properties of custom ops in the future. Two new properties have been added +already, \f(CW\*(C`xop_class\*(C'\fR and \f(CW\*(C`xop_peep\*(C'\fR. +.PP +\&\f(CW\*(C`xop_class\*(C'\fR is one of the OA_*OP constants. It allows B and other +introspection mechanisms to work with custom ops +that aren't BASEOPs. \f(CW\*(C`xop_peep\*(C'\fR is a pointer to +a function that will be called for ops of this +type from \f(CW\*(C`Perl_rpeep\*(C'\fR. +.PP +See "Custom Operators" in perlguts and "Custom Operators" in perlapi for more +detail. +.PP +The old \f(CW\*(C`PL_custom_op_names\*(C'\fR/\f(CW\*(C`PL_custom_op_descs\*(C'\fR interface is still +supported but discouraged. +.PP +\fIScope hooks\fR +.IX Subsection "Scope hooks" +.PP +It is now possible for XS code to hook into Perl's lexical scope +mechanism at compile time, using the new \f(CW\*(C`Perl_blockhook_register\*(C'\fR +function. See "Compile-time scope hooks" in perlguts. +.PP +\fIThe recursive part of the peephole optimizer is now hookable\fR +.IX Subsection "The recursive part of the peephole optimizer is now hookable" +.PP +In addition to \f(CW\*(C`PL_peepp\*(C'\fR, for hooking into the toplevel peephole optimizer, a +\&\f(CW\*(C`PL_rpeepp\*(C'\fR is now available to hook into the optimizer recursing into +side-chains of the optree. +.PP +\fINew non-magical variants of existing functions\fR +.IX Subsection "New non-magical variants of existing functions" +.PP +The following functions/macros have been added to the API. The \f(CW*_nomg\fR +macros are equivalent to their non\-\f(CW\*(C`_nomg\*(C'\fR variants, except that they ignore +get-magic. Those ending in \f(CW\*(C`_flags\*(C'\fR allow one to specify whether +get-magic is processed. +.PP +.Vb 8 +\& sv_2bool_flags +\& SvTRUE_nomg +\& sv_2nv_flags +\& SvNV_nomg +\& sv_cmp_flags +\& sv_cmp_locale_flags +\& sv_eq_flags +\& sv_collxfrm_flags +.Ve +.PP +In some of these cases, the non\-\f(CW\*(C`_flags\*(C'\fR functions have +been replaced with wrappers around the new functions. +.PP +\fIpv/pvs/sv versions of existing functions\fR +.IX Subsection "pv/pvs/sv versions of existing functions" +.PP +Many functions ending with pvn now have equivalent \f(CW\*(C`pv/pvs/sv\*(C'\fR versions. +.PP +\fIList op-building functions\fR +.IX Subsection "List op-building functions" +.PP +List op-building functions have been added to the +API. See op_append_elem, +op_append_list, and +op_prepend_elem in perlapi. +.PP +\fR\f(CI\*(C`LINKLIST\*(C'\fR\fI\fR +.IX Subsection "LINKLIST" +.PP +The LINKLIST macro, part of op building that +constructs the execution-order op chain, has been added to the API. +.PP +\fILocalisation functions\fR +.IX Subsection "Localisation functions" +.PP +The \f(CW\*(C`save_freeop\*(C'\fR, \f(CW\*(C`save_op\*(C'\fR, \f(CW\*(C`save_pushi32ptr\*(C'\fR and \f(CW\*(C`save_pushptrptr\*(C'\fR +functions have been added to the API. +.PP +\fIStash names\fR +.IX Subsection "Stash names" +.PP +A stash can now have a list of effective names in addition to its usual +name. The first effective name can be accessed via the \f(CW\*(C`HvENAME\*(C'\fR macro, +which is now the recommended name to use in MRO linearisations (\f(CW\*(C`HvNAME\*(C'\fR +being a fallback if there is no \f(CW\*(C`HvENAME\*(C'\fR). +.PP +These names are added and deleted via \f(CW\*(C`hv_ename_add\*(C'\fR and +\&\f(CW\*(C`hv_ename_delete\*(C'\fR. These two functions are \fInot\fR part of the API. +.PP +\fINew functions for finding and removing magic\fR +.IX Subsection "New functions for finding and removing magic" +.PP +The \f(CWmg_findext()\fR and +\&\f(CWsv_unmagicext()\fR +functions have been added to the API. +They allow extension authors to find and remove magic attached to +scalars based on both the magic type and the magic virtual table, similar to how +\&\fBsv_magicext()\fR attaches magic of a certain type and with a given virtual table +to a scalar. This eliminates the need for extensions to walk the list of +\&\f(CW\*(C`MAGIC\*(C'\fR pointers of an \f(CW\*(C`SV\*(C'\fR to find the magic that belongs to them. +.PP +\fR\f(CI\*(C`find_rundefsv\*(C'\fR\fI\fR +.IX Subsection "find_rundefsv" +.PP +This function returns the SV representing \f(CW$_\fR, whether it's lexical +or dynamic. +.PP +\fR\f(CI\*(C`Perl_croak_no_modify\*(C'\fR\fI\fR +.IX Subsection "Perl_croak_no_modify" +.PP +\&\fBPerl_croak_no_modify()\fR is short-hand for +\&\f(CW\*(C`Perl_croak("%s", PL_no_modify)\*(C'\fR. +.PP +\fR\f(CI\*(C`PERL_STATIC_INLINE\*(C'\fR\fI define\fR +.IX Subsection "PERL_STATIC_INLINE define" +.PP +The \f(CW\*(C`PERL_STATIC_INLINE\*(C'\fR define has been added to provide the best-guess +incantation to use for static inline functions, if the C compiler supports +C99\-style static inline. If it doesn't, it'll give a plain \f(CW\*(C`static\*(C'\fR. +.PP +\&\f(CW\*(C`HAS_STATIC_INLINE\*(C'\fR can be used to check if the compiler actually supports +inline functions. +.PP +\fINew \fR\f(CI\*(C`pv_escape\*(C'\fR\fI option for hexadecimal escapes\fR +.IX Subsection "New pv_escape option for hexadecimal escapes" +.PP +A new option, \f(CW\*(C`PERL_PV_ESCAPE_NONASCII\*(C'\fR, has been added to \f(CW\*(C`pv_escape\*(C'\fR to +dump all characters above ASCII in hexadecimal. Before, one could get all +characters as hexadecimal or the Latin1 non-ASCII as octal. +.PP +\fR\f(CI\*(C`lex_start\*(C'\fR\fI\fR +.IX Subsection "lex_start" +.PP +\&\f(CW\*(C`lex_start\*(C'\fR has been added to the API, but is considered experimental. +.PP +\fR\f(BIop_scope()\fR\fI and \fR\f(BIop_lvalue()\fR\fI\fR +.IX Subsection "op_scope() and op_lvalue()" +.PP +The \fBop_scope()\fR and \fBop_lvalue()\fR functions have been added to the API, +but are considered experimental. +.SS "C API Changes" +.IX Subsection "C API Changes" +\fR\f(CI\*(C`PERL_POLLUTE\*(C'\fR\fI has been removed\fR +.IX Subsection "PERL_POLLUTE has been removed" +.PP +The option to define \f(CW\*(C`PERL_POLLUTE\*(C'\fR to expose older 5.005 symbols for +backwards compatibility has been removed. Its use was always discouraged, +and MakeMaker contains a more specific escape hatch: +.PP +.Vb 1 +\& perl Makefile.PL POLLUTE=1 +.Ve +.PP +This can be used for modules that have not been upgraded to 5.6 naming +conventions (and really should be completely obsolete by now). +.PP +\fICheck API compatibility when loading XS modules\fR +.IX Subsection "Check API compatibility when loading XS modules" +.PP +When Perl's API changes in incompatible ways (which usually happens between +major releases), XS modules compiled for previous versions of Perl will no +longer work. They need to be recompiled against the new Perl. +.PP +The \f(CW\*(C`XS_APIVERSION_BOOTCHECK\*(C'\fR macro has been added to ensure that modules +are recompiled and to prevent users from accidentally loading modules +compiled for old perls into newer perls. That macro, which is called when +loading every newly compiled extension, compares the API version of the +running perl with the version a module has been compiled for and raises an +exception if they don't match. +.PP +\fIPerl_fetch_cop_label\fR +.IX Subsection "Perl_fetch_cop_label" +.PP +The first argument of the C API function \f(CW\*(C`Perl_fetch_cop_label\*(C'\fR has changed +from \f(CW\*(C`struct refcounted_he *\*(C'\fR to \f(CW\*(C`COP *\*(C'\fR, to insulate the user from +implementation details. +.PP +This API function was marked as "may change", and likely isn't in use outside +the core. (Neither an unpacked CPAN nor Google's codesearch finds any other +references to it.) +.PP +\fR\f(BIGvCV()\fR\fI and \fR\f(BIGvGP()\fR\fI are no longer lvalues\fR +.IX Subsection "GvCV() and GvGP() are no longer lvalues" +.PP +The new \fBGvCV_set()\fR and \fBGvGP_set()\fR macros are now provided to replace +assignment to those two macros. +.PP +This allows a future commit to eliminate some backref magic between GV +and CVs, which will require complete control over assignment to the +\&\f(CW\*(C`gp_cv\*(C'\fR slot. +.PP +\fR\f(BICvGV()\fR\fI is no longer an lvalue\fR +.IX Subsection "CvGV() is no longer an lvalue" +.PP +Under some circumstances, the \fBCvGV()\fR field of a CV is now +reference-counted. To ensure consistent behaviour, direct assignment to +it, for example \f(CW\*(C`CvGV(cv) = gv\*(C'\fR is now a compile-time error. A new macro, +\&\f(CW\*(C`CvGV_set(cv,gv)\*(C'\fR has been introduced to run this operation +safely. Note that modification of this field is not part of the public +API, regardless of this new macro (and despite its being listed in this section). +.PP +\fR\f(BICvSTASH()\fR\fI is no longer an lvalue\fR +.IX Subsection "CvSTASH() is no longer an lvalue" +.PP +The \fBCvSTASH()\fR macro can now only be used as an rvalue. \fBCvSTASH_set()\fR +has been added to replace assignment to \fBCvSTASH()\fR. This is to ensure +that backreferences are handled properly. These macros are not part of the +API. +.PP +\fICalling conventions for \fR\f(CI\*(C`newFOROP\*(C'\fR\fI and \fR\f(CI\*(C`newWHILEOP\*(C'\fR +.IX Subsection "Calling conventions for newFOROP and newWHILEOP" +.PP +The way the parser handles labels has been cleaned up and refactored. As a +result, the \fBnewFOROP()\fR constructor function no longer takes a parameter +stating what label is to go in the state op. +.PP +The \fBnewWHILEOP()\fR and \fBnewFOROP()\fR functions no longer accept a line +number as a parameter. +.PP +\fIFlags passed to \fR\f(CI\*(C`uvuni_to_utf8_flags\*(C'\fR\fI and \fR\f(CI\*(C`utf8n_to_uvuni\*(C'\fR +.IX Subsection "Flags passed to uvuni_to_utf8_flags and utf8n_to_uvuni" +.PP +Some of the flags parameters to \fBuvuni_to_utf8_flags()\fR and +\&\fButf8n_to_uvuni()\fR have changed. This is a result of Perl's now allowing +internal storage and manipulation of code points that are problematic +in some situations. Hence, the default actions for these functions has +been complemented to allow these code points. The new flags are +documented in perlapi. Code that requires the problematic code +points to be rejected needs to change to use the new flags. Some flag +names are retained for backward source compatibility, though they do +nothing, as they are now the default. However the flags +\&\f(CW\*(C`UNICODE_ALLOW_FDD0\*(C'\fR, \f(CW\*(C`UNICODE_ALLOW_FFFF\*(C'\fR, \f(CW\*(C`UNICODE_ILLEGAL\*(C'\fR, and +\&\f(CW\*(C`UNICODE_IS_ILLEGAL\*(C'\fR have been removed, as they stem from a +fundamentally broken model of how the Unicode non-character code points +should be handled, which is now described in +"Non-character code points" in perlunicode. See also the Unicode section +under "Selected Bug Fixes". +.SS "Deprecated C APIs" +.IX Subsection "Deprecated C APIs" +.ie n .IP """Perl_ptr_table_clear""" 4 +.el .IP \f(CWPerl_ptr_table_clear\fR 4 +.IX Item "Perl_ptr_table_clear" +\&\f(CW\*(C`Perl_ptr_table_clear\*(C'\fR is no longer part of Perl's public API. Calling it +now generates a deprecation warning, and it will be removed in a future +release. +.ie n .IP """sv_compile_2op""" 4 +.el .IP \f(CWsv_compile_2op\fR 4 +.IX Item "sv_compile_2op" +The \fBsv_compile_2op()\fR API function is now deprecated. Searches suggest +that nothing on CPAN is using it, so this should have zero impact. +.Sp +It attempted to provide an API to compile code down to an optree, but failed +to bind correctly to lexicals in the enclosing scope. It's not possible to +fix this problem within the constraints of its parameters and return value. +.ie n .IP """find_rundefsvoffset""" 4 +.el .IP \f(CWfind_rundefsvoffset\fR 4 +.IX Item "find_rundefsvoffset" +The \f(CW\*(C`find_rundefsvoffset\*(C'\fR function has been deprecated. It appeared that +its design was insufficient for reliably getting the lexical \f(CW$_\fR at +run-time. +.Sp +Use the new \f(CW\*(C`find_rundefsv\*(C'\fR function or the \f(CW\*(C`UNDERBAR\*(C'\fR macro +instead. They directly return the right SV +representing \f(CW$_\fR, whether it's +lexical or dynamic. +.ie n .IP """CALL_FPTR"" and ""CPERLscope""" 4 +.el .IP "\f(CWCALL_FPTR\fR and \f(CWCPERLscope\fR" 4 +.IX Item "CALL_FPTR and CPERLscope" +Those are left from an old implementation of \f(CW\*(C`MULTIPLICITY\*(C'\fR using C++ objects, +which was removed in Perl 5.8. Nowadays these macros do exactly nothing, so +they shouldn't be used anymore. +.Sp +For compatibility, they are still defined for external \f(CW\*(C`XS\*(C'\fR code. Only +extensions defining \f(CW\*(C`PERL_CORE\*(C'\fR must be updated now. +.SS "Other Internal Changes" +.IX Subsection "Other Internal Changes" +\fIStack unwinding\fR +.IX Subsection "Stack unwinding" +.PP +The protocol for unwinding the C stack at the last stage of a \f(CW\*(C`die\*(C'\fR +has changed how it identifies the target stack frame. This now uses +a separate variable \f(CW\*(C`PL_restartjmpenv\*(C'\fR, where previously it relied on +the \f(CW\*(C`blk_eval.cur_top_env\*(C'\fR pointer in the \f(CW\*(C`eval\*(C'\fR context frame that +has nominally just been discarded. This change means that code running +during various stages of Perl-level unwinding no longer needs to take +care to avoid destroying the ghost frame. +.PP +\fIScope stack entries\fR +.IX Subsection "Scope stack entries" +.PP +The format of entries on the scope stack has been changed, resulting in a +reduction of memory usage of about 10%. In particular, the memory used by +the scope stack to record each active lexical variable has been halved. +.PP +\fIMemory allocation for pointer tables\fR +.IX Subsection "Memory allocation for pointer tables" +.PP +Memory allocation for pointer tables has been changed. Previously +\&\f(CW\*(C`Perl_ptr_table_store\*(C'\fR allocated memory from the same arena system as +\&\f(CW\*(C`SV\*(C'\fR bodies and \f(CW\*(C`HE\*(C'\fRs, with freed memory remaining bound to those arenas +until interpreter exit. Now it allocates memory from arenas private to the +specific pointer table, and that memory is returned to the system when +\&\f(CW\*(C`Perl_ptr_table_free\*(C'\fR is called. Additionally, allocation and release are +both less CPU intensive. +.PP +\fR\f(CI\*(C`UNDERBAR\*(C'\fR\fI\fR +.IX Subsection "UNDERBAR" +.PP +The \f(CW\*(C`UNDERBAR\*(C'\fR macro now calls \f(CW\*(C`find_rundefsv\*(C'\fR. \f(CW\*(C`dUNDERBAR\*(C'\fR is now a +noop but should still be used to ensure past and future compatibility. +.PP +\fIString comparison routines renamed\fR +.IX Subsection "String comparison routines renamed" +.PP +The \f(CW\*(C`ibcmp_*\*(C'\fR functions have been renamed and are now called \f(CW\*(C`foldEQ\*(C'\fR, +\&\f(CW\*(C`foldEQ_locale\*(C'\fR, and \f(CW\*(C`foldEQ_utf8\*(C'\fR. The old names are still available as +macros. +.PP +\fR\f(CI\*(C`chop\*(C'\fR\fI and \fR\f(CI\*(C`chomp\*(C'\fR\fI implementations merged\fR +.IX Subsection "chop and chomp implementations merged" +.PP +The opcode bodies for \f(CW\*(C`chop\*(C'\fR and \f(CW\*(C`chomp\*(C'\fR and for \f(CW\*(C`schop\*(C'\fR and \f(CW\*(C`schomp\*(C'\fR +have been merged. The implementation functions \fBPerl_do_chop()\fR and +\&\fBPerl_do_chomp()\fR, never part of the public API, have been merged and +moved to a static function in \fIpp.c\fR. This shrinks the Perl binary +slightly, and should not affect any code outside the core (unless it is +relying on the order of side-effects when \f(CW\*(C`chomp\*(C'\fR is passed a \fIlist\fR of +values). +.SH "Selected Bug Fixes" +.IX Header "Selected Bug Fixes" +.SS I/O +.IX Subsection "I/O" +.IP \(bu 4 +Perl no longer produces this warning: +.Sp +.Vb 2 +\& $ perl \-we \*(Aqopen(my $f, ">", \emy $x); binmode($f, "scalar")\*(Aq +\& Use of uninitialized value in binmode at \-e line 1. +.Ve +.IP \(bu 4 +Opening a glob reference via \f(CW\*(C`open($fh, ">", \e*glob)\*(C'\fR no longer +causes the glob to be corrupted when the filehandle is printed to. This would +cause Perl to crash whenever the glob's contents were accessed +[perl #77492]. +.IP \(bu 4 +PerlIO no longer crashes when called recursively, such as from a signal +handler. Now it just leaks memory [perl #75556]. +.IP \(bu 4 +Most I/O functions were not warning for unopened handles unless the +"closed" and "unopened" warnings categories were both enabled. Now only +\&\f(CW\*(C`use warnings \*(Aqunopened\*(Aq\*(C'\fR is necessary to trigger these warnings, as +had always been the intention. +.IP \(bu 4 +There have been several fixes to PerlIO layers: +.Sp +When \f(CW\*(C`binmode(FH, ":crlf")\*(C'\fR pushes the \f(CW\*(C`:crlf\*(C'\fR layer on top of the stack, +it no longer enables crlf layers lower in the stack so as to avoid +unexpected results [perl #38456]. +.Sp +Opening a file in \f(CW\*(C`:raw\*(C'\fR mode now does what it advertises to do (first +open the file, then \f(CW\*(C`binmode\*(C'\fR it), instead of simply leaving off the top +layer [perl #80764]. +.Sp +The three layers \f(CW\*(C`:pop\*(C'\fR, \f(CW\*(C`:utf8\*(C'\fR, and \f(CW\*(C`:bytes\*(C'\fR didn't allow stacking when +opening a file. For example +this: +.Sp +.Vb 1 +\& open(FH, ">:pop:perlio", "some.file") or die $!; +.Ve +.Sp +would throw an "Invalid argument" error. This has been fixed in this +release [perl #82484]. +.SS "Regular Expression Bug Fixes" +.IX Subsection "Regular Expression Bug Fixes" +.IP \(bu 4 +The regular expression engine no longer loops when matching +\&\f(CW\*(C`"\eN{LATIN SMALL LIGATURE FF}" =~ /f+/i\*(C'\fR and similar expressions +[perl #72998] (5.12.1). +.IP \(bu 4 +The trie runtime code should no longer allocate massive amounts of memory, +fixing #74484. +.IP \(bu 4 +Syntax errors in \f(CW\*(C`(?{...})\*(C'\fR blocks no longer cause panic messages +[perl #2353]. +.IP \(bu 4 +A pattern like \f(CW\*(C`(?:(o){2})?\*(C'\fR no longer causes a "panic" error +[perl #39233]. +.IP \(bu 4 +A fatal error in regular expressions containing \f(CW\*(C`(.*?)\*(C'\fR when processing +UTF\-8 data has been fixed [perl #75680] (5.12.2). +.IP \(bu 4 +An erroneous regular expression engine optimisation that caused regex verbs like +\&\f(CW*COMMIT\fR sometimes to be ignored has been removed. +.IP \(bu 4 +The regular expression bracketed character class \f(CW\*(C`[\e8\e9]\*(C'\fR was effectively the +same as \f(CW\*(C`[89\e000]\*(C'\fR, incorrectly matching a NULL character. It also gave +incorrect warnings that the \f(CW8\fR and \f(CW9\fR were ignored. Now \f(CW\*(C`[\e8\e9]\*(C'\fR is the +same as \f(CW\*(C`[89]\*(C'\fR and gives legitimate warnings that \f(CW\*(C`\e8\*(C'\fR and \f(CW\*(C`\e9\*(C'\fR are +unrecognized escape sequences, passed-through. +.IP \(bu 4 +A regular expression match in the right-hand side of a global substitution +(\f(CW\*(C`s///g\*(C'\fR) that is in the same scope will no longer cause match variables +to have the wrong values on subsequent iterations. This can happen when an +array or hash subscript is interpolated in the right-hand side, as in +\&\f(CW\*(C`s|(.)|@a{ print($1), /./ }|g\*(C'\fR [perl #19078]. +.IP \(bu 4 +Several cases in which characters in the Latin\-1 non-ASCII range (0x80 to +0xFF) used not to match themselves, or used to match both a character class +and its complement, have been fixed. For instance, U+00E2 could match both +\&\f(CW\*(C`\ew\*(C'\fR and \f(CW\*(C`\eW\*(C'\fR [perl #78464] [perl #18281] [perl #60156]. +.IP \(bu 4 +Matching a Unicode character against an alternation containing characters +that happened to match continuation bytes in the former's UTF8 +representation (like \f(CW\*(C`qq{\ex{30ab}} =~ /\exab|\exa9/\*(C'\fR) would cause erroneous +warnings [perl #70998]. +.IP \(bu 4 +The trie optimisation was not taking empty groups into account, preventing +"foo" from matching \f(CW\*(C`/\eA(?:(?:)foo|bar|zot)\ez/\*(C'\fR [perl #78356]. +.IP \(bu 4 +A pattern containing a \f(CW\*(C`+\*(C'\fR inside a lookahead would sometimes cause an +incorrect match failure in a global match (for example, \f(CW\*(C`/(?=(\eS+))/g\*(C'\fR) +[perl #68564]. +.IP \(bu 4 +A regular expression optimisation would sometimes cause a match with a +\&\f(CW\*(C`{n,m}\*(C'\fR quantifier to fail when it should have matched [perl #79152]. +.IP \(bu 4 +Case-insensitive matching in regular expressions compiled under +\&\f(CW\*(C`use locale\*(C'\fR now works much more sanely when the pattern or target +string is internally encoded in UTF8. Previously, under these +conditions the localeness was completely lost. Now, code points +above 255 are treated as Unicode, but code points between 0 and 255 +are treated using the current locale rules, regardless of whether +the pattern or the string is encoded in UTF8. The few case-insensitive +matches that cross the 255/256 boundary are not allowed. For +example, 0xFF does not caselessly match the character at 0x178, +LATIN CAPITAL LETTER Y WITH DIAERESIS, because 0xFF may not be LATIN +SMALL LETTER Y in the current locale, and Perl has no way of knowing +if that character even exists in the locale, much less what code +point it is. +.IP \(bu 4 +The \f(CW\*(C`(?|...)\*(C'\fR regular expression construct no longer crashes if the final +branch has more sets of capturing parentheses than any other branch. This +was fixed in Perl 5.10.1 for the case of a single branch, but that fix did +not take multiple branches into account [perl #84746]. +.IP \(bu 4 +A bug has been fixed in the implementation of \f(CW\*(C`{...}\*(C'\fR quantifiers in +regular expressions that prevented the code block in +\&\f(CW\*(C`/((\ew+)(?{ print $2 })){2}/\*(C'\fR from seeing the \f(CW$2\fR sometimes +[perl #84294]. +.SS "Syntax/Parsing Bugs" +.IX Subsection "Syntax/Parsing Bugs" +.IP \(bu 4 +\&\f(CW\*(C`when (scalar) {...}\*(C'\fR no longer crashes, but produces a syntax error +[perl #74114] (5.12.1). +.IP \(bu 4 +A label right before a string eval (\f(CW\*(C`foo: eval $string\*(C'\fR) no longer causes +the label to be associated also with the first statement inside the eval +[perl #74290] (5.12.1). +.IP \(bu 4 +The \f(CW\*(C`no 5.13.2\*(C'\fR form of \f(CW\*(C`no\*(C'\fR no longer tries to turn on features or +pragmata (like strict) [perl #70075] (5.12.2). +.IP \(bu 4 +\&\f(CW\*(C`BEGIN {require 5.12.0}\*(C'\fR now behaves as documented, rather than behaving +identically to \f(CW\*(C`use 5.12.0\*(C'\fR. Previously, \f(CW\*(C`require\*(C'\fR in a \f(CW\*(C`BEGIN\*(C'\fR block +was erroneously executing the \f(CW\*(C`use feature \*(Aq:5.12.0\*(Aq\*(C'\fR and +\&\f(CW\*(C`use strict\*(C'\fR behaviour, which only \f(CW\*(C`use\*(C'\fR was documented to +provide [perl #69050]. +.IP \(bu 4 +A regression introduced in Perl 5.12.0, making +\&\f(CW\*(C`my $x = 3; $x = length(undef)\*(C'\fR result in \f(CW$x\fR set to \f(CW3\fR has been +fixed. \f(CW$x\fR will now be \f(CW\*(C`undef\*(C'\fR [perl #85508] (5.12.2). +.IP \(bu 4 +When strict "refs" mode is off, \f(CW\*(C`%{...}\*(C'\fR in rvalue context returns +\&\f(CW\*(C`undef\*(C'\fR if its argument is undefined. An optimisation introduced in Perl +5.12.0 to make \f(CW\*(C`keys %{...}\*(C'\fR faster when used as a boolean did not take +this into account, causing \f(CW\*(C`keys %{+undef}\*(C'\fR (and \f(CW\*(C`keys %$foo\*(C'\fR when +\&\f(CW$foo\fR is undefined) to be an error, which it should be so in strict +mode only [perl #81750]. +.IP \(bu 4 +Constant-folding used to cause +.Sp +.Vb 1 +\& $text =~ ( 1 ? /phoo/ : /bear/) +.Ve +.Sp +to turn into +.Sp +.Vb 1 +\& $text =~ /phoo/ +.Ve +.Sp +at compile time. Now it correctly matches against \f(CW$_\fR [perl #20444]. +.IP \(bu 4 +Parsing Perl code (either with string \f(CW\*(C`eval\*(C'\fR or by loading modules) from +within a \f(CW\*(C`UNITCHECK\*(C'\fR block no longer causes the interpreter to crash +[perl #70614]. +.IP \(bu 4 +String \f(CW\*(C`eval\*(C'\fRs no longer fail after 2 billion scopes have been +compiled [perl #83364]. +.IP \(bu 4 +The parser no longer hangs when encountering certain Unicode characters, +such as U+387 [perl #74022]. +.IP \(bu 4 +Defining a constant with the same name as one of Perl's special blocks +(like \f(CW\*(C`INIT\*(C'\fR) stopped working in 5.12.0, but has now been fixed +[perl #78634]. +.IP \(bu 4 +A reference to a literal value used as a hash key (\f(CW$hash{\e"foo"}\fR) used +to be stringified, even if the hash was tied [perl #79178]. +.IP \(bu 4 +A closure containing an \f(CW\*(C`if\*(C'\fR statement followed by a constant or variable +is no longer treated as a constant [perl #63540]. +.IP \(bu 4 +\&\f(CW\*(C`state\*(C'\fR can now be used with attributes. It +used to mean the same thing as +\&\f(CW\*(C`my\*(C'\fR if any attributes were present [perl #68658]. +.IP \(bu 4 +Expressions like \f(CW\*(C`@$a > 3\*(C'\fR no longer cause \f(CW$a\fR to be mentioned in +the "Use of uninitialized value in numeric gt" warning when \f(CW$a\fR is +undefined (since it is not part of the \f(CW\*(C`>\*(C'\fR expression, but the operand +of the \f(CW\*(C`@\*(C'\fR) [perl #72090]. +.IP \(bu 4 +Accessing an element of a package array with a hard-coded number (as +opposed to an arbitrary expression) would crash if the array did not exist. +Usually the array would be autovivified during compilation, but typeglob +manipulation could remove it, as in these two cases which used to crash: +.Sp +.Vb 2 +\& *d = *a; print $d[0]; +\& undef *d; print $d[0]; +.Ve +.IP \(bu 4 +The \fB\-C\fR command-line option, when used on the shebang line, can now be +followed by other options [perl #72434]. +.IP \(bu 4 +The \f(CW\*(C`B\*(C'\fR module was returning \f(CW\*(C`B::OP\*(C'\fRs instead of \f(CW\*(C`B::LOGOP\*(C'\fRs for +\&\f(CW\*(C`entertry\*(C'\fR [perl #80622]. This was due to a bug in the Perl core, +not in \f(CW\*(C`B\*(C'\fR itself. +.SS "Stashes, Globs and Method Lookup" +.IX Subsection "Stashes, Globs and Method Lookup" +Perl 5.10.0 introduced a new internal mechanism for caching MROs (method +resolution orders, or lists of parent classes; aka "isa" caches) to make +method lookup faster (so \f(CW@ISA\fR arrays would not have to be searched +repeatedly). Unfortunately, this brought with it quite a few bugs. Almost +all of these have been fixed now, along with a few MRO-related bugs that +existed before 5.10.0: +.IP \(bu 4 +The following used to have erratic effects on method resolution, because +the "isa" caches were not reset or otherwise ended up listing the wrong +classes. These have been fixed. +.RS 4 +.IP "Aliasing packages by assigning to globs [perl #77358]" 4 +.IX Item "Aliasing packages by assigning to globs [perl #77358]" +.PD 0 +.IP "Deleting packages by deleting their containing stash elements" 4 +.IX Item "Deleting packages by deleting their containing stash elements" +.ie n .IP "Undefining the glob containing a package (""undef *Foo::"")" 4 +.el .IP "Undefining the glob containing a package (\f(CWundef *Foo::\fR)" 4 +.IX Item "Undefining the glob containing a package (undef *Foo::)" +.ie n .IP "Undefining an ISA glob (""undef *Foo::ISA"")" 4 +.el .IP "Undefining an ISA glob (\f(CWundef *Foo::ISA\fR)" 4 +.IX Item "Undefining an ISA glob (undef *Foo::ISA)" +.ie n .IP "Deleting an ISA stash element (""delete $Foo::{ISA}"")" 4 +.el .IP "Deleting an ISA stash element (\f(CWdelete $Foo::{ISA}\fR)" 4 +.IX Item "Deleting an ISA stash element (delete $Foo::{ISA})" +.ie n .IP "Sharing @ISA arrays between classes (via ""*Foo::ISA = \e@Bar::ISA"" or ""*Foo::ISA = *Bar::ISA"") [perl #77238]" 4 +.el .IP "Sharing \f(CW@ISA\fR arrays between classes (via \f(CW*Foo::ISA = \e@Bar::ISA\fR or \f(CW*Foo::ISA = *Bar::ISA\fR) [perl #77238]" 4 +.IX Item "Sharing @ISA arrays between classes (via *Foo::ISA = @Bar::ISA or *Foo::ISA = *Bar::ISA) [perl #77238]" +.RE +.RS 4 +.PD +.Sp +\&\f(CW\*(C`undef *Foo::ISA\*(C'\fR would even stop a new \f(CW@Foo::ISA\fR array from updating +caches. +.RE +.IP \(bu 4 +Typeglob assignments would crash if the glob's stash no longer existed, so +long as the glob assigned to were named \f(CW\*(C`ISA\*(C'\fR or the glob on either side of +the assignment contained a subroutine. +.IP \(bu 4 +\&\f(CW\*(C`PL_isarev\*(C'\fR, which is accessible to Perl via \f(CW\*(C`mro::get_isarev\*(C'\fR is now +updated properly when packages are deleted or removed from the \f(CW@ISA\fR of +other classes. This allows many packages to be created and deleted without +causing a memory leak [perl #75176]. +.PP +In addition, various other bugs related to typeglobs and stashes have been +fixed: +.IP \(bu 4 +Some work has been done on the internal pointers that link between symbol +tables (stashes), typeglobs, and subroutines. This has the effect that +various edge cases related to deleting stashes or stash entries (for example, +<%FOO:: = ()>), and complex typeglob or code-reference aliasing, will no +longer crash the interpreter. +.IP \(bu 4 +Assigning a reference to a glob copy now assigns to a glob slot instead of +overwriting the glob with a scalar [perl #1804] [perl #77508]. +.IP \(bu 4 +A bug when replacing the glob of a loop variable within the loop has been fixed +[perl #21469]. This +means the following code will no longer crash: +.Sp +.Vb 3 +\& for $x (...) { +\& *x = *y; +\& } +.Ve +.IP \(bu 4 +Assigning a glob to a PVLV used to convert it to a plain string. Now it +works correctly, and a PVLV can hold a glob. This would happen when a +nonexistent hash or array element was passed to a subroutine: +.Sp +.Vb 2 +\& sub { $_[0] = *foo }\->($hash{key}); +\& # $_[0] would have been the string "*main::foo" +.Ve +.Sp +It also happened when a glob was assigned to, or returned from, an element +of a tied array or hash [perl #36051]. +.IP \(bu 4 +When trying to report \f(CW\*(C`Use of uninitialized value $Foo::BAR\*(C'\fR, crashes could +occur if the glob holding the global variable in question had been detached +from its original stash by, for example, \f(CW\*(C`delete $::{"Foo::"}\*(C'\fR. This has +been fixed by disabling the reporting of variable names in those +cases. +.IP \(bu 4 +During the restoration of a localised typeglob on scope exit, any +destructors called as a result would be able to see the typeglob in an +inconsistent state, containing freed entries, which could result in a +crash. This would affect code like this: +.Sp +.Vb 5 +\& local *@; +\& eval { die bless [] }; # puts an object in $@ +\& sub DESTROY { +\& local $@; # boom +\& } +.Ve +.Sp +Now the glob entries are cleared before any destructors are called. This +also means that destructors can vivify entries in the glob. So Perl tries +again and, if the entries are re-created too many times, dies with a +"panic: gp_free ..." error message. +.IP \(bu 4 +If a typeglob is freed while a subroutine attached to it is still +referenced elsewhere, the subroutine is renamed to \f(CW\*(C`_\|_ANON_\|_\*(C'\fR in the same +package, unless the package has been undefined, in which case the \f(CW\*(C`_\|_ANON_\|_\*(C'\fR +package is used. This could cause packages to be sometimes autovivified, +such as if the package had been deleted. Now this no longer occurs. +The \f(CW\*(C`_\|_ANON_\|_\*(C'\fR package is also now used when the original package is +no longer attached to the symbol table. This avoids memory leaks in some +cases [perl #87664]. +.IP \(bu 4 +Subroutines and package variables inside a package whose name ends with +\&\f(CW\*(C`::\*(C'\fR can now be accessed with a fully qualified name. +.SS Unicode +.IX Subsection "Unicode" +.IP \(bu 4 +What has become known as "the Unicode Bug" is almost completely resolved in +this release. Under \f(CW\*(C`use feature \*(Aqunicode_strings\*(Aq\*(C'\fR (which is +automatically selected by \f(CW\*(C`use 5.012\*(C'\fR and above), the internal +storage format of a string no longer affects the external semantics. +[perl #58182]. +.Sp +There are two known exceptions: +.RS 4 +.IP 1. 4 +The now-deprecated, user-defined case-changing +functions require utf8\-encoded strings to operate. The CPAN module +Unicode::Casing has been written to replace this feature without its +drawbacks, and the feature is scheduled to be removed in 5.16. +.IP 2. 4 +\&\fBquotemeta()\fR (and its in-line equivalent \f(CW\*(C`\eQ\*(C'\fR) can also give different +results depending on whether a string is encoded in UTF\-8. See +"The "Unicode Bug"" in perlunicode. +.RE +.RS 4 +.RE +.IP \(bu 4 +Handling of Unicode non-character code points has changed. +Previously they were mostly considered illegal, except that in some +place only one of the 66 of them was known. The Unicode Standard +considers them all legal, but forbids their "open interchange". +This is part of the change to allow internal use of any code +point (see "Core Enhancements"). Together, these changes resolve +[perl #38722], [perl #51918], [perl #51936], and [perl #63446]. +.IP \(bu 4 +Case-insensitive \f(CW"/i"\fR regular expression matching of Unicode +characters that match multiple characters now works much more as +intended. For example +.Sp +.Vb 1 +\& "\eN{LATIN SMALL LIGATURE FFI}" =~ /ffi/ui +.Ve +.Sp +and +.Sp +.Vb 1 +\& "ffi" =~ /\eN{LATIN SMALL LIGATURE FFI}/ui +.Ve +.Sp +are both true. Previously, there were many bugs with this feature. +What hasn't been fixed are the places where the pattern contains the +multiple characters, but the characters are split up by other things, +such as in +.Sp +.Vb 1 +\& "\eN{LATIN SMALL LIGATURE FFI}" =~ /(f)(f)i/ui +.Ve +.Sp +or +.Sp +.Vb 1 +\& "\eN{LATIN SMALL LIGATURE FFI}" =~ /ffi*/ui +.Ve +.Sp +or +.Sp +.Vb 1 +\& "\eN{LATIN SMALL LIGATURE FFI}" =~ /[a\-f][f\-m][g\-z]/ui +.Ve +.Sp +None of these match. +.Sp +Also, this matching doesn't fully conform to the current Unicode +Standard, which asks that the matching be made upon the NFD +(Normalization Form Decomposed) of the text. However, as of this +writing (April 2010), the Unicode Standard is currently in flux about +what they will recommend doing with regard in such scenarios. It may be +that they will throw out the whole concept of multi-character matches. +[perl #71736]. +.IP \(bu 4 +Naming a deprecated character in \f(CW\*(C`\eN{\fR\f(CINAME\fR\f(CW}\*(C'\fR no longer leaks memory. +.IP \(bu 4 +We fixed a bug that could cause \f(CW\*(C`\eN{\fR\f(CINAME\fR\f(CW}\*(C'\fR constructs followed by +a single \f(CW"."\fR to be parsed incorrectly [perl #74978] (5.12.1). +.IP \(bu 4 +\&\f(CW\*(C`chop\*(C'\fR now correctly handles characters above \f(CW"\ex{7fffffff}"\fR +[perl #73246]. +.IP \(bu 4 +Passing to \f(CW\*(C`index\*(C'\fR an offset beyond the end of the string when the string +is encoded internally in UTF8 no longer causes panics [perl #75898]. +.IP \(bu 4 +\&\fBwarn()\fR and \fBdie()\fR now respect utf8\-encoded scalars [perl #45549]. +.IP \(bu 4 +Sometimes the UTF8 length cache would not be reset on a value +returned by substr, causing \f(CW\*(C`length(substr($uni_string, ...))\*(C'\fR to give +wrong answers. With \f(CW\*(C`${^UTF8CACHE}\*(C'\fR set to \-1, it would also produce +a "panic" error message [perl #77692]. +.SS "Ties, Overloading and Other Magic" +.IX Subsection "Ties, Overloading and Other Magic" +.IP \(bu 4 +Overloading now works properly in conjunction with tied +variables. What formerly happened was that most ops checked their +arguments for overloading \fIbefore\fR checking for magic, so for example +an overloaded object returned by a tied array access would usually be +treated as not overloaded [RT #57012]. +.IP \(bu 4 +Various instances of magic (like tie methods) being called on tied variables +too many or too few times have been fixed: +.RS 4 +.IP \(bu 4 +\&\f(CW$tied\->()\fR did not always call FETCH [perl #8438]. +.IP \(bu 4 +Filetest operators and \f(CW\*(C`y///\*(C'\fR and \f(CW\*(C`tr///\*(C'\fR were calling FETCH too +many times. +.IP \(bu 4 +The \f(CW\*(C`=\*(C'\fR operator used to ignore magic on its right-hand side if the +scalar happened to hold a typeglob (if a typeglob was the last thing +returned from or assigned to a tied scalar) [perl #77498]. +.IP \(bu 4 +Dereference operators used to ignore magic if the argument was a +reference already (such as from a previous FETCH) [perl #72144]. +.IP \(bu 4 +\&\f(CW\*(C`splice\*(C'\fR now calls set-magic (so changes made +by \f(CW\*(C`splice @ISA\*(C'\fR are respected by method calls) [perl #78400]. +.IP \(bu 4 +In-memory files created by \f(CW\*(C`open($fh, ">", \e$buffer)\*(C'\fR were not calling +FETCH/STORE at all [perl #43789] (5.12.2). +.IP \(bu 4 +\&\fButf8::is_utf8()\fR now respects get-magic (like \f(CW$1\fR) (5.12.1). +.RE +.RS 4 +.RE +.IP \(bu 4 +Non-commutative binary operators used to swap their operands if the same +tied scalar was used for both operands and returned a different value for +each FETCH. For instance, if \f(CW$t\fR returned 2 the first time and 3 the +second, then \f(CW\*(C`$t/$t\*(C'\fR would evaluate to 1.5. This has been fixed +[perl #87708]. +.IP \(bu 4 +String \f(CW\*(C`eval\*(C'\fR now detects taintedness of overloaded or tied +arguments [perl #75716]. +.IP \(bu 4 +String \f(CW\*(C`eval\*(C'\fR and regular expression matches against objects with string +overloading no longer cause memory corruption or crashes [perl #77084]. +.IP \(bu 4 +readline now honors \f(CW\*(C`<>\*(C'\fR overloading on tied +arguments. +.IP \(bu 4 +\&\f(CW\*(C`\*(C'\fR always respects overloading now if the expression is +overloaded. +.Sp +Because "<>\ as glob" was parsed differently from +"<>\ as filehandle" from 5.6 onwards, something like \f(CW\*(C`<$foo[0]>\*(C'\fR did +not handle overloading, even if \f(CW$foo[0]\fR was an overloaded object. This +was contrary to the documentation for overload, and meant that \f(CW\*(C`<>\*(C'\fR +could not be used as a general overloaded iterator operator. +.IP \(bu 4 +The fallback behaviour of overloading on binary operators was asymmetric +[perl #71286]. +.IP \(bu 4 +Magic applied to variables in the main package no longer affects other packages. +See "Magic variables outside the main package" above [perl #76138]. +.IP \(bu 4 +Sometimes magic (ties, taintedness, etc.) attached to variables could cause +an object to last longer than it should, or cause a crash if a tied +variable were freed from within a tie method. These have been fixed +[perl #81230]. +.IP \(bu 4 +DESTROY methods of objects implementing ties are no longer able to crash by +accessing the tied variable through a weak reference [perl #86328]. +.IP \(bu 4 +Fixed a regression of \fBkill()\fR when a match variable is used for the +process ID to kill [perl #75812]. +.IP \(bu 4 +\&\f(CW$AUTOLOAD\fR used to remain tainted forever if it ever became tainted. Now +it is correctly untainted if an autoloaded method is called and the method +name was not tainted. +.IP \(bu 4 +\&\f(CW\*(C`sprintf\*(C'\fR now dies when passed a tainted scalar for the format. It did +already die for arbitrary expressions, but not for simple scalars +[perl #82250]. +.IP \(bu 4 +\&\f(CW\*(C`lc\*(C'\fR, \f(CW\*(C`uc\*(C'\fR, \f(CW\*(C`lcfirst\*(C'\fR, and \f(CW\*(C`ucfirst\*(C'\fR no longer return untainted strings +when the argument is tainted. This has been broken since perl 5.8.9 +[perl #87336]. +.SS "The Debugger" +.IX Subsection "The Debugger" +.IP \(bu 4 +The Perl debugger now also works in taint mode [perl #76872]. +.IP \(bu 4 +Subroutine redefinition works once more in the debugger [perl #48332]. +.IP \(bu 4 +When \fB\-d\fR is used on the shebang (\f(CW\*(C`#!\*(C'\fR) line, the debugger now has access +to the lines of the main program. In the past, this sometimes worked and +sometimes did not, depending on the order in which things happened to be +arranged in memory [perl #71806]. +.IP \(bu 4 +A possible memory leak when using \fBcaller()\fR to set +\&\f(CW@DB::args\fR has been fixed (5.12.2). +.IP \(bu 4 +Perl no longer stomps on \f(CW$DB::single\fR, \f(CW$DB::trace\fR, and \f(CW$DB::signal\fR +if these variables already have values when \f(CW$^P\fR is assigned to [perl #72422]. +.IP \(bu 4 +\&\f(CW\*(C`#line\*(C'\fR directives in string evals were not properly updating the arrays +of lines of code (\f(CW\*(C`@{"_< ..."}\*(C'\fR) that the debugger (or any debugging or +profiling module) uses. In threaded builds, they were not being updated at +all. In non-threaded builds, the line number was ignored, so any change to +the existing line number would cause the lines to be misnumbered +[perl #79442]. +.SS Threads +.IX Subsection "Threads" +.IP \(bu 4 +Perl no longer accidentally clones lexicals in scope within active stack +frames in the parent when creating a child thread [perl #73086]. +.IP \(bu 4 +Several memory leaks in cloning and freeing threaded Perl interpreters have been +fixed [perl #77352]. +.IP \(bu 4 +Creating a new thread when directory handles were open used to cause a +crash, because the handles were not cloned, but simply passed to the new +thread, resulting in a double free. +.Sp +Now directory handles are cloned properly on Windows +and on systems that have a \f(CW\*(C`fchdir\*(C'\fR function. On other +systems, new threads simply do not inherit directory +handles from their parent threads [perl #75154]. +.IP \(bu 4 +The typeglob \f(CW\*(C`*,\*(C'\fR, which holds the scalar variable \f(CW$,\fR (output field +separator), had the wrong reference count in child threads. +.IP \(bu 4 +[perl #78494] When pipes are shared between threads, the \f(CW\*(C`close\*(C'\fR function +(and any implicit close, such as on thread exit) no longer blocks. +.IP \(bu 4 +Perl now does a timely cleanup of SVs that are cloned into a new +thread but then discovered to be orphaned (that is, their owners +are \fInot\fR cloned). This eliminates several "scalars leaked" +warnings when joining threads. +.SS "Scoping and Subroutines" +.IX Subsection "Scoping and Subroutines" +.IP \(bu 4 +Lvalue subroutines are again able to return copy-on-write scalars. This +had been broken since version 5.10.0 [perl #75656] (5.12.3). +.IP \(bu 4 +\&\f(CW\*(C`require\*(C'\fR no longer causes \f(CW\*(C`caller\*(C'\fR to return the wrong file name for +the scope that called \f(CW\*(C`require\*(C'\fR and other scopes higher up that had the +same file name [perl #68712]. +.IP \(bu 4 +\&\f(CW\*(C`sort\*(C'\fR with a \f(CW\*(C`($$)\*(C'\fR\-prototyped comparison routine used to cause the value +of \f(CW@_\fR to leak out of the sort. Taking a reference to \f(CW@_\fR within the +sorting routine could cause a crash [perl #72334]. +.IP \(bu 4 +Match variables (like \f(CW$1\fR) no longer persist between calls to a sort +subroutine [perl #76026]. +.IP \(bu 4 +Iterating with \f(CW\*(C`foreach\*(C'\fR over an array returned by an lvalue sub now works +[perl #23790]. +.IP \(bu 4 +\&\f(CW$@\fR is now localised during calls to \f(CW\*(C`binmode\*(C'\fR to prevent action at a +distance [perl #78844]. +.IP \(bu 4 +Calling a closure prototype (what is passed to an attribute handler for a +closure) now results in a "Closure prototype called" error message instead +of a crash [perl #68560]. +.IP \(bu 4 +Mentioning a read-only lexical variable from the enclosing scope in a +string \f(CW\*(C`eval\*(C'\fR no longer causes the variable to become writable +[perl #19135]. +.SS Signals +.IX Subsection "Signals" +.IP \(bu 4 +Within signal handlers, \f(CW$!\fR is now implicitly localized. +.IP \(bu 4 +CHLD signals are no longer unblocked after a signal handler is called if +they were blocked before by \f(CW\*(C`POSIX::sigprocmask\*(C'\fR [perl #82040]. +.IP \(bu 4 +A signal handler called within a signal handler could cause leaks or +double-frees. Now fixed [perl #76248]. +.SS "Miscellaneous Memory Leaks" +.IX Subsection "Miscellaneous Memory Leaks" +.IP \(bu 4 +Several memory leaks when loading XS modules were fixed (5.12.2). +.IP \(bu 4 +\&\fBsubstr()\fR, +\&\fBpos()\fR, \fBkeys()\fR, +and \fBvec()\fR could, when used in combination +with lvalues, result in leaking the scalar value they operate on, and cause its +destruction to happen too late. This has now been fixed. +.IP \(bu 4 +The postincrement and postdecrement operators, \f(CW\*(C`++\*(C'\fR and \f(CW\*(C`\-\-\*(C'\fR, used to cause +leaks when used on references. This has now been fixed. +.IP \(bu 4 +Nested \f(CW\*(C`map\*(C'\fR and \f(CW\*(C`grep\*(C'\fR blocks no longer leak memory when processing +large lists [perl #48004]. +.IP \(bu 4 +\&\f(CW\*(C`use \fR\f(CIVERSION\fR\f(CW\*(C'\fR and \f(CW\*(C`no \fR\f(CIVERSION\fR\f(CW\*(C'\fR no longer leak memory [perl #78436] +[perl #69050]. +.IP \(bu 4 +\&\f(CW\*(C`.=\*(C'\fR followed by \f(CW\*(C`<>\*(C'\fR or \f(CW\*(C`readline\*(C'\fR would leak memory if \f(CW$/\fR +contained characters beyond the octet range and the scalar assigned to +happened to be encoded as UTF8 internally [perl #72246]. +.IP \(bu 4 +\&\f(CW\*(C`eval \*(AqBEGIN{die}\*(Aq\*(C'\fR no longer leaks memory on non-threaded builds. +.SS "Memory Corruption and Crashes" +.IX Subsection "Memory Corruption and Crashes" +.IP \(bu 4 +\&\fBglob()\fR no longer crashes when \f(CW%File::Glob::\fR is empty and +\&\f(CW\*(C`CORE::GLOBAL::glob\*(C'\fR isn't present [perl #75464] (5.12.2). +.IP \(bu 4 +\&\fBreadline()\fR has been fixed when interrupted by signals so it no longer +returns the "same thing" as before or random memory. +.IP \(bu 4 +When assigning a list with duplicated keys to a hash, the assignment used to +return garbage and/or freed values: +.Sp +.Vb 1 +\& @a = %h = (list with some duplicate keys); +.Ve +.Sp +This has now been fixed [perl #31865]. +.IP \(bu 4 +The mechanism for freeing objects in globs used to leave dangling +pointers to freed SVs, meaning Perl users could see corrupted state +during destruction. +.Sp +Perl now frees only the affected slots of the GV, rather than freeing +the GV itself. This makes sure that there are no dangling refs or +corrupted state during destruction. +.IP \(bu 4 +The interpreter no longer crashes when freeing deeply-nested arrays of +arrays. Hashes have not been fixed yet [perl #44225]. +.IP \(bu 4 +Concatenating long strings under \f(CW\*(C`use encoding\*(C'\fR no longer causes Perl to +crash [perl #78674]. +.IP \(bu 4 +Calling \f(CW\*(C`\->import\*(C'\fR on a class lacking an import method could corrupt +the stack, resulting in strange behaviour. For instance, +.Sp +.Vb 1 +\& push @a, "foo", $b = bar\->import; +.Ve +.Sp +would assign "foo" to \f(CW$b\fR [perl #63790]. +.IP \(bu 4 +The \f(CW\*(C`recv\*(C'\fR function could crash when called with the MSG_TRUNC flag +[perl #75082]. +.IP \(bu 4 +\&\f(CW\*(C`formline\*(C'\fR no longer crashes when passed a tainted format picture. It also +taints \f(CW$^A\fR now if its arguments are tainted [perl #79138]. +.IP \(bu 4 +A bug in how we process filetest operations could cause a segfault. +Filetests don't always expect an op on the stack, so we now use +TOPs only if we're sure that we're not \f(CW\*(C`stat\*(C'\fRing the \f(CW\*(C`_\*(C'\fR filehandle. +This is indicated by \f(CW\*(C`OPf_KIDS\*(C'\fR (as checked in ck_ftst) [perl #74542] +(5.12.1). +.IP \(bu 4 +\&\fBunpack()\fR now handles scalar context correctly for \f(CW%32H\fR and \f(CW%32u\fR, +fixing a potential crash. \fBsplit()\fR would crash because the third item +on the stack wasn't the regular expression it expected. \f(CW\*(C`unpack("%2H", +\&...)\*(C'\fR would return both the unpacked result and the checksum on the stack, +as would \f(CW\*(C`unpack("%2u", ...)\*(C'\fR [perl #73814] (5.12.2). +.SS "Fixes to Various Perl Operators" +.IX Subsection "Fixes to Various Perl Operators" +.IP \(bu 4 +The \f(CW\*(C`&\*(C'\fR, \f(CW\*(C`|\*(C'\fR, and \f(CW\*(C`^\*(C'\fR bitwise operators no longer coerce read-only arguments +[perl #20661]. +.IP \(bu 4 +Stringifying a scalar containing "\-0.0" no longer has the effect of turning +false into true [perl #45133]. +.IP \(bu 4 +Some numeric operators were converting integers to floating point, +resulting in loss of precision on 64\-bit platforms [perl #77456]. +.IP \(bu 4 +\&\fBsprintf()\fR was ignoring locales when called with constant arguments +[perl #78632]. +.IP \(bu 4 +Combining the vector (\f(CW%v\fR) flag and dynamic precision would +cause \f(CW\*(C`sprintf\*(C'\fR to confuse the order of its arguments, making it +treat the string as the precision and vice-versa [perl #83194]. +.SS "Bugs Relating to the C API" +.IX Subsection "Bugs Relating to the C API" +.IP \(bu 4 +The C\-level \f(CW\*(C`lex_stuff_pvn\*(C'\fR function would sometimes cause a spurious +syntax error on the last line of the file if it lacked a final semicolon +[perl #74006] (5.12.1). +.IP \(bu 4 +The \f(CW\*(C`eval_sv\*(C'\fR and \f(CW\*(C`eval_pv\*(C'\fR C functions now set \f(CW$@\fR correctly when +there is a syntax error and no \f(CW\*(C`G_KEEPERR\*(C'\fR flag, and never set it if the +\&\f(CW\*(C`G_KEEPERR\*(C'\fR flag is present [perl #3719]. +.IP \(bu 4 +The XS multicall API no longer causes subroutines to lose reference counts +if called via the multicall interface from within those very subroutines. +This affects modules like List::Util. Calling one of its functions with an +active subroutine as the first argument could cause a crash [perl #78070]. +.IP \(bu 4 +The \f(CW\*(C`SvPVbyte\*(C'\fR function available to XS modules now calls magic before +downgrading the SV, to avoid warnings about wide characters [perl #72398]. +.IP \(bu 4 +The ref types in the typemap for XS bindings now support magical variables +[perl #72684]. +.IP \(bu 4 +\&\f(CW\*(C`sv_catsv_flags\*(C'\fR no longer calls \f(CW\*(C`mg_get\*(C'\fR on its second argument (the +source string) if the flags passed to it do not include SV_GMAGIC. So it +now matches the documentation. +.IP \(bu 4 +\&\f(CW\*(C`my_strftime\*(C'\fR no longer leaks memory. This fixes a memory leak in +\&\f(CW\*(C`POSIX::strftime\*(C'\fR [perl #73520]. +.IP \(bu 4 +\&\fIXSUB.h\fR now correctly redefines fgets under PERL_IMPLICIT_SYS [perl #55049] +(5.12.1). +.IP \(bu 4 +XS code using \fBfputc()\fR or \fBfputs()\fR on Windows could cause an error +due to their arguments being swapped [perl #72704] (5.12.1). +.IP \(bu 4 +A possible segfault in the \f(CW\*(C`T_PTROBJ\*(C'\fR default typemap has been fixed +(5.12.2). +.IP \(bu 4 +A bug that could cause "Unknown error" messages when +\&\f(CW\*(C`call_sv(code, G_EVAL)\*(C'\fR is called from an XS destructor has been fixed +(5.12.2). +.SH "Known Problems" +.IX Header "Known Problems" +This is a list of significant unresolved issues which are regressions +from earlier versions of Perl or which affect widely-used CPAN modules. +.IP \(bu 4 +\&\f(CW\*(C`List::Util::first\*(C'\fR misbehaves in the presence of a lexical \f(CW$_\fR +(typically introduced by \f(CW\*(C`my $_\*(C'\fR or implicitly by \f(CW\*(C`given\*(C'\fR). The variable +that gets set for each iteration is the package variable \f(CW$_\fR, not the +lexical \f(CW$_\fR. +.Sp +A similar issue may occur in other modules that provide functions which +take a block as their first argument, like +.Sp +.Vb 1 +\& foo { ... $_ ...} list +.Ve +.Sp +See also: +.IP \(bu 4 +\&\fBreadline()\fR returns an empty string instead of a cached previous value +when it is interrupted by a signal +.IP \(bu 4 +The changes in prototype handling break Switch. A patch has been sent +upstream and will hopefully appear on CPAN soon. +.IP \(bu 4 +The upgrade to \fIExtUtils\-MakeMaker\-6.57_05\fR has caused +some tests in the \fIModule-Install\fR distribution on CPAN to +fail. (Specifically, \fI02_mymeta.t\fR tests 5 and 21; \fI18_all_from.t\fR +tests 6 and 15; \fI19_authors.t\fR tests 5, 13, 21, and 29; and +\&\fI20_authors_with_special_characters.t\fR tests 6, 15, and 23 in version +1.00 of that distribution now fail.) +.IP \(bu 4 +On VMS, \f(CW\*(C`Time::HiRes\*(C'\fR tests will fail due to a bug in the CRTL's +implementation of \f(CW\*(C`setitimer\*(C'\fR: previous timer values would be cleared +if a timer expired but not if the timer was reset before expiring. HP +OpenVMS Engineering have corrected the problem and will release a patch +in due course (Quix case # QXCM1001115136). +.IP \(bu 4 +On VMS, there were a handful of \f(CW\*(C`Module::Build\*(C'\fR test failures we didn't +get to before the release; please watch CPAN for updates. +.SH Errata +.IX Header "Errata" +.SS "\fBkeys()\fP, \fBvalues()\fP, and \fBeach()\fP work on arrays" +.IX Subsection "keys(), values(), and each() work on arrays" +You can now use the \fBkeys()\fR, \fBvalues()\fR, and \fBeach()\fR builtins on arrays; +previously you could use them only on hashes. See perlfunc for details. +This is actually a change introduced in perl 5.12.0, but it was missed from +that release's perl5120delta. +.ie n .SS "\fBsplit()\fP and @_" +.el .SS "\fBsplit()\fP and \f(CW@_\fP" +.IX Subsection "split() and @_" +\&\fBsplit()\fR no longer modifies \f(CW@_\fR when called in scalar or void context. +In void context it now produces a "Useless use of split" warning. +This was also a perl 5.12.0 change that missed the perldelta. +.SH Obituary +.IX Header "Obituary" +Randy Kobes, creator of http://kobesearch.cpan.org/ and +contributor/maintainer to several core Perl toolchain modules, passed +away on September 18, 2010 after a battle with lung cancer. The community +was richer for his involvement. He will be missed. +.SH Acknowledgements +.IX Header "Acknowledgements" +Perl 5.14.0 represents one year of development since +Perl 5.12.0 and contains nearly 550,000 lines of changes across nearly +3,000 files from 150 authors and committers. +.PP +Perl continues to flourish into its third decade thanks to a vibrant +community of users and developers. The following people are known to +have contributed the improvements that became Perl 5.14.0: +.PP +Aaron Crane, Abhijit Menon-Sen, Abigail, Ævar Arnfjörð Bjarmason, +Alastair Douglas, Alexander Alekseev, Alexander Hartmaier, Alexandr +Ciornii, Alex Davies, Alex Vandiver, Ali Polatel, Allen Smith, Andreas +König, Andrew Rodland, Andy Armstrong, Andy Dougherty, Aristotle +Pagaltzis, Arkturuz, Arvan, A. Sinan Unur, Ben Morrow, Bo Lindbergh, +Boris Ratner, Brad Gilbert, Bram, brian d foy, Brian Phillips, Casey +West, Charles Bailey, Chas. Owens, Chip Salzenberg, Chris 'BinGOs' +Williams, chromatic, Craig A. Berry, Curtis Jewell, Dagfinn Ilmari +Mannsåker, Dan Dascalescu, Dave Rolsky, David Caldwell, David Cantrell, +David Golden, David Leadbeater, David Mitchell, David Wheeler, Eric +Brine, Father Chrysostomos, Fingle Nark, Florian Ragwitz, Frank Wiegand, +Franz Fasching, Gene Sullivan, George Greer, Gerard Goossen, Gisle Aas, +Goro Fuji, Grant McLean, gregor herrmann, H.Merijn Brand, Hongwen Qiu, +Hugo van der Sanden, Ian Goodacre, James E Keenan, James Mastros, Jan +Dubois, Jay Hannah, Jerry D. Hedden, Jesse Vincent, Jim Cromie, Jirka +Hruška, John Peacock, Joshua ben Jore, Joshua Pritikin, Karl Williamson, +Kevin Ryde, kmx, Lars Dɪᴇᴄᴋᴏᴡ 迪拉斯, Larwan Berke, Leon Brocard, Leon +Timmermans, Lubomir Rintel, Lukas Mai, Maik Hentsche, Marty Pauley, +Marvin Humphrey, Matt Johnson, Matt S Trout, Max Maischein, Michael +Breen, Michael Fig, Michael G Schwern, Michael Parker, Michael Stevens, +Michael Witten, Mike Kelly, Moritz Lenz, Nicholas Clark, Nick Cleaton, +Nick Johnston, Nicolas Kaiser, Niko Tyni, Noirin Shirley, Nuno Carvalho, +Paul Evans, Paul Green, Paul Johnson, Paul Marquess, Peter J. Holzer, +Peter John Acklam, Peter Martini, Philippe Bruhat (BooK), Piotr Fusik, +Rafael Garcia-Suarez, Rainer Tammer, Reini Urban, Renee Baecker, Ricardo +Signes, Richard Möhn, Richard Soderberg, Rob Hoelz, Robin Barker, Ruslan +Zakirov, Salvador Fandiño, Salvador Ortiz Garcia, Shlomi Fish, Sinan +Unur, Sisyphus, Slaven Rezic, Steffen Müller, Steve Hay, Steven +Schubiger, Steve Peters, Sullivan Beck, Tatsuhiko Miyagawa, Tim Bunce, +Todd Rinaldo, Tom Christiansen, Tom Hukins, Tony Cook, Tye McQueen, +Vadim Konovalov, Vernon Lyon, Vincent Pit, Walt Mankowski, Wolfram +Humann, Yves Orton, Zefram, and Zsbán Ambrus. +.PP +This is woefully incomplete as it's automatically generated from version +control history. In particular, it doesn't include the names of the +(very much appreciated) contributors who reported issues in previous +versions of Perl that helped make Perl 5.14.0 better. For a more complete +list of all of Perl's historical contributors, please see the \f(CW\*(C`AUTHORS\*(C'\fR +file in the Perl 5.14.0 distribution. +.PP +Many of the changes included in this version originated in the CPAN +modules included in Perl's core. We're grateful to the entire CPAN +community for helping Perl to flourish. +.SH "Reporting Bugs" +.IX Header "Reporting Bugs" +If you find what you think is a bug, you might check the articles +recently posted to the comp.lang.perl.misc newsgroup and the Perl +bug database at http://rt.perl.org/perlbug/ . There may also be +information at http://www.perl.org/ , the Perl Home Page. +.PP +If you believe you have an unreported bug, please run the perlbug +program included with your release. Be sure to trim your bug down +to a tiny but sufficient test case. Your bug report, along with the +output of \f(CW\*(C`perl \-V\*(C'\fR, will be sent off to perlbug@perl.org to be +analysed by the Perl porting team. +.PP +If the bug you are reporting has security implications, which make it +inappropriate to send to a publicly archived mailing list, then please send +it to perl5\-security\-report@perl.org. This points to a closed subscription +unarchived mailing list, which includes all the core committers, who are able +to help assess the impact of issues, figure out a resolution, and help +co-ordinate the release of patches to mitigate or fix the problem across all +platforms on which Perl is supported. Please use this address for +security issues in the Perl core \fIonly\fR, not for modules independently +distributed on CPAN. +.SH "SEE ALSO" +.IX Header "SEE ALSO" +The \fIChanges\fR file for an explanation of how to view exhaustive details +on what changed. +.PP +The \fIINSTALL\fR file for how to build Perl. +.PP +The \fIREADME\fR file for general stuff. +.PP +The \fIArtistic\fR and \fICopying\fR files for copyright information. -- cgit v1.2.3