From 13fe8fc9303de1444d5070f7efae7137d77e349d Mon Sep 17 00:00:00 2001 From: Michael Bayne Date: Sat, 20 Oct 2007 18:50:27 +0000 Subject: [PATCH] On second thought, reference equality is really the only appropriate thing for DObject. There will never be multiple instances with the same oid that represent "equal" objects and it's possible that in certain (controlled and limited) cirumstances, objects with different object managers might have the same oid even though they are different objects. git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@4853 542714f4-19e9-0310-aa3c-eee0fc999fb1 --- .../com/threerings/presents/dobj/DObject.java | 17 ----------------- 1 file changed, 17 deletions(-) diff --git a/src/java/com/threerings/presents/dobj/DObject.java b/src/java/com/threerings/presents/dobj/DObject.java index 95b6c4f9b..af40acc38 100644 --- a/src/java/com/threerings/presents/dobj/DObject.java +++ b/src/java/com/threerings/presents/dobj/DObject.java @@ -600,23 +600,6 @@ public class DObject return buf.append("]").toString(); } - @Override // from Object - public int hashCode () - { - return _oid; - } - - @Override // from Object - public boolean equals (Object other) - { - if (other == null) { - return false; - } else if (!getClass().equals(other.getClass())) { - return false; - } - return _oid == ((DObject)other).getOid(); - } - /** * Used to briefly describe this distributed object. */