Re: Potential bug in Hashtable

[Bryce McKinlay]

John Leuner wrote:

> I ran the latest classpath code against mauve, a
> hashtable test which checks the size() after a clone()
> failed:
>
> I think copy.size should be set to 0 in the clone
> method (before the putAll)?

I agree. HashMap probibly needs this fix also. Also I'm not sure 
Hashtable.clone() should call putAll, since this will be visible to 
subclasses. Maybe we should add the equivilent of the 
HashMap.putAllInternal.

regards

Bryce.