(where INTERPRETER == gij || Sun j2sdk 1.4 java)
produced almost identical files but there were a few small differences.
I also haven't looked into this yet. (diff attached)
But this is probably one of the runtimes picking up a constant from its
own runtime library and not from the GNU Classpath glibj.zip file.
--- gij.out 2002-11-14 22:18:50.000000000 +0100
+++ j2sdk.out 2002-11-14 22:18:26.000000000 +0100
@@ -640,7 +640,7 @@
java.lang,Compiler!wait(J,I) Pcif V*java.lang.InterruptedException
java.lang,Double! Pcif class#-9172774392245257468:java.lang.Number:java.lang.Object*java.lang.Comparable*java.io.Serializable
java.lang,Double!#MAX_VALUE Pcsf D:1.7976931348623157E308
-java.lang,Double!#MIN_VALUE Pcsf D:5.0E-324
+java.lang,Double!#MIN_VALUE Pcsf D:4.9E-324
This diff is a result of bugs in Double.toString() within the VM. It is
the underlying double value in both VMs, but a different string
representation. The correct string is "4.9E-324". Perhaps japize
should use Double.doubleToLongBits() to compare the bitwise value of
double constants (likewise Float.floatToIntBits()).
-java.lang,Float!#MIN_VALUE Pcsf F:1.4012985E-45
+java.lang,Float!#MIN_VALUE Pcsf F:1.4E-45
Likewise. The correct string should be "1.4E-45".
--
This signature intentionally left boring.
Eric Blake [EMAIL PROTECTED]
BYU student, free software programmer
_______________________________________________
Classpath mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/classpath
