Re: array[].equal
From: Chris Riesbeck (criesbeck_at_yahoo.com)
Date: 06/10/04
- Next message: GIMME: "Re: JDOM: java.lang.NoClassDefFoundError: org/jdom/Content"
- Previous message: Chris Roe: "Performance problems on Intel but not AMD... strange"
- In reply to: Murray: "Re: array[].equal"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 10 Jun 2004 13:28:35 -0500
In article <40c82cad$0$8988$afc38c87@news.optusnet.com.au>,
"Murray" <parps@SPAMOFFoptusnet.SPAMMAGE.com.au> wrote:
> "Roedy Green" <look-on@mindprod.com.invalid> wrote in message
> news:eehfc0l86crqv2kehavju62jap21vjlo5k@4ax.com...
> > Where do you look in the JavaDoc to find out just how clever
> > equal is on
> >
> > comparing two byte[], two int[] or two Object[]
> >
>
> Array doesn't implement equals(), so the method is the standard equals()
> inherited from Object. Hence no iteration logic is performed if that's what
> you mean. Have a look at Arrays.equals instead ...
Or was the question about == and where to look?
In that case, I believe things like this are only in the Java
Language Specification (Sec 15.21), not the javadocs.
== for arrays is explicitly described in 15.21.3
- Next message: GIMME: "Re: JDOM: java.lang.NoClassDefFoundError: org/jdom/Content"
- Previous message: Chris Roe: "Performance problems on Intel but not AMD... strange"
- In reply to: Murray: "Re: array[].equal"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|