I did some tests of java.io.Serializable's serialVersionUID using cp-tools.
All the VM's used in tests were from Debian testing release.
As a result, kaffe, jamvm, sablevm, and gij showed different results from Sun's java, where gij in GCC-3.4.3 not in Debian testing release showed same one with Sun's.
I guess that there is a problem in java.io.ObjectStreamClass.getClassUID() or its calling methods in GNU Classpath.
What do you think about this?
ykleelinux:~$ kaffe -classpath /home/yklee/project/cp-tools gnu.classpath.tools.serialver.SerialVer java.io.Serializable
java.io.Serializable: static final long serialVersionUID = -8059786540628275649L;
ykleelinux:~$
ykleelinux:~$ jamvm -classpath /home/yklee/project/cp-tools gnu.classpath.tools.serialver.SerialVer java.io.Serializable
java.io.Serializable: static final long serialVersionUID = -8059786540628275649L;
ykleelinux:~$
ykleelinux:~$ sablevm -c /home/yklee/project/cp-tools gnu.classpath.tools.serialver.SerialVer java.io.Serializable
java.io.Serializable: static final long serialVersionUID = -8059786540628275649L;
ykleelinux:~$
ykleelinux:~$ gij -classpath /home/yklee/project/cp-tools gnu.classpath.tools.serialver.SerialVer java.io.Serializable
java.io.Serializable: static final long serialVersionUID = -8059786540628275649L;
ykleelinux:~$
ykleelinux:~$ /usr/local/gcc-3.4.3/bin/gij -classpath /home/yklee/project/cp-tools gnu.classpath.tools.serialver.SerialVer java.io.Serializable java.io.Serializable: static final long serialVersionUID = 1196656838076753133L;
ykleelinux:~$
ykleelinux:~$ java -classpath /home/yklee/project/cp-tools gnu.classpath.tools.serialver.SerialVer java.io.Serializable
java.io.Serializable: static final long serialVersionUID = 1196656838076753133L;
_______________________________________________ Classpath mailing list [email protected] http://lists.gnu.org/mailman/listinfo/classpath
