Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!aioe.org!.POSTED!not-for-mail
From: Roedy Green <see_website@mindprod.com.invalid>
Newsgroups: comp.lang.java.programmer
Subject: Re: The behavior of "equals" method of Arrays.asList() implementation
Date: Tue, 28 Jun 2011 10:04:28 -0700
Organization: Canadian Mind Products
Lines: 15
Message-ID: <ca2k07hsabd50lvcpajobn3dbm265rejeu@4ax.com>
References: <b30a98ec-acc8-4e7b-bb9d-0de48a554d07@g2g2000vbl.googlegroups.com>
Reply-To: Roedy Green <see_website@mindprod.com.invalid>
NNTP-Posting-Host: RCd/Ul4tyxGUBII8WGwa5g.user.speranza.aioe.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Complaints-To: abuse@aioe.org
X-Notice: Filtered by postfilter v. 0.8.2
X-Newsreader: Forte Agent 6.00/32.1186
Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:5735

On Tue, 28 Jun 2011 02:19:02 -0700 (PDT), Alex J <vstrength@gmail.com>
wrote, quoted or indirectly quoted someone who said :

>Basically I wonder if it is safe to use equals for collections (and
>junit's assertEquals in particular which in fact results in the
>*.equals invocation).

Every object implements equals. Sometimes it amounts to == which many
not be what you want.
-- 
Roedy Green Canadian Mind Products
http://mindprod.com
One of the curses of the computer age is manufacturers now design 
home appliances to die on the very day the warranty expires.
It is deliberate waste in the service of mindless profit.