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=24535>. 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=24535 Memory allocation problem in MemBufInputSource class [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Additional Comments From [EMAIL PROTECTED] 2003-11-09 22:16 ------- Hello. I think perhaps you might not have grasped the purpose of the last parameter: If you have allocated memory for the XML input that you want the parser to deallocate, you set the parameter to true and it will deallocate it. If you don't want this to happen--and obviously you don't if the memory in question was allocated on the stack--then you simply set the fourth parameter of the constructor to false, and the parser will let the memory be. It is up to your application to make sure that it knows the difference between memory that it does and does not want the parser to deallocate. The reason this flexibility exists is that there are times when you can save a mem copy this way. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
