summaryrefslogtreecommitdiff
path: root/doc/gperf.texi
diff options
context:
space:
mode:
authorBruno Haible <bruno@clisp.org>2003-02-17 10:36:47 +0000
committerBruno Haible <bruno@clisp.org>2003-02-17 10:36:47 +0000
commitec800f65ec88465b0f9b3f9063b945dd4749f535 (patch)
tree27b1b5488e66cb100d0271d3b2bc2b2077376129 /doc/gperf.texi
parent799d1c7534f4366fe1592b3b010e0a8be3eb3863 (diff)
downloadgperf-ec800f65ec88465b0f9b3f9063b945dd4749f535.tar.gz
Introduce new alpha_inc pass, to avoid artificial duplicates.
Diffstat (limited to 'doc/gperf.texi')
-rw-r--r--doc/gperf.texi11
1 files changed, 1 insertions, 10 deletions
diff --git a/doc/gperf.texi b/doc/gperf.texi
index 7f0499e..f47c706 100644
--- a/doc/gperf.texi
+++ b/doc/gperf.texi
@@ -993,7 +993,7 @@ through a search that minimizes the number of byte positions.
@itemx --duplicates
@cindex Duplicates
Handle keywords whose selected byte sets hash to duplicate values.
-Duplicate hash values can occur for three reasons:
+Duplicate hash values can occur for two reasons:
@itemize @bullet
@item
@@ -1004,15 +1004,6 @@ the majority of keywords still require one probe into the table. To
overcome this problem, the option @samp{-m 50} should be used.
@item
-Since the @code{gperf} generated hash function treats the bytes at
-different byte positions with equal weight, keywords that are permutations
-of each other can lead to the same hash function value if they are not
-disambiguated by the set of selected byte positions. Sometimes even this
-is not possible; for example, the keyword set @{"xy", "yx", "xz", "zx"@}
-will always lead to duplicates, regardless how the selected byte positions
-are chosen. You can use the option @samp{-D} to handle this rare case.
-
-@item
Sometimes a set of keywords may have the same names, but possess different
attributes. With the -D option @code{gperf} treats all these keywords as
part of an equivalence class and generates a perfect hash function with