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

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

From	Eric Sosman <esosman@ieee-dot-org.invalid>
Newsgroups	comp.lang.java.programmer
Subject	Re: The behavior of "equals" method of Arrays.asList() implementation
Date	2011-06-28 07:08 -0400
Organization	A noiseless patient Spider
Message-ID	<iuccqd$i9p$1@dont-email.me> (permalink)
References	<b30a98ec-acc8-4e7b-bb9d-0de48a554d07@g2g2000vbl.googlegroups.com>

Show all headers | View raw

On 6/28/2011 5:19 AM, Alex J wrote:
> 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).
>
> One of collection instances I am working with is returned from
> Arrays.asList(..) method invocation.
> Sun JDK sources defines no equals method for
> java.util.Arrays.ArrayList inner class so I guess it is not safe to
> compare collections in that way.

     Look again.  The nested class extends AbstractList, and
inherits the equals() implementation from it.

-- 
Eric Sosman
esosman@ieee-dot-org.invalid

Back to comp.lang.java.programmer | Previous | Next — Previous in thread | Next 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