(XML4C) DOMParser constructor crash
-
Do you know what would cause the construction of a Xerxes DOM parser to die? It seems like this should be valid, but I'm obviously missing something.
// DOM newbie test
DOMParser* pDomParser = new DOMParser(); // crashes
ASSERT (pDomParser != NULL);
delete pDomParser;Are we required to derive from
DOMParserand override certain methods? Btw, I'm using a prebuilt binary of the XML4C 4.0.0 implementation. A ptr to the API docs would also be much appreciated. Thanks! /ravi Let's put "civil" back in "civilization" http://www.ravib.com ravib@ravib.com -
Do you know what would cause the construction of a Xerxes DOM parser to die? It seems like this should be valid, but I'm obviously missing something.
// DOM newbie test
DOMParser* pDomParser = new DOMParser(); // crashes
ASSERT (pDomParser != NULL);
delete pDomParser;Are we required to derive from
DOMParserand override certain methods? Btw, I'm using a prebuilt binary of the XML4C 4.0.0 implementation. A ptr to the API docs would also be much appreciated. Thanks! /ravi Let's put "civil" back in "civilization" http://www.ravib.com ravib@ravib.comAre you calling the Initialize routine? XMLPlatformUtils::Initialize(); What version are you using if not? "We are what we repeatedly do. excellence, then, is not an act, but a habit." Aristotle
-
Are you calling the Initialize routine? XMLPlatformUtils::Initialize(); What version are you using if not? "We are what we repeatedly do. excellence, then, is not an act, but a habit." Aristotle
Thanks Michael, that did the trick! I ended up with a purported memory leak, but the Xerxes docs say the diagnostic overagressive and can be ignored. I then switched from XML4C V4 to V5 and encountered a new problem: When I build my (simple) Xerces test project, VC++ complains that
DOMDocument(present in several Xerces header files) is an ambiguous symbol. The clash seems to occur as a result of the Platform SDK (Aug 2002) being installed on my system. Do you know how I get around this problem? Thanks, /ravi Let's put "civil" back in "civilization" http://www.ravib.com ravib@ravib.com -
Thanks Michael, that did the trick! I ended up with a purported memory leak, but the Xerxes docs say the diagnostic overagressive and can be ignored. I then switched from XML4C V4 to V5 and encountered a new problem: When I build my (simple) Xerces test project, VC++ complains that
DOMDocument(present in several Xerces header files) is an ambiguous symbol. The clash seems to occur as a result of the Platform SDK (Aug 2002) being installed on my system. Do you know how I get around this problem? Thanks, /ravi Let's put "civil" back in "civilization" http://www.ravib.com ravib@ravib.comI actually have not used the Xerces C since last Jan, so I am afraid no. Have you downloaded the current release. There was an update the end of August so maybe it was addressed with that revision. "We are what we repeatedly do. excellence, then, is not an act, but a habit." Aristotle
-
I actually have not used the Xerces C since last Jan, so I am afraid no. Have you downloaded the current release. There was an update the end of August so maybe it was addressed with that revision. "We are what we repeatedly do. excellence, then, is not an act, but a habit." Aristotle
Yes, I'm using the latest release. I've switched back to version 4 to get around the symbol clash. Thanks for your help! /ravi Let's put "civil" back in "civilization" http://www.ravib.com ravib@ravib.com