From: Father Chrysostomos <sprout@cpan.org>
Date: Fri, 15 Nov 2013 04:30:30 +0000 (-0800)
Subject: perldelta for 7004ee4937 and a618185710
X-Git-Tag: upstream/5.20.0~1227
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=424623a2fa52e73a9a35548708d4d1a87fb950ea;p=platform%2Fupstream%2Fperl.git

perldelta for 7004ee4937 and a618185710
---

diff --git a/pod/perldelta.pod b/pod/perldelta.pod
index a252fce..e2b0154 100644
--- a/pod/perldelta.pod
+++ b/pod/perldelta.pod
@@ -554,6 +554,14 @@ Undefining a glob that triggers a DESTROY method that undefines the same
 glob is now safe.  It used to produce "Attempt to free unreferenced glob
 pointer" warnings and leak memory.
 
+=item *
+
+If subroutine redefinition (C<eval 'sub foo{}'> or C<newXS> for XS code)
+triggers a DESTROY method on the sub that is being redefined, and that
+method assigns a subroutine to the same slot (C<*foo = sub {}>), C<$_[0]>
+is no longer left pointing to a freed scalar.  Now there is a memory leak
+instead. :-(
+
 =back
 
 =head1 Known Problems