Yes, return=release. I can't speak for everyone, but when I upgraded the BCB Xerces library, I intentionally made it dependent upon the BCB c-rtl (cc3250mt.dll) so that the application and the library could use a common memory manager, until such time that Xerces implements a solution to the problem.
Another solution would be to link Xerces into your application and eliminate the dll altogether. I personally have not succeeded in doing this, but someone recently published how to do this using the MSVC built library. I also recall reading a while back where someone rebuilt Xerces and included a routine to release transcoded buffers. I don't believe those changes made it into the "official" sources. Don At 02:12 PM 12/28/2001 -0500, you wrote: >Hi Don, > >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. > >Thanks, > >Toby > >>Sounds like a heap collision between different memory managers. Transcode >>allocates the char* buffer returned to your program. If your program >>utilizes a different memory manager that that of Xerces, you are >>effectively releasing memory that you didn't allocate. >> >>To the best of my knowledge, Xerces has not implemented a function >>through which you can return memory that was allocated by Xerces. >> >>HTH, >>Don > >-- >Tobias McNulty >Data Description, Inc. >840 Hanshaw Road, Suite 9 >Ithaca, NY 14850 >Phone: (607) 257-1000 >E-mail: [EMAIL PROTECTED] >Web: www.datadesk.com > >--------------------------------------------------------------------- >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]
