This is the mail archive of the
mauve-discuss@sourceware.cygnus.com
mailing list for the Mauve project.
significance of double test?
- To: mauve-discuss at sourceware dot cygnus dot com
- Subject: significance of double test?
- From: Peter Naulls <peter at erble dot freeserve dot co dot uk>
- Date: Thu, 09 Mar 2000 14:25:44 +0000
This is the first test from new_Double:
// Some broken implementations convert "7.79625120912E289" to
// the value 7.796251209119999E289.
harness.check (new Double("7.79625120912E289").toString (),
"7.79625120912E289");
Can someone tell me the significance of this test? i.e., what's
the precise behaviour that's likely to result in the wrong value?
The reason I ask is that my JVM exhibits the undesirable value, and
I'm wondering what can be done to fix it.
Additionally, since my JVM is being developed on a non-unix platform,
and while I've found the Mauve suite itself phenomenally useful, the
scripts which are used to run the test aren't useable at all. To
overcome this, I've written a "FullTestHarness" class, which parses
a list of test cases, keeps a running % count, and also can discount
tests (due to library faults, not JVM faults, etc). If anyone
would like to see this, let me know.
Peter
--
+---------------------------------------------+-----------------------------+
| Peter Naulls - pnaulls@usa.net | |
| http://free.prohosting.com/~chocky/ | Java and JVM Consultant |
| Java for RISC OS and ARM - java-arm@usa.net | Technical Author |
| http://free.prohosting.com/~chocky/java/ | Program performance analyst |
+---------------------------------------------+-----------------------------+