Hi there (again :-() It may be a little bit long, so I'd like to apologize first.
I'm trying (for my work) to add a functional layer to the xerces library so that other developers can use it by calling some more functional methods. The point is also to raise some particular type of exception so that it can be easily reused. When I directly implement some code to create a small XML file (see previous posts), it works perfectly. All my objects are released, and I'm happy. (the code is here http://www.nabble.com/file/p23402427/bjtotestGood.cxx bjtotestGood.cxx ) But I try to encapsulate that into a more functional way, I get a memory leak. First I though of doing some nice Oriented Object Programming and subclass some of the xerces objects (DOMElement and DOMDocument especially), but I found out that these classes are pure virtual classes and I can't subclass them without redefining all the pure virtual methods. I tried to subclass the implementation objects (i.e. DOMElementImpl and DOMDocumentImpl) but I'm stuck with all the Factories and Singeltons (DOMIplementation and DOMIplementationRegirsty mainly). So I decide to create some functional objects from scratch (XMLElement and XMLDocument) that would not inherit from DOMElement and DOMDocument, but have theses objects as members of my classes. But when I do that, and I re-implement the small program to generate some small XML files, I get a memory leak... I just don't understand, since I do exactly the same thing that I was doing first. I joined the source code here so that, if you feel willing to help, you can get the code : http://www.nabble.com/file/p23402427/batchTest.rar batchTest.rar I cleaned the code (we use several libraries) so that it could compile and run on any (i hope) UNIX server. I run it on an AIX 5.1 Thanks a lot if you got here, and thanks a lot in advance for your help. -- View this message in context: http://www.nabble.com/Memory-leak-over-and-over...-tp23402427p23402427.html Sent from the Xerces - C - Dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
