RE: [lang] MutableNumbers: if you have an idea, please share it.

[Brent Worden]

Here's some mutable number types I've had laying around for about 5 years.
Feel free to use them in lang (or disregard them) as you see fit.

Brent Worden
http://www.brent.worden.org

> -----Original Message-----
> From: _matthewHawthorne [mailto:[EMAIL PROTECTED]
> Sent: Saturday, June 28, 2003 4:17 PM
> To: [EMAIL PROTECTED]
> Subject: [lang] MutableNumbers: if you have an idea, please share it.
>
>
> I have started some initial work on the concept of MutableNumbers, that
> I mentioned a few months ago.  Before I begin anything major, I want to
> get some feedback.
>
> Any comments and suggestions are appreciated, especially with regard to
> class design, and usefulness.
>
>
> --------------------------------
> Initial design
> --------------------------------
>
> MutableNumber
>
>     // Internal value
>     double value;
>
>     // java.lang.Number overrides
>     byte byteValue()
>     short shortValue()
>     int intValue()
>     long longValue()
>     float floatValue()
>     double doubleValue()
>
>     // Mutator methods
>     setByteValue(byte)
>     setShortValue(short)
>     setIntValue(int)
>     setLongValue(long)
>     setFloatValue(float)
>     setDoubleValue(double)
>
>
> Two sample extensions would be:
>
> MutableInteger
>     MutableInteger(int)
>
> MutableFloat
>     MutableFloat(float)
>
>
> --------------------------------
> Questions
> --------------------------------
> 1) Would MutableNumbers be useful?
>
> A typical usage could be:
>
> Thing.setId(new Integer(1))
> Thing.setId(new Integer(2))
>
> Thing.setId(new MutableInteger(1))
> Thing.getId().setIntValue(2)
>
> But, in looking at this, it doesn't seem to make much of a difference.
> Are there any other uses?
>
>
> 2) Is double an acceptable internal type for all numbers?  It seemed
> simplest to choose the largest type, and upcast all other types.
>
>
> 3) Where should the following methods go?
>
>     Byte byteObject()
>     Short shortObject()
>     Integer intObject()
>     Long longObject()
>     Float floatObject()
>     Double doubleObject()
>
> The could all easily be placed in the MutableNumber class itself, but
> this would almost eliminate the need for subclasses entirely.
>
> If MutableNumber is not abstract, it becomes:
>
> MutableNumber num = new MutableNumber()
> num.setIntValue(5)
> num.intObject()
>
> vs.
>
> MutableInteger mutInt = new MutableInteger(5)
> mutInt.intObject()
>
>
> 4) Would the following  be good additions also?
>
> boolean booleanValue()
> setBooleanValue(boolean)
> Boolean booleanObject()
>
> This may duplicate some current commons functionality (in BooleanUtils I
> believe), but I think this addition would be consistent with the other
> methods.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>

mutable.zip
Description: Zip compressed data

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]