This is a bug in Java 3D 1.1 that is fixed in 1.2_alpha1.
--
Kevin Rushforth
Java 3D Team
Sun Microsystems
[EMAIL PROTECTED]
>Date: Wed, 10 Nov 1999 12:17:38 +0100
>From: Marco Lohse <[EMAIL PROTECTED]>
>Subject: [JAVA3D] hashCode() Function ?
>To: [EMAIL PROTECTED]
>
>Hello,
>I read in the Java 3D API for Tuple3f.hashCode():
>"Two different Tuple3f objects with identical data values (ie, returns true
>for equals(Tuple3f) ) will return the same hash number. Two tuples with
>different data members may return the same hash value, although this is not
>likely."
>
>but I get these very, very unlikely results:
>
>Tuple3f (1.0, -1.0, 1.0) hashCode() -1082130432
>Tuple3f (-1.0, 1.0, 1.0) hashCode() -1082130432
>Tuple3f (-1.0, -1.0, -1.0) hashCode() -1082130432
>Tuple3f (1.0, 1.0, -1.0) hashCode() -1082130432
>Tuple3f (1.0, 1.0, 1.0) hashCode() 1065353216
>Tuple3f (-1.0, -1.0, 1.0) hashCode() 1065353216
>Tuple3f (-1.0, 1.0, -1.0) hashCode() 1065353216
>...
>
>This must be a miracle ;-( Marco.
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JAVA3D-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
