You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@commons.apache.org by bu...@apache.org on 2003/12/11 23:23:31 UTC

DO NOT REPLY [Bug 25454] - new StringUtils.replaceChars behaves differently from old CharSetUtils.translate

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25454>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25454

new StringUtils.replaceChars behaves differently from old CharSetUtils.translate

ggregory@seagullsw.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED



------- Additional Comments From ggregory@seagullsw.com  2003-12-11 22:23 -------
Well, this is a tricky one. I feel the basic problem is that the Javadoc
underspecifies the behavior of both methods, so perhaps we could discuss first
what the behavior /should be/. 

The heart of the problem is that the CharSetUtils method is a one pass map-style
of method, while the StringUtils method is not, it uses a nested loop, which is
somewhat contradictory to the Javadoc comment of doing the work "in one go".

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org