This is a live mirror of the Perl 5 development currently hosted at
https://github.com/perl/perl5
https://perl5.git.perl.org
/
perl5.git
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
| inline |
side by side
(parent:
d0fcfa0
)
perldelta for 7004ee4937 and a618185710
author
Father Chrysostomos
<sprout@cpan.org>
Fri, 15 Nov 2013 04:30:30 +0000
(20:30 -0800)
committer
Father Chrysostomos
<sprout@cpan.org>
Fri, 15 Nov 2013 04:30:30 +0000
(20:30 -0800)
pod/perldelta.pod
patch
|
blob
|
blame
|
history
diff --git
a/pod/perldelta.pod
b/pod/perldelta.pod
index
a252fce
..
e2b0154
100644
(file)
--- 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