This is the mail archive of the
mauve-discuss@sources.redhat.com
mailing list for the Mauve project.
Re: 600+ BigDecimal tests
- From: Stephen Crawley <crawley at dstc dot edu dot au>
- To: Mark Wielaard <mark at klomp dot org>
- Cc: Dalibor Topic <robilad at yahoo dot com>, Anthony Green <green at redhat dot com>, mauve-discuss at sources dot redhat dot com, crawley at piglet dot dstc dot edu dot au
- Date: Mon, 20 Jan 2003 09:39:56 +1000
- Subject: Re: 600+ BigDecimal tests
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