summaryrefslogtreecommitdiffstats
path: root/ChangeLog
diff options
context:
space:
mode:
authordkf <donal.k.fellows@manchester.ac.uk>2010-02-17 21:58:08 (GMT)
committerdkf <donal.k.fellows@manchester.ac.uk>2010-02-17 21:58:08 (GMT)
commit75bf2508e3fdda7b0fb86b63d1cb8e14954cd880 (patch)
treeab11411b42bc7dae1ca8db2a091543842cce9d0a /ChangeLog
parent0198d4b07964264dc869e7b3ec88e8b7fd25d18f (diff)
downloadtcl-75bf2508e3fdda7b0fb86b63d1cb8e14954cd880.zip
tcl-75bf2508e3fdda7b0fb86b63d1cb8e14954cd880.tar.gz
tcl-75bf2508e3fdda7b0fb86b63d1cb8e14954cd880.tar.bz2
Return to using the classic hash function. Now with *extensive* notes in the
comments about why this function is preferred.
Diffstat (limited to 'ChangeLog')
-rw-r--r--ChangeLog8
1 files changed, 8 insertions, 0 deletions
diff --git a/ChangeLog b/ChangeLog
index 9a983fb..ea6906a 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,13 @@
2010-02-17 Donal K. Fellows <dkf@users.sf.net>
+ * generic/tclHash.c (HashStringKey): Restore these hash functions
+ * generic/tclLiteral.c (HashString): to use the classic algorithm.
+ * generic/tclObj.c (TclHashObjKey): Community felt normal case
+ speed to be more important than resistance to malicious cases. For
+ now, hashes that need to deal with the malicious case can use a custom
+ hash table and install their own hash function, though that is not
+ functionality exposed to the script level.
+
* generic/tclCompCmds.c (TclCompileDictUpdateCmd): Stack depth must be
correctly described when compiling a body to prevent crashes in some
debugging modes.