summaryrefslogtreecommitdiff
path: root/pod/perltie.pod
diff options
context:
space:
mode:
authorDavid Cantrell <david@cantrell.org.uk>2009-05-06 11:26:56 +0100
committerAbigail <abigail@abigail.be>2009-05-06 12:51:37 +0200
commitbebf870e6d027ca8a7a3da6a23b4612c5178aae4 (patch)
tree88f5da4b891d21a83022e75767766c95df92fc24 /pod/perltie.pod
parent4dcdb34ab7673f92a45785ff83aaec90cce7bfd6 (diff)
downloadperl-bebf870e6d027ca8a7a3da6a23b4612c5178aae4.tar.gz
perltie.pod docpatch
Some years ago I submitted a docpatch for perltie to mention DBM::Deep alongside MLDBM. This updates that patch. The change is merely to remove the word "experimental" now that DBM::Deep is over five years old and is stable. $ diff -u ./pod/perltie.pod~ ./pod/perltie.pod Signed-off-by: Abigail <abigail@abigail.be>
Diffstat (limited to 'pod/perltie.pod')
-rw-r--r--pod/perltie.pod2
1 files changed, 1 insertions, 1 deletions
diff --git a/pod/perltie.pod b/pod/perltie.pod
index 9f26473879..0323e32261 100644
--- a/pod/perltie.pod
+++ b/pod/perltie.pod
@@ -1181,7 +1181,7 @@ tie methods for slice operations.
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
-with how references are to be represented on disk. One experimental
+with how references are to be represented on disk. One
module that does attempt to address this need is DBM::Deep. Check your
nearest CPAN site as described in L<perlmodlib> for source code. Note
that despite its name, DBM::Deep does not use dbm. Another earlier attempt