PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT
ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW
AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE
DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL
BE LOST SOMEWHERE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3347

*** shadow/3347 Wed Aug 29 13:57:14 2001
--- shadow/3347.tmp.6279        Wed Aug 29 13:57:14 2001
***************
*** 0 ****
--- 1,33 ----
+ +============================================================================+
+ | Memory deallocation                                                        |
+ +----------------------------------------------------------------------------+
+ |        Bug #: 3347                        Product: Xerces-C++              |
+ |       Status: NEW                         Version: 1.5.1                   |
+ |   Resolution:                            Platform: PC                      |
+ |     Severity: Enhancement              OS/Version: Windows 9x              |
+ |     Priority: Other                     Component: Utilities               |
+ +----------------------------------------------------------------------------+
+ |  Assigned To: [EMAIL PROTECTED]                                  |
+ |  Reported By: [EMAIL PROTECTED]                                           |
+ |      CC list: Cc:                                                          |
+ +----------------------------------------------------------------------------+
+ |          URL:                                                              |
+ +============================================================================+
+ |                              DESCRIPTION                                   |
+ I am proposing a solution to the DOM_String::transcode() allocation problem. 
+ (If the calling application is statically linked to the runtime and Xerces is
+ dynamically linked, the memory is allocated from one heap, and the calling
+ application cannot successfully free it)
+ 
+ Occaisionally, there is a need to create an application that is statically
+ linked to the runtime.  Rather than building a custom version of Xerces which is
+ statically linked to the runtime, I propose that a simple function be added (to
+ XMLPlatformUtils?) to release memory.
+ 
+ I have implemented a version of this for my project, and found that it works
+ very well.
+ 
+ void XMLPlatformUtils::Free(void *p) 
+ {
+   free(p); 
+ }

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to