DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=27661>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=27661
[lang] [patch] ArrayUtils.addAll doesn't always return new array
------- Additional Comments From ggregory@seagullsw.com 2004-03-15 18:09 -------
I think we need to discuss this. You are correct that the Javadoc states that a
new array is returned but the Javadoc ALSO states the special cases:
ArrayUtils.addAll(array1, null) = array1
ArrayUtils.addAll(null, array2) = array2
Which clearly show the boundary cases. So the code and Javadoc DO match. The
real question for the API is: Should a new array ALWAYS be created?
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
|