2011年5月17日

[installer 2802] perl-5.14.0

perl-5.14.0 出ています。

☆ perl-5.14.0
http://www.perl.com/CPAN/src/
http://www.cpan.org/src/perl-5.14.0.tar.gz

NAME
perldelta - what is new for perl v5.14.0


DESCRIPTION
This document describes differences between the 5.12.0 release and the
5.14.0 release.

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.

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.

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.

Core Enhancements
Unicode
Unicode Version 6.0 is now supported (mostly)
Perl comes with the Unicode 6.0 data base updated with Corrigendum #8,
with one exception noted below. See
< http://unicode.org/versions/Unicode6.0.0/>; for details on the new
release. Perl does not support any Unicode provisional properties,
including the new ones for this release.

Unicode 6.0 has chosen to use the name "BELL" 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 "BELL" mean the ASCII "BEL" character, U+0007. In Perl 5.14,
"\N{BELL}" 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 "ALERT", which corresponds nicely with the existing
shorthand sequence for it, "\a". "\N{BEL}" means U+0007, with no warning
given. The character at U+1F514 has no name in 5.14, but can be referred
to by "\N{U+1F514}". In Perl 5.16, "\N{BELL}" will refer to U+1F514; all
code that uses "\N{BELL}" should be converted to use "\N{ALERT}",
"\N{BEL}", or "\a" before upgrading.

Full functionality for "use feature 'unicode_strings'"
This release provides full functionality for "use feature
'unicode_strings'". 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.

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 *strongly* encouraged to use
this subpragma to avoid nasty surprises.

"\N{*NAME*}" and "charnames" enhancements
* "\N{*NAME*}" and "charnames::vianame" 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.

* Unicode has several *named character sequences*, in which particular
sequences of code points are given names. "\N{*NAME*}" now
recognizes these.

* "\N{*NAME*}", "charnames::vianame", and "charnames::viacode" 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.

* It is now possible to override Perl's abbreviations with your own
custom aliases.

* You can now create a custom alias of the ordinal of a character,
known by "\N{*NAME*}", "charnames::vianame()", and
"charnames::viacode()". 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.

* The new function charnames::string_vianame() is a run-time version
of "\N{*NAME*}}", returning the string of characters whose Unicode
name is its parameter. It can handle Unicode named character
sequences, whereas the pre-existing charnames::vianame() cannot, as
the latter returns a single code point.

See charnames for details on all these changes.

New warnings categories for problematic (non-)Unicode code points.
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: "surrogate" when UTF-16 surrogates
are encountered; "nonchar" when Unicode non-character code points are
encountered; and "non_unicode" when code points above the legal Unicode
maximum of 0x10FFFF are encountered.

Any unsigned value can be encoded as a character
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 ":encoding(UTF-8)" layer) will continue to fail.
Prior to this release, handling was inconsistent and in places,
incorrect.

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".

Unicode database files not installed
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
< http://www.unicode.org/Public/zipped/6.0.0/>;.

Regular Expressions
"(?^...)" construct signifies default modifiers
An ASCII caret "^" immediately following a "(?" in a regular expression
now means that the subexpression does not inherit surrounding modifiers
such as "/i", but reverts to the Perl defaults. Any modifiers following
the caret override the defaults.

Stringification of regular expressions now uses this notation. For
example, "qr/hlagh/i" would previously be stringified as
"(?i-xsm:hlagh)", but now it's stringified as "(?^i:hlagh)".

The main purpose of this change is to allow tests that rely on the
stringification *not* to have to change whenever new modifiers are
added. See "Extended Patterns" in perlre.

This change is likely to break code that compares stringified regular
expressions with fixed strings containing "?-xism".

"/d", "/l", "/u", and "/a" modifiers
Four new regular expression modifiers have been added. These are
mutually exclusive: one only can be turned on at a time.

* The "/l" modifier says to compile the regular expression as if it
were in the scope of "use locale", even if it is not.

* The "/u" modifier says to compile the regular expression as if it
were in the scope of a "use feature 'unicode_strings'" pragma.

* The "/d" (default) modifier is used to override any "use locale" and
"use feature 'unicode_strings'" pragmas in effect at the time of
compiling the regular expression.

* The "/a" regular expression modifier restricts "\s", "\d" and "\w"
and the POSIX ("[[:posix:]]") character classes to the ASCII range.
Their complements and "\b" and "\B" are correspondingly affected.
Otherwise, "/a" behaves like the "/u" modifier, in that
case-insensitive matching uses Unicode semantics.

If the "/a" modifier is repeated, then additionally in
case-insensitive matching, no ASCII character can match a non-ASCII
character. For example,

"k" =~ /\N{KELVIN SIGN}/ai
"\xDF" =~ /ss/ai

match but

"k" =~ /\N{KELVIN SIGN}/aai
"\xDF" =~ /ss/aai

do not match.

See "Modifiers" in perlre for more detail.

Non-destructive substitution
The substitution ("s///") and transliteration ("y///") operators now
support an "/r" option that copies the input variable, carries out the
substitution on the copy, and returns the result. The original remains
unmodified.

