xerces 2.5 Problems with transcode and also with get*Count functions

Hi, I'm trying to implement a saxparser and got some problems when trying to parse the files.Actually I have an xml factory object which return the appropiate parser (Dom or SAX2) according to what the user specifies. The final idea is to parse an XML file, and get some specific tags but first i wa

RE: delete[] problems with transcode

thanks for your help -Original Message- From: Tinny Ng [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 01, 2001 3:48 PM To: [EMAIL PROTECTED] Subject: Re: delete[] problems with transcode "Christy, Rich" wrote: > However, I do see several references to possib

Re: delete[] problems with transcode

"Christy, Rich" wrote: > However, I do see several references to possible > leaks in IDeepNodeListPool within calls to IDOM_NodeList > getElementsByTagName(). Any ideas? > > Thanks > > Rich I just looked into the code again, I think there is a small leak on the pool instance. Anyway, I just ch

RE: delete[] problems with transcode

getElementsByTagName(). Any ideas? Thanks Rich -Original Message- From: Alberto Massari [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 31, 2001 10:29 AM To: [EMAIL PROTECTED] Subject: Re: delete[] problems with transcode At 08:08 AM 10/31/2001 -0800, you wrote: >"Christy, Ric

Re: delete[] problems with transcode

At 08:08 AM 10/31/2001 -0800, you wrote: >"Christy, Rich" wrote: > > > Actually purify was complaining of a memory leak with the list until I > > deleted it. > >There may be an IDOM leak bug How does the caller retrieve parameter >"const IDOM_Element *parentElement" ? If it is from the par

RE: delete[] problems with transcode

OK, I'll give that a try. Thanks -Original Message- From: Tinny Ng [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 31, 2001 10:09 AM To: [EMAIL PROTECTED] Subject: Re: delete[] problems with transcode "Christy, Rich" wrote: > Actually purify was complaining of

Re: delete[] problems with transcode

"Christy, Rich" wrote: > Actually purify was complaining of a memory leak with the list until I > deleted it. There may be an IDOM leak bug How does the caller retrieve parameter "const IDOM_Element *parentElement" ? If it is from the parser, then memory should be released when the parse

Re: delete[] problems with transcode

"Christy, Rich" wrote: > What about what transcode returns. I thought any memory returned from that > was the clients responsibility to delete. > Yes, so "delete[] transcodedElement" should be kept. I only said that "delete list" not needed. Tinny -

RE: delete[] problems with transcode

. Just a guess. It doesn't hold water if this is in fact the leak that Purify was complaining about. -Original Message- From: Christy, Rich [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 31, 2001 10:22 AM To: '[EMAIL PROTECTED]' Subject: RE: delete[] problems with trans

RE: delete[] problems with transcode

]] Sent: Wednesday, October 31, 2001 7:47 AM To: [EMAIL PROTECTED] Subject: Re: delete[] problems with transcode Rich, I don't think it's related to transcode. There's no need to "delete list", the IDOM implementation has its own memory management. The only explicit delete

RE: delete[] problems with transcode

What about what transcode returns. I thought any memory returned from that was the clients responsibility to delete. -Original Message- From: Tinny Ng [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 31, 2001 7:47 AM To: [EMAIL PROTECTED] Subject: Re: delete[] problems with transcode

Re: delete[] problems with transcode

/ need to delete list only (destructor does not delete elements in list) >delete list; > >return element; > } > > I core dumps on the call to transcode. > > Thanks, > > Rich > > -Original Message- > From: Tinny Ng [mailto:[EMAIL PROTECTED]] > Sent:

RE: delete[] problems with transcode

iginal Message- From: Tinny Ng [mailto:[EMAIL PROTECTED]] Sent: Tuesday, October 30, 2001 4:01 PM To: [EMAIL PROTECTED] Subject: Re: delete[] problems with transcode Christy, Can you post more detail, e.g. how does IDOMStreamer::findElement call transcode()? Thanks! Tinny "Christy,

Re: delete[] problems with transcode

Christy, Can you post more detail, e.g. how does IDOMStreamer::findElement call transcode()? Thanks! Tinny "Christy, Rich" wrote: > After downloading and installing 1.5.2 official release, I started having > core dumps calls to XMLString::transcode. The errors appear to be problems > with new

problems with transcode

Hi, I am using Xerces 1.4 with C++ Builder. I have the following code: char *attrValC = parent_node.getNodeName().transcode(); AnsiString nodeName = attrValC; delete[] attrValC; I've noticed that I have memory leak here. Where I run the program with the CodeGuard I get "Bad object array ..." m