=encoding utf8
=for comment
-This has been completed up to d54f8cf785.
+This has been completed up to 26de4ac8, except for:
+d9a4b459f94297889956ac3adc42707365f274c2
+bf5522a13a381257966e7ed6b731195a873b153e
+9cef83062267e94311e1fd8744396e440642738e
+8e88cfee26d866223a6b3bfffce6270271de00db
=head1 NAME
This is particularly useful to suppresses the default actions of a
C<Devel::*> module's C<import> method whilst still loading it for debugging.
+=head2 Filehandle method calls load IO::File on demand
+
+When a method call on a filehandle would die because the method can not
+be resolved and L<IO::File> has not been loaded, Perl now loads IO::File
+via C<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 only happens 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
+
+=head2 Full functionality for C<use feature 'unicode_strings'>
+
+This release provides full functionality for C<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 L<feature>.
+
+This feature avoids the "Unicode Bug" (See
+L<perlunicode/The "Unicode Bug"> for details.) If their is a
+possibility that your code will process Unicode strings, you are
+B<strongly> encouraged to use this subpragma to avoid nasty surprises.
+
+This availability of this should strongly affect the whole tone of
+various documents, such as L<perlunicode> and L<perluniintro>, but this
+work has not been done yet.
+
+=head2 Exception Handling Backcompat Hack
+
+When an exception is thrown in an C<eval BLOCK>, C<$@> is now set before
+unwinding, as well as being set after unwinding as the eval block exits. This
+early setting supports code that has historically treated C<$@> during unwinding
+as an indicator of whether the unwinding was due to an exception. These modules
+had been broken by 5.13.1's change from setting C<$@> early to setting it late.
+This double setting arrangement is a stopgap until the reason for unwinding can
+be made properly introspectable. C<$@> has never been a reliable indicator of
+this.
+
+=head2 DTrace probes now include package name
+
+The DTrace probes now include an additional argument (C<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
+
=head1 Security
XXX Any security-related notices go here. In particular, any security
because of a code generator) then avoid the error by adding a space before
the C<=>.
+=head2 Run-time code block in regular expressions
+
+Code blocks in regular expressions (C<(?{...})> and C<(??{...})>) used not
+to inherit any 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 was a bug, which has now been fixed. But it has the potential to break
+any code that was relying on this bug.
+
=head1 Deprecations
XXX Any deprecated features, syntax, modules etc. should be listed here.
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.
+=head2 Tie functions on scalars holding typeglobs
+
+Calling a tie function (C<tie>, C<tied>, C<untie>) with a scalar argument
+acts on a file handle 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.
+
+This bug was fixed in 5.13.7 but, because of the breakage it caused, the
+fix has been reverted. Now there is a deprecation warning whenever a tie
+function is used on a handle without an explicit C<*>.
+
=head1 Performance Enhancements
XXX Changes which enhance performance without changing behaviour go here. There
=item *
+C<Devel::SelfStubber> has been upgraded from version 1.04 to 1.05.
+
+=item *
+
+C<Digest::SHA> has been upgraded from 5.48 to 5.50
+
+shasum now more closely mimics sha1sum/md5sum and Addfile
+accepts all POSIX filenames.
+
+=item *
+
+C<Dumpvalue> has been upgraded from version 1.14 to 1.15.
+
+=item *
+
+C<Env> has been upgraded from version 1.01 to 1.02.
+
+=item *
+
+C<ExtUtils::CBuilder> has been upgraded from 0.2703 to 0.2802
+
+=item *
+
+C<if> has been upgraded from 0.06 to 0.0601.
+
+=item *
+
+C<Devel::SelfStubber> has been upgraded from version 1.03 to 1.04.
+
+=item *
+
C<IPC::Cmd> has been upgraded from 0.64 to 0.66
Resolves an issue with splitting Win32 command lines
=item *
+C<Locale::Codes> has been upgraded from version 3.14 to 3.15
+
+=item *
+
+C<Memoize> has been upgraded from version 1.01_03 to 1.02.
+
+=item *
+
C<MIME::Base64> has been upgraded from 3.10 to 3.13
Now provides encode_base64url and decode_base64url functions to process
=item *
+C<mro> has been upgraded from version 1.05 to 1.06.
+
+C<next::method> I<et al.> now take into account that every class inherits
+from UNIVERSAL
+L<[perl #68654]|http://rt.perl.org/rt3/Public/Bug/Display.html?id=68654>.
+
+=item *
+
C<overload> has been upgraded from 1.11 to 1.12.
=item *
=item *
+C<re> has been upgraded from 0.14 to 0.15.
+
+=item *
+
C<Socket> has been upgraded from 1.91 to 1.92.
It has several new functions for handling IPv6 addresses.
=item *
+C<Storable> has been upgraded from 2.24 to 2.25.
+
+This adds support for serialising code references that contain UTF-8 strings
+correctly. The Storable minor version number changed as a result -- this means
+Storable users that set C<$Storable::accept_future_minor> to a C<FALSE> value
+will see errors (see L<Storable/FORWARD COMPATIBILITY> for more details).
+
+=item *
+
C<Time::HiRes> has been upgraded from 1.9721 to 1.9721_01.
=item *
C<version> has been upgraded from 0.82 to 0.86.
+=item *
+
+C<Win32> has been upgraded from 0.039 to 0.040.
+
=back
=head2 Removed Modules and Pragmata
=item *
-XXX
+There is a new "Closure prototype called" error.
=back
=item *
-XXX
+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 C<use constant>, since the value
+of the constant may not be known at the time the program is written
+L<[perl #77762]|http://rt.perl.org/rt3/Public/Bug/Display.html?id=77762>.
=back
=over 4
-=item XXX-some-platform
+=item NetBSD
-XXX
+The NetBSD hints file has been changed to make the system's malloc the
+default.
=back
=item *
-XXX
+C<mg_findext> and C<sv_unmagicext> have been added.
+
+These new functions 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
+C<sv_magicext> 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
+C<MAGIC> pointers of an C<SV> to find the magic that belongs to them.
+
+=item *
+
+The C<parse_fullexpr()>, C<parse_listexpr(), C<parse_termexpr()> and
+C<parse_arithexpr()> functions have been added.
+
+These are for parsing expressions at various precedence levels.
=back
to be stringified, even if the hash was tied
L<[perl #79178]|http://rt.perl.org/rt3/Public/Bug/Display.html?id=79178>.
+=item *
+
+A closure containing an C<if> statement followed by a constant or variable
+is no longer treated as a constant
+L<[perl #63540]|http://rt.perl.org/rt3/Public/Bug/Display.html?id=63540>.
+
+=item *
+
+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
+L<[perl #68560]|http://rt.perl.org/rt3/Public/Bug/Display.html?id=68560>.
+
+=item *
+
+A regular expression optimisation would sometimes cause a match with a
+C<{n,m}> quantifier to fail when it should match
+L<[perl #79152]|http://rt.perl.org/rt3/Public/Bug/Display.html?id=79152>.
+
+=item *
+
+What has become known as the "Unicode Bug" is resolved in this release.
+Under C<use feature 'unicode_strings'>, the internal storage format of a
+string no longer affects the external semantics. There are two known
+exceptions. User-defined case changing functions, which are planned to
+be deprecated in 5.14, require utf8-encoded strings to function; and the
+character C<LATIN SMALL LETTER SHARP S> in regular expression
+case-insensitive matching has a somewhat different set of bugs depending
+on the internal storage format. Case-insensitive matching of all
+characters that have multi-character matches, as this one does, is
+problematical in Perl.
+L<[perl #58182]|http://rt.perl.org/rt3/Public/Bug/Display.html?id=58182>.
+
+=item *
+
+Mentioning a read-only lexical variable from the enclosing scope in a
+string C<eval> would cause the variable to become writable
+L<[perl #19135]|http://rt.perl.org/rt3/Public/Bug/Display.html?id=19135>.
+
+=item *
+
+C<state> can now be used with attributes. It used to mean the same thing as
+C<my> if attributes were present
+L<[perl #68658]|http://rt.perl.org/rt3/Public/Bug/Display.html?id=68658>.
+
+=item *
+
+Expressions like C<< @$a > 3 >> no longer cause C<$a> to be mentioned in
+the "Use of uninitialized value in numeric gt" warning when C<$a> is
+undefined (since it is not part of the C<E<gt>> expression, but the operand
+of the C<@>)
+L<[perl #72090]|http://rt.perl.org/rt3/Public/Bug/Display.html?id=72090>.
+
+=item *
+
+C<require> no longer causes C<caller> to return the wrong file name for
+the scope that called C<require> and other scopes higher up that had the
+same file name
+L<[perl #68712]|http://rt.perl.org/rt3/Public/Bug/Display.html?id=68712>.
+
+=item *
+
+The ref types in the typemap for XS bindings now support magical variables
+L<[perl #72684]|http://rt.perl.org/rt3/Public/Bug/Display.html?id=72684>.
+
+=item *
+
+Match variables (e.g., C<$1>) no longer persist between calls to a sort
+subroutine
+L<[perl #76026]|http://rt.perl.org/rt3/Public/Bug/Display.html?id=76026>.
+
+=item *
+
+The C<B> module was returning B::OPs instead of B::LOGOPs for C<entertry>
+L<[perl #80622]|http://rt.perl.org/rt3/Public/Bug/Display.html?id=80622>.
+
+This was due to a bug in the perl core, not in C<B> itself.
+
=back
=head1 Known Problems
=item *
-A number of bugs with regular expression bracketed character classes
-have been fixed, mostly having to do with matching characters in the
-non-ASCII Latin-1 range.
+XXX
=back
https://perl5.git.perl.org / perl5.git / blobdiff