my $old = "cat";
my $new = $old =~ s/cat/dog/r;
# $old is "cat" and $new is "dog"

This is particularly useful with "map". See perlop for more examples.

Re-entrant regular expression engine
It is now safe to use regular expressions within "(?{...})" and
"(??{...})" code blocks inside regular expressions.

These blocks are still experimental, however, and still have problems
with lexical ("my") variables and abnormal exiting.

"use re '/flags'"
The "re" pragma now has the ability to turn on regular expression flags
till the end of the lexical scope:

use re "/x";
"foo" =~ / (.+) /; # /x implied

See "'/flags' mode" in re for details.

\o{...} for octals
There is a new octal escape sequence, "\o", 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.

Add "\p{Titlecase}" as a synonym for "\p{Title}"
This synonym is added for symmetry with the Unicode property names
"\p{Uppercase}" and "\p{Lowercase}".

Regular expression debugging output improvement
Regular expression debugging output (turned on by "use re 'debug'") now
uses hexadecimal when escaping non-ASCII characters, instead of octal.

Return value of "delete $+{...}"
Custom regular expression engines can now determine the return value of
"delete" on an entry of "%+" or "%-".

Syntactical Enhancements
Array and hash container functions accept references
Warning: This feature is considered experimental, as the exact behaviour
may change in a future version of Perl.

All builtin functions that operate directly on array or hash containers
now also accept unblessed hard references to arrays or hashes:

|----------------------------+---------------------------|
| 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 |
|----------------------------+---------------------------|

This allows these builtin functions to act on long dereferencing chains
or on the return value of subroutines without needing to wrap them in
"@{}" or "%{}":

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

Single term prototype
The "+" prototype is a special alternative to "$" that acts like "\[@%]"
when given a literal array or hash variable, but will otherwise force
scalar context on the argument. See "Prototypes" in perlsub.

"package" block syntax
A package declaration can now contain a code block, in which case the
declaration is in scope inside that block only. So "package Foo { ... }"
is precisely equivalent to "{ package Foo; ... }". It also works with a
version number in the declaration, as in "package Foo 1.2 { ... }",
which is its most attractive feature. See perlfunc.

Statement labels can appear in more places
Statement labels can now occur before any type of statement or
declaration, such as "package".

Stacked labels
Multiple statement labels can now appear before a single statement.

