Commit e8385fd7 authored by rtoy's avatar rtoy
Browse files


o Don't convert characters to uppercase when computing SXHASH for
  characters.  The characters aren't EQUAL anyway, so the hash value
  doesn't have to be the same.

o Update
parent f0c421a2
......@@ -5,7 +5,7 @@
;;; Carnegie Mellon University, and has been placed in the public domain.
"$Header: /Volumes/share2/src/cmucl/cvs2git/cvsroot/src/code/hash-new.lisp,v 1.47 2008/04/29 13:07:47 rtoy Exp $")
"$Header: /Volumes/share2/src/cmucl/cvs2git/cvsroot/src/code/hash-new.lisp,v 1.48 2009/03/27 16:03:15 rtoy Exp $")
;;; **********************************************************************
......@@ -980,7 +980,7 @@
;; The pointers and immediate types.
(cons (sxhash-list s-expr depth))
(fixnum (ldb sxhash-bits-byte s-expr))
(character (char-code (char-upcase s-expr)))
(character (char-code s-expr))
;; Pathnames are EQUAL if all the components are EQUAL, so we
;; hash all of the components of a pathname together.
......@@ -28,6 +28,10 @@ New in this release:
trying to simplify the union of a large number of disjoint
numeric types. Previously, we handled the case of integer
types. Extend this to handle floats as well.
- SXHASH was computing the same hash code for upper and lower case
characters by upcasing the character. This isn't necessary
since the characters are not EQUAL, so make SXHASH return
different values for upper and lower case letter.
* Trac Tickets:
#31: pathname bug with :case :common
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment