There are overloaded XMLString::transcode() methods
where you pass your own buffer in.  I believe that these
will avoid the problem since your app (whatever lib)
can both allocate and free the memory.

Also, if you can organize your algorithm so that it
reuses a single transcode buffer, you can increase
performance since you're not hitting the memory
management system as much.  Works for us...

- Rich Taylor, Application Developer, WebMD

-----Original Message-----
From: Lyman Neuschaefer [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, April 18, 2001 4:50 PM
To: '[EMAIL PROTECTED]'
Subject: RE: Deallocating memory allocated by XMLString::transcode on
Win3 2 platform


Thanks for all of your replies.  

I have linked the app using "debug multithreaded" versions of 
all the libraries on which it depends, including Xerces and the CRT.
However, I'm encountering the same assertion failure 
on attempting to delete "XMLString::transcode"-allocated memory.
 
I may have more success with "debug multithreaded dll" versions,
but would prefer not to depend on any dll's.  Is there some way
to use Xerces as a debug multithreaded static library and not incur
memory leaks?

Thanks,

Lyman

-----Original Message-----
From: Ken Goldman [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, April 18, 2001 11:41 AM
To: Lyman Neuschaefer
Subject: XMLString::transcode


> Sorry for not having consulted the FAQ.  How silly of me.

You're not the only one.  In fact, I wonder if anyone has ever gotten
it right the first time.

> The FAQ says that the problem is due to mixing of runtimes, 
> as you say.  However, I'm using the Debug version of the Xerces
> library, as well as the Debug version of the CRT.  What else might
> be the problem?

It should be the debug *** DLL *** version.

-- 
Ken Goldman   [EMAIL PROTECTED]   914-784-7646

---------------------------------------------------------------------
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]

Reply via email to