Re: Scheme style auto-resizing hashtable (fwd)

[Jay Glascoe <jglascoe@jay.giss.nasa.gov>]

whoops, got guile's email address screwed up.

	Jay Glascoe
	jglascoe@jay.giss.nasa.gov

---------- Forwarded message ----------
Date: Fri, 23 Oct 1998 22:49:42 -0400 (EDT)
From: Jay Glascoe <jglascoe@jay.giss.nasa.gov>
To: Maciej Stachowiak <mstachow@mit.edu>
Cc: guile@gnu.com
Subject: Re: Scheme style auto-resizing hashtable 

and another thing,

I'm going to completely re-haul make-hashtab to accept one optional
argument: either an alist or a vector of associations.  I figure my hash
tables do an excellent job of choosing (and modifying) max-bucket-size,
and they resize so quickly that an initial number-buckets of 4 is more
than adequate.  As for the auto-shrink argument, well the user will just
have to call hashtab-(en|dis)able themselves.

Now, why the optional alist/vector of associations argument?  I figure
that someone using an alist that grows larger than they expected (say
>100) can easily trade it in for a hash table.  And any good avl-tree
will probably have avl->alist and avl->vector procedures.

	Jay