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
This commit is contained in:
@@ -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.
|
||||
*/
|
||||
|
||||
Reference in New Issue
Block a user