summaryrefslogtreecommitdiff
path: root/pod/perldiag.pod
diff options
context:
space:
mode:
authorDavid Mitchell <davem@iabyn.com>2011-05-10 17:24:29 +0100
committerDavid Mitchell <davem@iabyn.com>2011-05-19 14:49:43 +0100
commitee872193302939c724fd6c2c18071c621bfac6c4 (patch)
tree9649f1d0a1d70dd68afd4642f6b90f78fb405ff0 /pod/perldiag.pod
parent272e8453abcb0fceb34b1464670386e03a1f55bb (diff)
downloadperl-ee872193302939c724fd6c2c18071c621bfac6c4.tar.gz
remove 'hfreeentries failed to free hash' panic
Currently perl attempts to clear a hash 100 times before panicking. So for example, if a naughty destructor keeps adding things back into the hash, this will eventually panic. Note that this can usually only occur with %h=() or undef(%h), since when freeing a hash, there's usually no reference to the hash that a destructor can use to mess with the hash. Remove this limit (so it may potentially loop forever). My reasoning is that (a) if the user wants to keep adding things back into the hash, who are we to stop her? (b) as part of of the process of making sv_clear() non-recursive when freeing hashes, I'm trying to reduce the amount of state that must be maintained between each iteration. Note that arrays currently don't have a limit.
Diffstat (limited to 'pod/perldiag.pod')
-rw-r--r--pod/perldiag.pod7
1 files changed, 0 insertions, 7 deletions
diff --git a/pod/perldiag.pod b/pod/perldiag.pod
index 8f2ad2913f..b90a141961 100644
--- a/pod/perldiag.pod
+++ b/pod/perldiag.pod
@@ -3423,13 +3423,6 @@ repeatedly, but each time something re-created entries in the glob. Most
likely the glob contains an object with a reference back to the glob and a
destructor that adds a new object to the glob.
-=item panic: hfreeentries failed to free hash
-
-(P) The internal routine used to clear a hash's entries tried repeatedly,
-but each time something added more entries to the hash. Most likely the hash
-contains an object with a reference back to the hash and a destructor that
-adds a new object to the hash.
-
=item panic: INTERPCASEMOD
(P) The lexer got into a bad state at a case modifier.