If you link your applications as required, you won't have this problem, and you can delete pointer properly. As far as I'm concerned, this is not-a-bug. If you don't want to play by the rules required by Xerces, transcode the string directly into your own buffer.
This has been discussed endlessly on the list, so a search of the archives
should give you lots of ideas for transcoding without using
DOMString::transcode(). In particular, you should look at the
XMLString::transcode() functions that allow the caller to pass the
destination buffer for the transcoded data.
Dave
Jay Turner
<jay.turner@sabr To: [EMAIL PROTECTED],
Homam Dabis <[EMAIL PROTECTED]>
e.com> cc: (bcc: David N
Bertoni/Cambridge/IBM)
Subject: Xerces Bug 4565 - Memory Leak
in transcode
03/12/2002 11:35
AM
Please respond
to xerces-c-dev
Do you have any more information on this? We are experiencing the same slow
memory leak because we cannot properly delete the returned strings and it
is causing problems.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
