Changes seem fine to me. As MutableNumber extends Number, but is not in itself Mutable, and yet implements Mutable, I don't think there's a need for it. Just there for symmetry I presume.
It's handling only a couple of lines of shared code, so not a huge deal there either. Hen On Mon, 5 Jul 2004, Stephen Colebourne wrote: > I have just reworked the MutableInteger class to MutableInt. The old code > seemed to have issues with equals and hashcode. I'm also suggesting that > MutableNumber doesn't achieve a lot and is worth dropping. > > Anyone care to review MutableInt before I update the rest of the mutable > package? > > Stephen > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
