This is the mail archive of the java-patches@gcc.gnu.org mailing list for the Java project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Patch Ping: Double.parseDouble cannot handle NaN, Infinity or-Infinity

From: Mark Anderson <mark at panonet dot net>
To: tromey at redhat dot com, Bryce McKinlay <mckinlay at redhat dot com>
Cc: Andrew Haley <aph at redhat dot com>, java-patches at gcc dot gnu dot org
Date: Tue, 29 Mar 2005 09:09:58 +0000
Subject: Re: Patch Ping: Double.parseDouble cannot handle NaN, Infinity or-Infinity
References: <200503171459.54699.mark@panonet.net> <42418654.6030106@redhat.com> <m3d5tq2jfn.fsf@localhost.localdomain>

On Wednesday 23 March 2005 20:31, Tom Tromey wrote:
> >>>>> "Bryce" == Bryce McKinlay <mckinlay@redhat.com> writes:
>
> Bryce> I don't see any reason why we shouldn't push this into classpath,
> too.
>
> Classpath already doesn't have this bug.
> I'm just saying, it is simpler to implement the same fix that is
> there, namely checking the buffer after conversion to utf8.
> Otherwise, we're either churning Classpath (for little gain that I
> can see), or adding useless fields to Double.
>
> Tom

So do we have a final decision so I can produce a final patch for this bug?

-- 
Regards,
Mark

Follow-Ups:
- Re: Patch Ping: Double.parseDouble cannot handle NaN, Infinity or-Infinity
  - From: Tom Tromey

References:
- Re: Patch Ping: Double.parseDouble cannot handle NaN, Infinity or-Infinity
  - From: Mark Anderson
- Re: Patch Ping: Double.parseDouble cannot handle NaN, Infinity or-Infinity
  - From: Bryce McKinlay
- Re: Patch Ping: Double.parseDouble cannot handle NaN, Infinity or-Infinity
  - From: Tom Tromey

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]