Hello-

I am running on Windows XP. We recently upgraded our development environment to VS 
.net 2003. Since we upgraded, I have been having a problem where a debug assert occurs 
when we delete a string created by XMLString::transcode. I noticed a note about this 
on http://xml.apache.org/xerces-c/faq-build.html#faq-12 . I see the problem in xerces 
1.6 and in xerces 2.3 (I upgraded trying to solve the problem.)

1) Why did this used to work and why does it not work any more?

2) For for strings created by XMLString::transcode I can deallocate them using 
XMLString::release as suggested in the link above, however I have the same debug 
assert with the delete of an SAX2XMLREADER created by 
XMLReaderFactory::createXMLReader, and that has no release method for me to switch to. 
 createXMLReader's comment even says I'm supposed to delete it myself.

3) Is the problem really because xerces-c comes with a VS .net 2002 xerces-all.sln 
(solution) file with which to compile it, and my code is using vs .net 2003? So I am 
calling a vs02 created dll from a vs03 created dll. I then tried to upgrade the 
xerces-all.sln file to a VS .net 2003 .sln. But when I compile it I get loads of 
errors. Here is just the start of 102 errors I get when I compile XercesLib in vs .net 
2003:

..\..\..\..\..\src\xercesc\validators\common\CMLeaf.hpp(143) : error C2226: syntax 
error : unexpected type 'xercesc_2_3::QName'
..\..\..\..\..\src\xercesc\validators\common\CMLeaf.hpp(143) : error C2238: unexpected 
token(s) preceding ';'
..\..\..\..\..\src\xercesc\validators\common\CMLeaf.hpp(212) : error C2511: 
'xercesc_2_3::CMLeaf::CMLeaf(xercesc_2_3::QName *const ,const unsigned 
int,xercesc_2_3::MemoryManager *const )' : overloaded member function not found in 
'xercesc_2_3::CMLeaf'
..\..\..\..\..\src\xercesc\validators\common\CMLeaf.hpp(136) : see declaration of 
'xercesc_2_3::CMLeaf'

4) As an interesting side note, when I did compile the xerces-all.sln in VS .net 2002 
that came with the source code   it would not link with out unresolved externals until 
I commented out the unimplemented copy constructor of XMemory in XMemory.hpp

Thank you, I would really appreciate any suggestions.
Virginia

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

Reply via email to