summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorZefram <zefram@fysh.org>2012-05-25 18:56:45 +0100
committerZefram <zefram@fysh.org>2012-05-25 18:56:45 +0100
commit80b8b050d2c6976822563e9f8edb2baa83539b12 (patch)
tree7bb0ba79eac1657d108c75ef402ab98a2b0a74e4
parent39ce3d224ef430ffae8903e121e2da28bf50c127 (diff)
downloadperl-80b8b050d2c6976822563e9f8edb2baa83539b12.tar.gz
perldelta updates
-rw-r--r--pod/perldelta.pod44
1 files changed, 43 insertions, 1 deletions
diff --git a/pod/perldelta.pod b/pod/perldelta.pod
index 906aadc478..3f83b3b05a 100644
--- a/pod/perldelta.pod
+++ b/pod/perldelta.pod
@@ -1,6 +1,6 @@
=encoding utf8
-=for comment complete up to commit c9e3649f13e1c1db9054c8d419ce2969309e093d
+=for comment complete up to commit a4f7a67c079118a2f900d5f95d3cada67e3475ea
=head1 NAME
@@ -166,6 +166,12 @@ C<no overload> now warns for invalid arguments, just like C<use overload>.
=item *
+L<Pod::Functions> has been upgraded from version 1.05 to 1.06.
+
+Typo fix in generated documentation.
+
+=item *
+
L<Storable> has been upgraded from version 2.34 to 2.35.
Modifying C<$_[0]> within C<STORABLE_freeze> no longer results in crashes
@@ -222,6 +228,35 @@ XXX Description of the change here
=back
+=head3 L<perldiag>
+
+=over 4
+
+=item *
+
+The explanation of symbolic references being prevented by "strict refs"
+now doesn't assume that the reader knows what symbolic references are.
+
+=item *
+
+XXX Description of the change here
+
+=back
+
+=head3 L<perlfunc>
+
+=over 4
+
+=item *
+
+The return value of C<pipe> is now documented.
+
+=item *
+
+XXX Description of the change here
+
+=back
+
=head3 L<XXX>
=over 4
@@ -546,6 +581,13 @@ error when it is the data that are at fault [perl #60204].
C<join> and C<"@array"> now call FETCH only once on a tied C<$">
[perl #8931].
+=item *
+
+Some subroutine calls generated by compiling core ops affected by a
+C<CORE::GLOBAL> override had op checking performed twice. The checking
+is always idempotent for pure Perl code, but the double checking can
+matter when custom call checkers are involved.
+
=back
=head1 Known Problems