Tobias McNulty wrote: > > Thanks for the quick reply. [In the last paragraph,] by return do > you mean release? If so, I'm curious as to how one is supposed to > deal with this Xerces-allocated memory, if normal system functions do > not work.
Normal system functions do work, as long as you use the same C runtime code that Xerces uses. :-) You didn't mention which platform you're having problems with? Typically, this happens under Win32, where you get in trouble when different C runtimes are mixed (msvcrt.dll vs. msvcrtd.dll vs. statically linked CRT, single-threaded vs. multi-threaded). Your Java stuff probably uses the release runtime DLL (msvcrt.dll), hence you should avoid using the debug Xerces DLL. If it still doesn't work, simply create another DLL that uses the same CRT as Xerces and delete your strings in there. Joachim PS: Yes, it would be nice if Xerces provided an API for freeing objects it allocated. -- work: [EMAIL PROTECTED] (http://www.netacquire.com) private: [EMAIL PROTECTED] (http://www.kraut.ca) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
