AbstractNumber if
you prefer to keep MutableNumber as an interface).
Gary
> -Original Message-
> From: Stephen Colebourne [mailto:[EMAIL PROTECTED]
> Sent: Thursday, September 30, 2004 16:15
> To: Jakarta Commons Developers List
> Subject: Re: [lang] Mutable t
[EMAIL PROTECTED]
> Sent: Thursday, September 30, 2004 16:15
> To: Jakarta Commons Developers List
> Subject: Re: [lang] Mutable type casts and MutableNumber
>
> From: "matthew.hawthorne" <[EMAIL PROTECTED]>
> > Gary Gregory wrote:
> > > 1st minor: ther
From: "matthew.hawthorne" <[EMAIL PROTECTED]>
> Gary Gregory wrote:
> > 1st minor: there are a bunch of unnecessary type-casts, I'd like to
> > remove those if no one objects.
+1
> > 2nd: There is no MutableNumber class. It seems to me that the mutable
> > number classes are paralle to java.lang.N
Gary Gregory wrote:
1st minor: there are a bunch of unnecessary type-casts, I'd like to
remove those if no one objects. For example, in MutableInteger, this
cast to long is superfluous:
public long longValue() {
return (long) value;
}
That sounds right, perhaps these casts were just
Hello,
I do like the new mutable classes; I can use them now in our project as
a matter of fact.
Two issues,
1st minor: there are a bunch of unnecessary type-casts, I'd like to
remove those if no one objects. For example, in MutableInteger, this
cast to long is superfluous:
public long lon
