From: Stephen Crawley <crawley@dstc.edu.au>
To: Mark Wielaard <mark@klomp.org>
Cc: Dalibor Topic <robilad@yahoo.com>,
Anthony Green <green@redhat.com>,
mauve-discuss@sources.redhat.com, crawley@piglet.dstc.edu.au
Subject: Re: 600+ BigDecimal tests
Date: Sun, 19 Jan 2003 23:40:00 -0000 [thread overview]
Message-ID: <200301192339.h0JNdufh022135@piglet.dstc.edu.au> (raw)
In-Reply-To: Message from Mark Wielaard <mark@klomp.org> of "18 Jan 2003 17:04:37 +0100." <1042905877.24536.344.camel@elsschot>
Folks,
I've been looking at DiagBigDecimal and the "bugs" that it shows up.
Some are genuine, but some are questionable. (The following is from memory
... YMMV)
* There is a bug with the parse methods barffing with a "+" in the
exponent in strings like "123.4E+5".
I think this is the bug that Mark has patched.
* There is a bug in the toString() method that doesn't add a leading
zero in some cases; e.g. it produces ".1234" instead of "0.1234".
I have a fix for this. [I'll submit it tonight.]
* Some of the other tests check exception message strings, and are
failing because the messages are different.
I don't know whether this is a bug or not. Is Classpath aiming to
give the same exception messages as the Sun JDK implementation ???
* The 'has001' failure is due to differences in the way that
Classpath and the SUN JDK are calculating hashcodes.
I don't know whether this is a bug or not. Is Classpath aiming to
give the same hash code values as the Sun JDK implementation ???
-- Steve
next prev parent reply other threads:[~2003-01-19 23:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-22 14:58 Anthony Green
2003-01-03 1:35 ` Mark Wielaard
2003-01-17 19:26 ` Mark Wielaard
2003-01-18 15:27 ` Dalibor Topic
2003-01-18 16:05 ` Mark Wielaard
2003-01-19 23:40 ` Stephen Crawley [this message]
2003-01-20 0:09 ` Anthony Green
2003-01-20 0:25 ` Stephen Crawley
2003-01-20 1:21 ` Artur Biesiadowski
2003-01-20 2:11 ` Stephen Crawley
2003-01-20 9:48 ` Dalibor Topic
2003-01-20 0:06 ` Anthony Green
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200301192339.h0JNdufh022135@piglet.dstc.edu.au \
--to=crawley@dstc.edu.au \
--cc=crawley@piglet.dstc.edu.au \
--cc=green@redhat.com \
--cc=mark@klomp.org \
--cc=mauve-discuss@sources.redhat.com \
--cc=robilad@yahoo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).