Phil Steitz wrote:
When implementing hashCode I noticed that equals was distinguishing <x,NaN> from <NaN, y>, which is not consistent with isNaN. I changed the semantics to make <*,NaN> == <NaN,*> == Complex.NaN.
I'm not sure I understand your change, but IIRC IEEE 745 requires that a NaN doesn't compare equal to anything, including itself. This would probably mean a Complex with a NaN component shouldn't compare equal to anything. I may misremember something though. J.Pietschmann --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
