This sounds like we should add the missing methods. MutableNumber is only
worth adding if someone is going to hold a variable reference as a mutable
Number, and I can't see the use case for that (over and above mutable
Object)
Stephen
From: "Gary Gregory" <[EMAIL PROTECTED]>
In particular, Number
I think there is value indeed to a MutableNumber class and or interface
if you compare Number to the mutable classes that wrap number
primitives.
In particular, Number declares all of the conversion methods like
byteValue(), intValue(), etc. Number provides default implementation for
byteValue()