Comments on: A Java Gotcha

By: The Cheap Sitcom Clip Scene Blog Post | Enfranchised Mind

The Cheap Sitcom Clip Scene Blog Post | Enfranchised Mind — Tue, 15 Jul 2008 05:07:11 +0000

[...] “I just realized that my code has a possible infinite recursion case. Specifically, if two ThreeDeePoint objects compare to eachother, they’ll end up spinning infinitely into the abyss.” (A Java Gotcha) [...]

By: Robert Fischer

Robert Fischer — Mon, 29 Oct 2007 18:17:43 +0000

I just posted an update on this:

http://enfranchisedmind.com/blog/archive/2007/10/29/419

That’s analyzing whether this relationship is appropriate or not.

Although, yes, all inheritance problems can be solved by not doing inheritance.

By: JQ

JQ — Sat, 27 Oct 2007 21:21:51 +0000

I think ThreeDeePoint should not extend TwoDeePoint. Instead of using “is a” relationship.. try using a “has a” relationship.. ThreeDeePoint has a TwoDeePoint. I think that could solve your equals/compareTo issues. That’s all I have for now.

By: Enfranchised Mind » Another solution to the Java equals/compareTo Problem (More or Less)

Mon, 26 Feb 2007 21:37:46 +0000

[...] There is an partial solution to that annoying Java equals/compareTo issue. After you know that the object that you are comparing to is apparently equal to you, you then need to return this.hashCode() == them.hashCode(). Assuming people have properly overridden hashCode, this should mostly keep you safe. [...]

By: Enfranchised Mind

Enfranchised Mind — Fri, 12 Jan 2007 18:16:44 +0000

Commons-Lang and the equals()/compareTo() Debacle…

Like most traumatic realizations, I’ve been having trouble getting the fundamental equals/compareTo brokeness of Java out of my head.
I decided to take a look at the Commons-Lang library to see how they deal with it. They’ve got a class ca…