summaryrefslogtreecommitdiff
path: root/pod/perltie.pod
diff options
context:
space:
mode:
authorGurusamy Sarathy <gsar@cpan.org>2000-05-07 01:22:23 +0000
committerGurusamy Sarathy <gsar@cpan.org>2000-05-07 01:22:23 +0000
commit3d0ae7ba72551d8af1ecbcfb8a67d9a77f1cf195 (patch)
tree3791c1935999d98ab2f66662f94e4b30d48398c6 /pod/perltie.pod
parentbe26652545762cccb4c0118f022cf9d0ec20cf93 (diff)
downloadperl-3d0ae7ba72551d8af1ecbcfb8a67d9a77f1cf195.tar.gz
avoid warnings in diagnostics.pm; pod tweaks (from Peter Prymmer
and Tom Phoenix) p4raw-id: //depot/perl@6077
Diffstat (limited to 'pod/perltie.pod')
-rw-r--r--pod/perltie.pod7
1 files changed, 2 insertions, 5 deletions
diff --git a/pod/perltie.pod b/pod/perltie.pod
index c835738573..95de3bb928 100644
--- a/pod/perltie.pod
+++ b/pod/perltie.pod
@@ -862,14 +862,11 @@ called:
=head1 SEE ALSO
See L<DB_File> or L<Config> for some interesting tie() implementations.
+A good starting point for many tie() implementations is with one of the
+modules L<Tie::Scalar>, L<Tie::Array>, L<Tie::Hash>, or L<Tie::Handle>.
=head1 BUGS
-Tied arrays are I<incomplete>. They are also distinctly lacking something
-for the C<$#ARRAY> access (which is hard, as it's an lvalue), as well as
-the other obvious array functions, like push(), pop(), shift(), unshift(),
-and splice().
-
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