-
Bug
-
Resolution: Fixed
-
P4
-
1.4.0
-
None
-
tiger
-
generic, x86
-
generic, windows_2000
The following problem was originally reported in 4634068.
There are a number of classes that do not respect the
implied contract for equals and hashCode. See, for example,
Joshua Bloch's book "Effective Java", items 7-8.
java.awt.DisplayMode defines
equals(java.awt.DisplayMode) but doesn't redefine
equals(Object)
Problems found by applying automatic tools to JDK
libraries. However, manual inspectation of the classes
reveals the same problems.
-- iag@sfbay 2002-02-06
There are a number of classes that do not respect the
implied contract for equals and hashCode. See, for example,
Joshua Bloch's book "Effective Java", items 7-8.
java.awt.DisplayMode defines
equals(java.awt.DisplayMode) but doesn't redefine
equals(Object)
Problems found by applying automatic tools to JDK
libraries. However, manual inspectation of the classes
reveals the same problems.
-- iag@sfbay 2002-02-06
- duplicates
-
JDK-4529353 java.awt.DisplayMode.equals( DisplayMode ) does not check for null
-
- Closed
-
-
JDK-4867213 Wrong equals() method signature in java.awt.DisplayMode
-
- Closed
-
- relates to
-
JDK-4977139 Inifinite loop possible in DisplayMode.equals(Object)
-
- Resolved
-
-
JDK-4634068 JDK code doesn't respect contract for equals and hashCode
-
- Closed
-