RE: Faulty documentation in header of XMLString.h??

[David N Bertoni/Cambridge/IBM]

Xerces-C for WIn32 ships with 2 DLLs -- one that's a release build and one
that's a debug build, so you need to choose the correct import library for
linking.  That's xerces-c_2.lib or xerces-c_2D.lib, depending on your
configuration.

Dave



                                                                                       
                                                
                      "Samar Lotia"                                                    
                                                
                      <[EMAIL PROTECTED]         To:      
"'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>                  
                      om>                      cc:      (bcc: David N 
Bertoni/Cambridge/IBM)                                           
                                               Subject: RE: Faulty documentation in 
header of XMLString.h??                            
                      09/26/2002 01:30                                                 
                                                
                      PM                                                               
                                                
                      Please respond                                                   
                                                
                      to xerces-c-dev                                                  
                                                
                                                                                       
                                                
                                                                                       
                                                



If you are using the debug multithreaded DLL you need to build your own
copy
of xerces with debug DLL. The shipped binaries use the non-debug
multithreaded DLL runtime and that uses a different allocator. The debug C
runtime cannot "delete" a pointer "new"-ed by the release C runtime.

-----Original Message-----
From: Vijay Ganapati [mailto:[EMAIL PROTECTED]]
Sent: Thursday, September 26, 2002 3:29 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: Faulty documentation in header of XMLString.h??


I sure am building it as Debug Multithreaded DLL (one of those things i do
when i start a new project is religiously do this and also get rid of
smart-ass precompiled header settings)

It is possible that since i just used the zipped
binaries off the bat, (which probably have just the release
versions??) that COULD be a problem. But have you tried this and does it
work fine??!!

----- Original Message -----
From: "David Schulze" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, September 26, 2002 1:11 PM
Subject: RE: Faulty documentation in header of XMLString.h??


> If using Win32 verify that you are building as MultiThreaded DLL (or
Debug
> MultiThreaded DLL)
>
> -----Original Message-----
> From: Vijay Ganapati [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, September 26, 2002 4:10 PM
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Faulty documentation in header of XMLString.h??
>
>
> When i do
>
> char * pmychar =
>
XMLString::transcode(pDOMNamedNodeMap->getNamedItem(L"id")->getNodeName());
>
> then, going by the documentation, i should delete pmychar so:
>
> delete[] pmychar;
>
> However it crashes, and i suspect the pmychar returned is not dynamically
> allocated as the documentation seems to assert??
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


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



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





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