summary refs log tree commit diff
path: root/FAQ.in
diff options
context:
space:
mode:
authorUlrich Drepper <drepper@redhat.com>1999-04-10 09:38:42 +0000
committerUlrich Drepper <drepper@redhat.com>1999-04-10 09:38:42 +0000
commit34df6c305435d96e76456cb98bcdb56363fb918f (patch)
tree0b0d16719adeac4cca6b3ba1e9925202d8e4fa0d /FAQ.in
parentc1349648c5b0b75583f9f96e42e689f10f8f74ad (diff)
downloadglibc-34df6c305435d96e76456cb98bcdb56363fb918f.tar.gz
glibc-34df6c305435d96e76456cb98bcdb56363fb918f.tar.xz
glibc-34df6c305435d96e76456cb98bcdb56363fb918f.zip
Change Perl <-> db2 answer.
Diffstat (limited to 'FAQ.in')
-rw-r--r--FAQ.in14
1 files changed, 4 insertions, 10 deletions
diff --git a/FAQ.in b/FAQ.in
index 8786c4d64f..393a12073d 100644
--- a/FAQ.in
+++ b/FAQ.in
@@ -1207,16 +1207,10 @@ completely.
 	the Perl db modules the testsuite is not passed.  This did not
 	happen with db-1, gdbm, or ndbm.
 
-{UD} You are using an outdated copy of the DB_File Perl module.  In fact db-2
-finally removed the handling of zero-sized keys which was one of the features
-tested by the old Perl testsuite and therefore you see an error.  But this
-never was documented and guaranteed, only broken programs used this feature.
-
-Consequently db-2 does not need to support this feature and instead signals
-an error which leads to easier debugging.  The DB_File module maintainer
-Paul Marquess <pmarquess@bfsec.bt.co.uk> acknowledged this change and fixed
-the testsuite so that if you use DB_File v1.60 or later you should not have
-any more problems with db-2.
+{MK} Db-2 does not support zero-sized keys.  The Perl testsuite
+tests the support for zero-sized keys and therefore fails when db-2 is
+used.  The Perl folks are looking for a solution, but thus far have
+not found a satisfactory one.
 
 ??	The pow() inline function I get when including <math.h> is broken.
 	I get segmentation faults when I run the program.