summaryrefslogtreecommitdiff
path: root/lib/Hash
diff options
context:
space:
mode:
authorAndreas König <a.koenig@mind.de>2002-10-04 08:38:57 +0200
committerhv <hv@crypt.org>2002-10-10 11:29:12 +0000
commit641c4430082a3fd1d8e803e65d696244a0104810 (patch)
treea2ac06911dfd84ca43465e97f6396e959581f028 /lib/Hash
parenta7ad731c5ef0d5f23c440149f8f810a4785a2903 (diff)
downloadperl-641c4430082a3fd1d8e803e65d696244a0104810.tar.gz
Re: Hash::Util::lock_keys inhibits bless
Message-ID: <m3bs6astr2.fsf@k242.linux.bogus> p4raw-id: //depot/perl@17992
Diffstat (limited to 'lib/Hash')
-rw-r--r--lib/Hash/Util.pm9
1 files changed, 5 insertions, 4 deletions
diff --git a/lib/Hash/Util.pm b/lib/Hash/Util.pm
index 0c8979d61b..90a8e5aaa5 100644
--- a/lib/Hash/Util.pm
+++ b/lib/Hash/Util.pm
@@ -59,10 +59,11 @@ This is intended to largely replace the deprecated pseudo-hashes.
Restricts the given %hash's set of keys to @keys. If @keys is not
given it restricts it to its current keyset. No more keys can be
-added. delete() and exists() will still work, but it does not effect
-the set of allowed keys. B<Note>: the current implementation does not
-allow you to bless() the resulting hash, so if you want to use
-lock_keys() for an object, you need to bless it prior to locking it.
+added. delete() and exists() will still work, but will not alter
+the set of allowed keys. B<Note>: the current implementation prevents
+the hash from being bless()ed while it is in a locked state. Any attempt
+to do so will raise an exception. Of course you can still bless()
+the hash before you call lock_keys() so this shouldn't be a problem.
unlock_keys(%hash);