[ http://issues.apache.org/jira/browse/LANG-238?page=comments#action_12461475 ] Paul Benedict commented on LANG-238: ------------------------------------
The rollback is correct, but that's because the implementation is wrong. The enhancement request is not to compare two arrays of whatever type, but to compare one array of values to make sure they contain the same value -- ala the max and min method signatures. Not: equals(int[], int[]) But: equals(int[]) > [lang] Add equals(type[]) to NumberUtils > ---------------------------------------- > > Key: LANG-238 > URL: http://issues.apache.org/jira/browse/LANG-238 > Project: Commons Lang > Issue Type: Improvement > Affects Versions: Nightly Builds > Environment: Operating System: other > Platform: Other > Reporter: Paul Benedict > Priority: Minor > Fix For: 2.3 > > > It would be useful to add an equals() method like the current min and max > methods which take an array type and determine if all the values are equal. > I have found myself in need of this often. I have to retrieve objects from > multiple data sources in parallel to build an array of complex object. To > ensure > validity, I always compare that my sub-retrievals returned the same number of > objects as expected. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
