comparison src/lrecord.h @ 2515:de9952d2ed18

[xemacs-hg @ 2005-01-26 10:22:19 by ben] Hash table cleanups, part 1 of 2 emacs-marshals.c, hash.c, hash.h, ui-gtk.c: Clean up and generalize creation of string hash tables. ui-gtk.c, elhash.h, gccache-gtk.c, glyphs-gtk.c, lrecord.h, marker.c, objects-gtk.c, objects-msw.c, objects-tty.c, objects-x.c, objects.c, opaque.c, rangetab.c, specifier.c, specifier.h, xgccache.c: Use Hashcode rather than unsigned long.
author ben
date Wed, 26 Jan 2005 10:22:29 +0000
parents ecf1ebac70d8
children 9f70af3ac939
comparison
equal deleted inserted replaced
2514:b49d38bc659d 2515:de9952d2ed18
274 the Lisp_Object itself as the hash. But, you must still satisfy 274 the Lisp_Object itself as the hash. But, you must still satisfy
275 the constraint that if two objects are `equal', then they *must* 275 the constraint that if two objects are `equal', then they *must*
276 hash to the same value in order for hash tables to work properly. 276 hash to the same value in order for hash tables to work properly.
277 This means that `hash' can be NULL only if the `equal' method is 277 This means that `hash' can be NULL only if the `equal' method is
278 also NULL. */ 278 also NULL. */
279 unsigned long (*hash) (Lisp_Object, int); 279 Hashcode (*hash) (Lisp_Object, int);
280 280
281 /* Data layout description for your object. See long comment below. */ 281 /* Data layout description for your object. See long comment below. */
282 const struct memory_description *description; 282 const struct memory_description *description;
283 283
284 /* These functions allow any object type to have builtin property 284 /* These functions allow any object type to have builtin property