It seems equals is not overridden for arrays, which means that equals in the case of arrays will be testing for object identity. However, wrappers do override equals, and two instances of a wrapper class are equal if they are both instances of the same class, and if the values they hold are equal.
All code in my posts, unless a source is explicitly mentioned, is my own.
To compare int[] you can use the equals function in the Arrays class. , int[])]Arrays
"Any fool can write code that a computer can understand. Good programmers write code that humans can understand." --- Martin Fowler
Please correct my English.
Punit, are you thinking of the equality (==) operator? That's the one that has the restriction for the Integer type of -128 to 127. This case would be no different for equals than the other case.
I forgot to mention that for the == operator to report equal on the Integer objects it is also necessary that they have been created through autoboxing, and not via the new() operator. The new operator will always create a new object on the heap (similar to what happens with Strings and the constant pool.) [ December 29, 2008: Message edited by: Ruben Soto ]
All code in my posts, unless a source is explicitly mentioned, is my own.