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=21990>. 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=21990 ICULCPTranscoder::transcode memory leak ------- Additional Comments From [EMAIL PROTECTED] 2003-08-25 16:13 ------- OK, let me see if I can express this more coherently than I did in the previous response. If you reserve a byte for null-termination, then you will not need the code to re-allocate and copy the string as your patch does. Yes, you will end up re- transcoding more strings, but I'm not convinced making the code more complicated for one edge case is worthwhile. Code which can handle all failure cases would not be that much more complicated, if this function is meant to be truly efficient. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
