Change 21042 by [EMAIL PROTECTED] on 2003/09/05 06:47:43
Acknowledge some known tie bugs.
Affected files ...
... //depot/perl/pod/perltie.pod#34 edit
Differences ...
==== //depot/perl/pod/perltie.pod#34 (text) ====
Index: perl/pod/perltie.pod
--- perl/pod/perltie.pod#33~19819~ Thu Jun 19 07:08:13 2003
+++ perl/pod/perltie.pod Thu Sep 4 23:47:43 2003
@@ -1072,6 +1072,14 @@
=head1 BUGS
+The bucket usage information provided by C<scalar(%hash)> is not
+available. What this means is that using %tied_hash in boolean
+context doesn't work right (currently this always tests false,
+regardless of whether the hash is empty or hash elements).
+
+Localizing tied arrays or hashes does not work. After exiting the
+scope the arrays or the hashes are not restored.
+
You cannot easily tie a multilevel data structure (such as a hash of
hashes) to a dbm file. The first problem is that all but GDBM and
Berkeley DB have size limitations, but beyond that, you also have problems
@@ -1083,12 +1091,8 @@
Tied filehandles are still incomplete. sysopen(), truncate(),
flock(), fcntl(), stat() and -X can't currently be trapped.
-The bucket usage information provided by C<scalar(%hash)> is not
-available. If C<%hash> is tied, this will currently result in a
-fatal error.
-
-Counting the number of entries in a hash via C<scalar(keys(%hash))> or
-C<scalar(values(%hash)>) is inefficient since it needs to iterate
+Counting the number of entries in a hash via C<scalar(keys(%hash))>
+or C<scalar(values(%hash)>) is inefficient since it needs to iterate
through all the entries with FIRSTKEY/NEXTKEY.
=head1 AUTHOR
End of Patch.
