Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.java.programmer > #5735

Re: The behavior of "equals" method of Arrays.asList() implementation

Show all headers | View raw

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.

Back to comp.lang.java.programmer | Previous | Next — Previous in thread | Find similar

Thread

The behavior of "equals" method of Arrays.asList() implementation Alex J <vstrength@gmail.com> - 2011-06-28 02:19 -0700
  Re: The behavior of "equals" method of Arrays.asList() implementation Eric Sosman <esosman@ieee-dot-org.invalid> - 2011-06-28 07:08 -0400
    Re: The behavior of "equals" method of Arrays.asList() implementation Lew <noone@lewscanon.com> - 2011-06-28 07:29 -0400
  Re: The behavior of "equals" method of Arrays.asList() implementation Roedy Green <see_website@mindprod.com.invalid> - 2011-06-28 10:04 -0700

csiph-web