Uppercase X/B allowed in hexadecimal/binary literals
Literals may now use either upper case "0X..." or "0B..." prefixes, in
addition to the already supported "0x..." and "0b..." syntax [perl
#76296].

C, Ruby, Python, and PHP already support this syntax, and it makes Perl
more internally consistent: a round-trip with "eval sprintf "%#X", 0x10"
now returns 16, just like "eval sprintf "%#x", 0x10".

Overridable tie functions
"tie", "tied" and "untie" can now be overridden [perl #75902].

Exception Handling
To make them more reliable and consistent, several changes have been
made to how "die", "warn", and $@ behave.

* When an exception is thrown inside an "eval", the exception is no
longer at risk of being clobbered by destructor code running during
unwinding. Previously, the exception was written into $@ early in
the throwing process, and would be overwritten if "eval" was used
internally in the destructor for an object that had to be freed
while exiting from the outer "eval". Now the exception is written
into $@ last thing before exiting the outer "eval", so the code
running immediately thereafter can rely on the value in $@ correctly
corresponding to that "eval". ($@ is still also set before exiting
the "eval", for the sake of destructors that rely on this.)

Likewise, a "local $@" inside an "eval" no longer clobbers any
exception thrown in its scope. Previously, the restoration of $@
upon unwinding would overwrite any exception being thrown. Now the
exception gets to the "eval" anyway. So "local $@" is safe before a
"die".

Exceptions thrown from object destructors no longer modify the $@ 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 $@
or completely replaced the surrounding $@, depending on whether that
exception and the surrounding $@ were strings or objects. Now, an
exception in this situation is always emitted as a warning, leaving
the surrounding $@ untouched. In addition to object destructors,
this also affects any function call run by XS code using the
"G_KEEPERR" flag.

* Warnings for "warn" can now be objects in the same way as exceptions
for "die". 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 $SIG{__WARN__} handler now
receives an object-based warning as an object, where previously it
was passed the result of stringifying the object.

Other Enhancements
Assignment to $0 sets the legacy process name with prctl() on Linux
On Linux the legacy process name is now set with prctl(2), in addition
to altering the POSIX name via "argv[0]", as Perl has done since version
4.000. Now system utilities that read the legacy process name such as
*ps*, *top*, and *killall* recognize the name you set when assigning to
$0. The string you supply is truncated at 16 bytes; this limitation is
imposed by Linux.

srand() now returns the seed
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
srand() 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.

printf-like functions understand post-1980 size modifiers
Perl's printf and sprintf operators, and Perl's internal printf
replacement function, now understand the C90 size modifiers "hh"
("char"), "z" ("size_t"), and "t" ("ptrdiff_t"). Also, when compiled
with a C99 compiler, Perl now understands the size modifier "j"
("intmax_t") (but this is not portable).

So, for example, on any modern machine, "sprintf("%hhd", 257)" returns
"1".

New global variable "${^GLOBAL_PHASE}"
A new global variable, "${^GLOBAL_PHASE}", 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.

"-d:-foo" calls "Devel::foo::unimport"
The syntax -d:foo was extended in 5.6.1 to make -d:foo=bar equivalent to
-MDevel::foo=bar, which expands internally to "use Devel::foo 'bar'".
Perl now allows prefixing the module name with -, with the same
semantics as -M; that is:

"-d:-foo"
Equivalent to -M-Devel::foo: expands to "no Devel::foo" and calls
"Devel::foo->unimport()" if that method exists.

"-d:-foo=bar"
Equivalent to -M-Devel::foo=bar: expands to "no Devel::foo 'bar'",
and calls "Devel::foo->unimport("bar")" if that method exists.

This is particularly useful for suppressing the default actions of a
"Devel::*" module's "import" method whilst still loading it for
debugging.

Filehandle method calls load IO::File on demand
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 "require" and attempts method resolution again:

open my $fh, ">", $file;
$fh->binmode(":raw"); # loads IO::File and succeeds

This also works for globs like "STDOUT", "STDERR", and "STDIN":

STDOUT->autoflush(1);

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:

use IO::Handle;
open my $fh, ">", $file;
$fh->autoflush(1); # IO::File not loaded

Improved IPv6 support
The "Socket" module provides new affordances for IPv6, including
implementations of the "Socket::getaddrinfo()" and
"Socket::getnameinfo()" functions, along with related constants and a
handful of new functions. See Socket.

DTrace probes now include package name
The "DTrace" probes now include an additional argument, "arg3", which
contains the package the subroutine being entered or left was compiled
in.

For example, using the following DTrace script:

perl$target:::sub-entry
{
printf("%s::%s\n", copyinstr(arg0), copyinstr(arg3));
}

and then running:

$ perl -e 'sub test { }; test'

"DTrace" will print:

main::test

New C APIs
See "Internal Changes".

Security
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 "\p{foo::bar}" could call foo::bar() if it existed. The
documented convention is now enforced.

Also, Perl no longer allows tainted regular expressions to invoke a
user-defined property. It simply dies instead [perl #82616].

Incompatible Changes
Perl 5.14.0 is not binary-compatible with any previous stable release.

In addition to the sections that follow, see "C API Changes".

Regular Expressions and String Escapes
Inverted bracketed character classes and multi-character folds
Some characters match a sequence of two or three characters in "/i"
regular expression matching under Unicode rules. One example is "LATIN
SMALL LETTER SHARP S" which matches the sequence "ss".

'ss' =~ /\A[\N{LATIN SMALL LETTER SHARP S}]\z/i # Matches

This, however, can lead to very counter-intuitive results, especially
when inverted. Because of this, Perl 5.14 does not use multi-character
"/i" matching in inverted character classes.

'ss' =~ /\A[^\N{LATIN SMALL LETTER SHARP S}]+\z/i # ???

This should match any sequences of characters that aren't the "SHARP S"
nor what "SHARP S" matches under "/i". "s" isn't "SHARP S", but Unicode
says that "ss" is what "SHARP S" matches under "/i". So which one
"wins"? Do you fail the match because the string has "ss" or accept it
because it has an "s" followed by another "s"?

Earlier releases of Perl did allow this multi-character matching, but
due to bugs, it mostly did not work.

\400-\777
In certain circumstances, "\400"-"\777" 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 "\x{100}"-"\x{1FF}", with no deprecation
warning.

Use of "\400"-"\777" in the command-line option -0 retain their
conventional meaning. They slurp whole input files; previously, this was
documented only for -0777.

Because of various ambiguities, you should use the new "\o{...}"
construct to represent characters in octal instead.

Most "\p{}" properties are now immune to case-insensitive matching
For most Unicode properties, it doesn't make sense to have them match
differently under "/i" case-insensitive matching. Doing so can lead to
unexpected results and potential security holes. For example

m/\p{ASCII_Hex_Digit}+/i

could previously match non-ASCII characters because of the Unicode
matching rules (although there were several bugs with this). Now
matching under "/i" gives the same results as non-"/i" 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 "m/\p{Uppercase}/i" and "m/\p{Lowercase}/i", both of which match the
same code points as matched by "m/\p{Cased}/i". Details are in "Unicode
Properties" in perlrecharclass.

User-defined property handlers that need to match differently under "/i"
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.

\p{} implies Unicode semantics
Specifying a Unicode property in the pattern indicates that the pattern
is meant for matching according to Unicode rules, the way "\N{*NAME*}"
does.

Regular expressions retain their localeness when interpolated
Regular expressions compiled under "use locale" now retain this when
interpolated into a new regular expression compiled outside a "use
locale", and vice-versa.

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.

Stringification of regexes has changed
Default regular expression modifiers are now notated using "(?^...)".
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.

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):

use re qw(regexp_pattern);
my ($pat, $mods) = regexp_pattern($re_ref);

If the actual stringification is important or older Perls need to be
supported, you can use something like the following:

# Accept both old and new-style stringification
my $modifiers = (qr/foobar/ =~ /\Q(?^/) ? "^" : "-xism";

And then use $modifiers instead of "-xism".

Run-time code blocks in regular expressions inherit pragmata
Code blocks in regular expressions ("(?{...})" and "(??{...})")
previously did not inherit pragmata (strict, warnings, etc.) if the
regular expression was compiled at run time as happens in cases like
these two:

use re "eval";
$foo =~ $bar; # when $bar contains (?{...})
$foo =~ /$bar(?{ $finished = 1 })/;

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.

Stashes and Package Variables
Localised tied hashes and arrays are no longed tied
In the following:

tie @a, ...;
{
local @a;
# here, @a is a now a new, untied array
}
# here, @a refers again to the old, tied array

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.

Stashes are now always defined
"defined %Foo::" now always returns true, even when no symbols have yet
been defined in that package.

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.

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. "defined %hash" has always exposed an implementation
detail: emptying a hash by deleting all entries from it does not make
"defined %hash" false. Hence "defined %hash" is not valid code to
determine whether an arbitrary hash is empty. Instead, use the behaviour
of an empty %hash always returning false in scalar context.

Clearing stashes
Stash list assignment "%foo:: = ()" 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 "caller". They now retain their package names such that
"caller" returns the original sub name if there is still a reference to
its typeglob and "foo::__ANON__" otherwise [perl #79208].

Dereferencing typeglobs
If you assign a typeglob to a scalar variable:

$glob = *foo;

the glob that is copied to $glob is marked with a special flag
indicating that the glob is just a copy. This allows subsequent
assignments to $glob to overwrite the glob. The original glob, however,
is immutable.

Some Perl operators did not distinguish between these two types of
globs. This would result in strange behaviour in edge cases: "untie
$scalar" would not untie the scalar if the last thing assigned to it was
a glob (because it treated it as "untie *$scalar", which unties a
handle). Assignment to a glob slot (such as "*$glob = \@some_array")
would simply assign "\@some_array" to $glob.

To fix this, the "*{}" operator (including its *foo and *$foo 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. ("tie",
"tied" and "untie" have been left as they are for compatibility's sake,
but will warn. See "Deprecations".)

This causes an incompatible change in code that assigns a glob to the
return value of "*{}" when that operator was passed a glob copy. Take
the following code, for instance:

$glob = *foo;
*$glob = *bar;

The *$glob on the second line returns a new immutable glob. That new
glob is made an alias to *bar. Then it is discarded. So the second
assignment has no effect.

See < http://rt.perl.org/rt3/Public/Bug/Display.html?id=77810>; for more
detail.

Magic variables outside the main package
In previous versions of Perl, magic variables like $!, %SIG, etc. would
"leak" into other packages. So %foo::SIG could be used to access
signals, "${"foo::!"}" (with strict mode off) to access C's "errno",
etc.

This was a bug, or an "unintentional" feature, which caused various ill
effects, such as signal handlers being wiped when modules were loaded,
etc.

This has been fixed (or the feature has been removed, depending on how
you see it).

local($_) strips all magic from $_
local() on scalar variables gives them a new value but keeps all their
magic intact. This has proven problematic for the default scalar
variable $_, where perlsub recommends that any subroutine that assigns
to $_ should first localize it. This would throw an exception if $_ is
aliased to a read-only variable, and could in general have various
unintentional side-effects.

Therefore, as an exception to the general rule, local($_) will not only
assign a new value to $_, but also remove all existing magic from it as
well.

Parsing of package and variable names
Parsing the names of packages and package variables has changed:
multiple adjacent pairs of colons, as in "foo::::bar", are now all
treated as package separators.

Regardless of this change, the exact parsing of package separators has
never been guaranteed and is subject to change in future Perl versions.

Changes to Syntax or to Perl Operators
"given" return values
"given" blocks now return the last evaluated expression, or an empty
list if the block was exited by "break". Thus you can now write:

my $type = do {
given ($num) {
break when undef;
"integer" when /^[+-]?[0-9]+$/;
"float" when /^[+-]?[0-9]+(?:\.[0-9]+)?$/;
"unknown";
}
};

See "Return value" in perlsyn for details.

Change in parsing of certain prototypes
Functions declared with the following prototypes now behave correctly as
unary functions:

*
\$ \% \@ \* \&
\[...]
;$ ;*
;\$ ;\% etc.
;\[...]

Due to this bug fix [perl #75904], functions using the "(*)", "(;$)" and
"(;*)" prototypes are parsed with higher precedence than before. So in
the following example:

sub foo(;$);
foo $a < $b;

the second line is now parsed correctly as "foo($a) < $b", rather than
"foo($a < $b)". This happens when one of these operators is used in an
unparenthesised argument:

< > <= >= lt gt le ge
== != <=> eq ne cmp ~~
&
| ^
&&
|| //
.. ...
?:
= += -= *= etc.
, =>

Smart-matching against array slices
Previously, the following code resulted in a successful match:

my @a = qw(a y0 z);
my @b = qw(a x0 z);
@a[0 .. $#b] ~~ @b;

This odd behaviour has now been fixed [perl #77468].

Negation treats strings differently from before
The unary negation operator, "-", now treats strings that look like
numbers as numbers [perl #57706].

Negative zero
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.

If you still need to determine whether a zero is negative, use
"sprintf("%g", $zero) =~ /^-/" or the Data::Float module on CPAN.

":=" is now a syntax error
Previously "my $pi := 4" was exactly equivalent to "my $pi : = 4", with
the ":" being treated as the start of an attribute list, ending before
the "=". The use of ":=" to mean ": =" was deprecated in 5.12.0, and is
now a syntax error. This allows future use of ":=" as a new token.

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.

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 "=".

Change in the parsing of identifiers
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.

Threads and Processes
Directory handles not copied to threads
On systems other than Windows that do not have a "fchdir" function,
newly-created threads no longer inherit directory handles from their
parent threads. Such programs would usually have crashed anyway [perl
#75154].

"close" on shared pipes
To avoid deadlocks, the "close" 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.

fork() emulation will not wait for signalled children
On Windows parent processes would not terminate until all forked
children had terminated first. However, "kill("KILL", ...)" is
inherently unstable on pseudo-processes, and "kill("TERM", ...)" might
not get delivered if the child is blocked in a system call.

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 waitpid()
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.

See perlfork for more information about the fork() emulation on Windows.

Configuration
Naming fixes in Policy_sh.SH may invalidate Policy.sh
Several long-standing typos and naming confusions in Policy_sh.SH have
been fixed, standardizing on the variable names used in config.sh.

This will change the behaviour of Policy.sh if you happen to have been
accidentally relying on its incorrect behaviour.

Perl source code is read in text mode on Windows
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 "DATA"
filehandle, including seek()/tell(), and even simply reading from "DATA"
after filehandles have been flushed by a call to system(), backticks,
fork() etc.

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].

Deprecations
See also "Deprecated C APIs".

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, "m/foo/sand
$bar" is for now still parsed as "m/foo/s and $bar", but will now issue
a warning.

"\c*X*"
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 "c" could be. Now, a
deprecation warning is raised if that character isn't an ASCII
character. Also, a deprecation warning is raised for "\c{" (which is the
same as simply saying ";").

"\b{" and "\B{"
In regular expressions, a literal "{" immediately following a "\b" (not
in a bracketed character class) or a "\B{" is now deprecated to allow
for its future use by Perl itself.

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.

This is a mandatory warning, not obeying -X or lexical warning bits. The
warning is modelled on that supplied by deprecate.pm for
deprecated-in-core .pm libraries. It points to the specific CPAN
distribution that contains the .pl libraries. The CPAN versions, of
course, do not generate the warning.

List assignment to $[
Assignment to $[ 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 $[ in list context. This fixes an oversight in 5.12.0.

Use of qw(...) as parentheses
Historically the parser fooled itself into thinking that "qw(...)"
literals were always enclosed in parentheses, and as a result you could
sometimes omit parentheses around them:

for $x qw(a b c) { ... }

The parser no longer lies to itself in this way. Wrap the list literal
in parentheses like this:

for $x (qw(a b c)) { ... }

This is being deprecated because the parentheses in "for $i (1,2,3) {
... }" are not part of expression syntax. They are part of the statement
syntax, with the "for" statement wanting literal parentheses. The
synthetic parentheses that a "qw" expression acquired were only intended
to be treated as part of expression syntax.

Note that this does not change the behaviour of cases like:

use POSIX qw(setlocale localeconv);
our @EXPORT = qw(foo bar baz);

where parentheses were never required around the expression.

"\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.

"?PATTERN?"
"?PATTERN?" (without the initial "m") has been deprecated and now
produces a warning. This is to allow future use of "?" in new operators.
The match-once functionality is still available as "m?PATTERN?".

Tie functions on scalars holding typeglobs
Calling a tie function ("tie", "tied", "untie") with a scalar argument
acts on a filehandle if the scalar happens to hold a typeglob.

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.

Now there is a deprecation warning whenever a tie function is used on a
handle without an explicit "*".

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.

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.

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 "vendor" or "site" Perl library directories. This will inhibit the
deprecation warnings.

Alternatively, you may want to consider patching lib/deprecate.pm 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.

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 "Task::Deprecations::5_14".

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.

Performance Enhancements
"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 *not* 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.

Optimisation of shift() and pop() calls without arguments
Two fewer OPs are used for shift() and pop() calls with no argument
(with implicit @_). This change makes shift() 5% faster than "shift @_"
on non-threaded perls, and 25% faster on threaded ones.

Optimisation of regexp engine string comparison work
The "foldEQ_utf8" 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.

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.

String appending is 100 times faster
When doing a lot of string appending, perls built to use the system's
"malloc" could end up allocating a lot more memory than needed in a
inefficient way.

"sv_grow", 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.

Eliminate "PL_*" accessor functions under ithreads
When "MULTIPLICITY" was first developed, and interpreter state moved
into an interpreter struct, thread- and interpreter-local "PL_*"
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.

Freeing weak references
When there are many weak references to an object, freeing that object
can under some circumstances take O(*NE<0xB2>*) time to free, where *N*
is the number of references. The circumstances in which this can happen
have been reduced [perl #75254]

Lexical array and hash assignments
An earlier optimisation to speed up "my @array = ..." and "my %hash =
..." assignments caused a bug and was disabled in Perl 5.12.0.

Now we have found another way to speed up these assignments [perl
#82110].

@_ uses less memory
Previously, @_ 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].

Size optimisations to SV and HV structures
"xhv_fill" has been eliminated from "struct xpvhv", saving 1 IV per hash
and on some systems will cause "struct xpvhv" to become cache-aligned.
To avoid this memory saving causing a slowdown elsewhere, boolean use of
"HvFILL" now calls "HvTOTALKEYS" 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.

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.

"XPV", "XPVIV", and "XPVNV" now allocate only the parts of the "SV" body
they actually use, saving some space.

Scalars containing regular expressions now allocate only the part of the
"SV" body they actually use, saving some space.

Memory consumption improvements to Exporter
The @EXPORT_FAIL 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.

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.

"%+" and "%-" use less memory
The bulk of the "Tie::Hash::NamedCapture" 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 "%+" or "%-".

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).

Adjacent pairs of nextstate opcodes are now optimized away
Previously, in code such as

use constant DEBUG => 0;

sub GAK {
warn if DEBUG;
print "stuff\n";
}

the ops for "warn if DEBUG" would be folded to a "null" op ("ex-const"),
but the "nextstate" op would remain, resulting in a runtime op dispatch
of "nextstate", "nextstate", etc.

The execution of a sequence of "nextstate" ops is indistinguishable from
just the last "nextstate" op so the peephole optimizer now eliminates
the first of a pair of "nextstate" 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.

Modules and Pragmata
New Modules and Pragmata
* CPAN::Meta::YAML 0.003 has been added as a dual-life module. It
supports a subset of YAML sufficient for reading and writing
META.yml and MYMETA.yml 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.

* 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 META.json and META.yml) 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.

* 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 CPAN.pm and CPANPLUS can
"bootstrap" HTTP access to CPAN using pure Perl without relying on
external binaries like curl(1) or wget(1).

* JSON::PP 2.27105 has been added as a dual-life module to allow CPAN
clients to read META.json files in CPAN distributions.

* 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.

* 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.

* The following modules were added by the Unicode::Collate upgrade.
See below for details.

Unicode::Collate::CJK::Big5

Unicode::Collate::CJK::GB2312

Unicode::Collate::CJK::JISX0208

Unicode::Collate::CJK::Korean

Unicode::Collate::CJK::Pinyin

Unicode::Collate::CJK::Stroke

* 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.

Updated Modules and Pragma
* attributes has been upgraded from version 0.12 to 0.14.

* Archive::Extract has been upgraded from version 0.38 to 0.48.

Updates since 0.38 include: a safe print method that guards
Archive::Extract from changes to $\; 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 unzip(1) executable.

* Archive::Tar has been upgraded from version 1.54 to 1.76.

Important changes since 1.54 include the following:

* Compatibility with busybox implementations of tar(1).

* A fix so that write() and create_archive() close only
filehandles they themselves opened.

* A bug was fixed regarding the exit code of extract_archive.

* The ptar(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.

* A new ptargrep(1) utility for using regular expressions against
the contents of files in a tar archive.

* pax extended headers are now skipped.

* Attribute::Handlers has been upgraded from version 0.87 to 0.89.

* autodie has been upgraded from version 2.06_01 to 2.1001.

* AutoLoader has been upgraded from version 5.70 to 5.71.

* The B module has been upgraded from version 1.23 to 1.29.

It no longer crashes when taking apart a "y///" containing
characters outside the octet range or compiled in a "use utf8"
scope.

The size of the shared object has been reduced by about 40%, with no
reduction in functionality.

* B::Concise has been upgraded from version 0.78 to 0.83.

B::Concise marks rv2sv(), rv2av(), and rv2hv() ops with the new
"OPpDEREF" flag as "DREFed".

It no longer produces mangled output with the -tree option [perl
#80632].

* B::Debug has been upgraded from version 1.12 to 1.16.

* B::Deparse has been upgraded from version 0.96 to 1.03.

The deparsing of a "nextstate" op has changed when it has both a
change of package relative to the previous nextstate, or a change of
"%^H" or other state and a label. The label was previously emitted
first, but is now emitted last (5.12.1).

The "no 5.13.2" or similar form is now correctly handled by
B::Deparse (5.12.3).

B::Deparse now properly handles the code that applies a conditional
pattern match against implicit $_ as it was fixed in [perl #20444].

Deparsing of "our" followed by a variable with funny characters (as
permitted under the "use utf8" pragma) has also been fixed [perl
#33752].

* B::Lint has been upgraded from version 1.11_01 to 1.13.

* base has been upgraded from version 2.15 to 2.16.

* Benchmark has been upgraded from version 1.11 to 1.12.

* bignum has been upgraded from version 0.23 to 0.27.

* Carp has been upgraded from version 1.15 to 1.20.

Carp now detects incomplete caller() overrides and avoids using
bogus @DB::args. To provide backtraces, Carp relies on particular
behaviour of the caller() 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).

This fixes certain cases of "Bizarre copy of ARRAY" caused by
modules overriding caller() incorrectly (5.12.2).

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].

* CGI has been upgraded from version 3.48 to 3.52.

This provides the following security fixes: the MIME boundary in
multipart_init() is now random and the handling of newlines embedded
in header values has been improved.

* Compress::Raw::Bzip2 has been upgraded from version 2.024 to 2.033.

It has been updated to use bzip2(1) 1.0.6.

* Compress::Raw::Zlib has been upgraded from version 2.024 to 2.033.

* constant has been upgraded from version 1.20 to 1.21.

Unicode constants work once more. They have been broken since Perl
5.10.0 [CPAN RT #67525].

* CPAN has been upgraded from version 1.94_56 to 1.9600.

Major highlights:

* much less configuration dialog hassle
* support for META/MYMETA.json
* support for local::lib
* support for HTTP::Tiny to reduce the dependency on FTP sites
* automatic mirror selection
* iron out all known bugs in configure_requires
* support for distributions compressed with bzip2(1)
* allow Foo/Bar.pm on the command line to mean "Foo::Bar"

* CPANPLUS has been upgraded from version 0.90 to 0.9103.

A change to cpanp-run-perl resolves RT #55964 and RT #57106, both of
which related to failures to install distributions that use
"Module::Install::DSL" (5.12.2).

A dependency on Config was not recognised as a core module
dependency. This has been fixed.

CPANPLUS now includes support for META.json and MYMETA.json.

* CPANPLUS::Dist::Build has been upgraded from version 0.46 to 0.54.

* Data::Dumper has been upgraded from version 2.125 to 2.130_02.

The indentation used to be off when $Data::Dumper::Terse was set.
This has been fixed [perl #73604].

This upgrade also fixes a crash when using custom sort functions
that might cause the stack to change [perl #74170].

Dumpxs no longer crashes with globs returned by *$io_ref [perl
#72332].

* DB_File has been upgraded from version 1.820 to 1.821.

* DBM_Filter has been upgraded from version 0.03 to 0.04.

* Devel::DProf has been upgraded from version 20080331.00 to
20110228.00.

Merely loading Devel::DProf now no longer triggers profiling to
start. Both "use Devel::DProf" and "perl -d:DProf ..." behave as
before and start the profiler.

NOTE: 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.

* Devel::Peek has been upgraded from version 1.04 to 1.07.

* Devel::SelfStubber has been upgraded from version 1.03 to 1.05.

* diagnostics has been upgraded from version 1.19 to 1.22.

It now renders pod links slightly better, and has been taught to
find descriptions for messages that share their descriptions with
other messages.

* Digest::MD5 has been upgraded from version 2.39 to 2.51.

It is now safe to use this module in combination with threads.

* Digest::SHA has been upgraded from version 5.47 to 5.61.

shasum now more closely mimics sha1sum(1)/md5sum(1).

Addfile accepts all POSIX filenames.

New SHA-512/224 and SHA-512/256 transforms (ref. NIST Draft FIPS
180-4 [February 2011])

* DirHandle has been upgraded from version 1.03 to 1.04.

* Dumpvalue has been upgraded from version 1.13 to 1.16.

* DynaLoader has been upgraded from version 1.10 to 1.13.

It fixes a buffer overflow when passed a very long file name.

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].

* Encode has been upgraded from version 2.39 to 2.42.

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.

* Env has been upgraded from version 1.01 to 1.02.

* Errno has been upgraded from version 1.11 to 1.13.

The implementation of Errno has been refactored to use about 55%
less memory.

On some platforms with unusual header files, like Win32 gcc(1) using
"mingw64" headers, some constants that weren't actually error
numbers have been exposed by Errno. This has been fixed [perl
#77416].

* Exporter has been upgraded from version 5.64_01 to 5.64_03.

Exporter no longer overrides $SIG{__WARN__} [perl #74472]

* ExtUtils::CBuilder has been upgraded from version 0.27 to 0.280203.

* ExtUtils::Command has been upgraded from version 1.16 to 1.17.

* ExtUtils::Constant has been upgraded from 0.22 to 0.23.

The AUTOLOAD helper code generated by
"ExtUtils::Constant::ProxySubs" can now croak() for missing
constants, or generate a complete "AUTOLOAD" subroutine in XS,
allowing simplification of many modules that use it (Fcntl,
File::Glob, GDBM_File, I18N::Langinfo, POSIX, Socket).

ExtUtils::Constant::ProxySubs can now optionally push the names of
all constants onto the package's @EXPORT_OK.

* ExtUtils::Install has been upgraded from version 1.55 to 1.56.

* ExtUtils::MakeMaker has been upgraded from version 6.56 to 6.57_05.

* ExtUtils::Manifest has been upgraded from version 1.57 to 1.58.

* ExtUtils::ParseXS has been upgraded from version 2.21 to 2.2210.

* Fcntl has been upgraded from version 1.06 to 1.11.

* File::Basename has been upgraded from version 2.78 to 2.82.

* File::CheckTree has been upgraded from version 4.4 to 4.41.

* File::Copy has been upgraded from version 2.17 to 2.21.

* File::DosGlob has been upgraded from version 1.01 to 1.04.

It allows patterns containing literal parentheses: they no longer
need to be escaped. On Windows, it no longer adds an extra ./ to
file names returned when the pattern is a relative glob with a drive
specification, like C:*.pl [perl #71712].

* File::Fetch has been upgraded from version 0.24 to 0.32.

HTTP::Lite is now supported for the "http" scheme.

The fetch(1) utility is supported on FreeBSD, NetBSD, and Dragonfly
BSD for the "http" and "ftp" schemes.

* File::Find has been upgraded from version 1.15 to 1.19.

It improves handling of backslashes on Windows, so that paths like
C:\dir\/file are no longer generated [perl #71710].

* File::Glob has been upgraded from version 1.07 to 1.12.

* File::Spec has been upgraded from version 3.31 to 3.33.

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;
catpath() returns an empty directory rather than the current
directory if the input directory name is empty; and abs2rel()
properly handles Unix-style input (5.12.2).

* File::stat has been upgraded from 1.02 to 1.05.

The "-x" and "-X" file test operators now work correctly when run by
the superuser.

* Filter::Simple has been upgraded from version 0.84 to 0.86.

* GDBM_File has been upgraded from 1.10 to 1.14.

This fixes a memory leak when DBM filters are used.

* Hash::Util has been upgraded from 0.07 to 0.11.

Hash::Util no longer emits spurious "uninitialized" warnings when
recursively locking hashes that have undefined values [perl #74280].

* Hash::Util::FieldHash has been upgraded from version 1.04 to 1.09.

* I18N::Collate has been upgraded from version 1.01 to 1.02.

* I18N::Langinfo has been upgraded from version 0.03 to 0.08.

langinfo() now defaults to using $_ if there is no argument given,
just as the documentation has always claimed.

* I18N::LangTags has been upgraded from version 0.35 to 0.35_01.

* if has been upgraded from version 0.05 to 0.0601.

* IO has been upgraded from version 1.25_02 to 1.25_04.

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.

* IPC::Cmd has been upgraded from version 0.54 to 0.70.

Resolves an issue with splitting Win32 command lines. An argument
consisting of the single character "0" used to be omitted (CPAN RT
#62961).

* IPC::Open3 has been upgraded from 1.05 to 1.09.

open3() now produces an error if the "exec" call fails, allowing
this condition to be distinguished from a child process that exited
with a non-zero status [perl #72016].

The internal xclose() routine now knows how to handle file
descriptors as documented, so duplicating "STDIN" in a child process
using its file descriptor now works [perl #76474].

* IPC::SysV has been upgraded from version 2.01 to 2.03.

* lib has been upgraded from version 0.62 to 0.63.

* Locale::Maketext has been upgraded from version 1.14 to 1.19.

Locale::Maketext now supports external caches.

This upgrade also fixes an infinite loop in
"Locale::Maketext::Guts::_compile()" when working with tainted
values (CPAN RT #40727).

"->maketext" calls now back up and restore $@ so error messages are
not suppressed (CPAN RT #34182).

* Log::Message has been upgraded from version 0.02 to 0.04.

* Log::Message::Simple has been upgraded from version 0.06 to 0.08.

* Math::BigInt has been upgraded from version 1.89_01 to 1.994.

This fixes, among other things, incorrect results when computing
binomial coefficients [perl #77640].

It also prevents "sqrt($int)" from crashing under "use bigrat".
[perl #73534].

* Math::BigInt::FastCalc has been upgraded from version 0.19 to 0.28.

* Math::BigRat has been upgraded from version 0.24 to 0.26_02.

* Memoize has been upgraded from version 1.01_03 to 1.02.

* MIME::Base64 has been upgraded from 3.08 to 3.13.

Includes new functions to calculate the length of encoded and
decoded base64 strings.

Now provides encode_base64url() and decode_base6

投稿者 xml-rpc : 2011年5月17日 18:25
役に立ちました?:
過去のフィードバック 平均:(0) 総合:(0) 投票回数:(0)
本記事へのTrackback: http://hoop.euqset.org/blog/mt-tb2006.cgi/103756
トラックバック
コメント
コメントする




画像の中に見える文字を入力してください。