Path: csiph.com!usenet.pasdenom.info!gegeweb.org!eternal-september.org!feeder.eternal-september.org!mx04.eternal-september.org!.POSTED!not-for-mail From: Jim Janney Newsgroups: comp.lang.java.programmer Subject: Re: Need clarification on Object.equals. Date: Tue, 18 Dec 2012 14:24:02 -0700 Organization: bilaterally symmetric Lines: 12 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: mx04.eternal-september.org; posting-host="75975abe3fe3503ca7350803ab98e478"; logging-data="31197"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+PiRqkJ+6xHVLCPMMbeAaB" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (gnu/linux) Cancel-Lock: sha1:FEAfcoC56rBShuhFpyVYoO5/Zbg= sha1:Cf8N3Q1k0srvToDlzPK//zSkSyE= Xref: csiph.com comp.lang.java.programmer:20477 plewto@gmail.com writes: > > Thanks for your response, > > I see where the problem is. I do not directly implement equals, however Node is an extension of AbstractSet which does redefine equals. As it turns out I was in the process of rewriting Node so that it no longer extends AbsteractSet when the anomaly popped up in test code, so it is actually a mote point. And in terms of set equality the test objects are indeed equal, since each represents the empty set. -- Jim Janney