db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "RPost" <rp0...@pacbell.net>
Subject Re: [Fwd: Re: [PATCH] (DERBY-123) Derby incorrectly rounds double values down during insert into NUMERIC]
Date Fri, 04 Feb 2005 17:23:18 GMT
My mistake. When I saw your "Double.toString()" (with no parameters) I
assumed you meant the non-static version since a static toString with no
parameters doesn't exist and doesn't make sense. Thanks for clarifying.
----- Original Message -----
From: "Daniel John Debrunner" <djd@debrunners.com>
To: <derby-dev@db.apache.org>
Sent: Friday, February 04, 2005 9:05 AM
Subject: Re: [Fwd: Re: [PATCH] (DERBY-123) Derby incorrectly rounds double
values down during insert into NUMERIC]


>
> >>Even using Double.toString() in itself creates an extra two objects . .
.
> >>
> >>
> >
> >Dan's right but interestingly, it is even more convoluted.
> >
> >Double.toString() in Double.java is "public String toString() { return
> >String.valueOf(value);}
> >
> >And then String.valueOf(value) in turn is "public static String
> >valueOf(double d) { return Double.toString(d);}
> >
> >Which means it winds up calling the Double.toString(theValue) that you
are
> >now going to call anyway.
> >
> >
> >
> To be clear I was referring to the static Double.toString(double) method.
>
> Dan.
>


Mime
View raw message