t to fudge the Xerces
stuff.
Good luck.
-Original Message-
From: Paul Rivera [mailto:[EMAIL PROTECTED]
Sent: 24 December 2004 09:29
To: xerces-c-dev@xml.apache.org
Subject: Re: XMemory and MFC
Thanks for replying. I commented out the "#define new
DEBUG_NEW". I'm still
Thanks for replying. I commented out the "#define new
DEBUG_NEW". I'm still getting the same compile
errors. Is xerces-2.6.0 supposed to work with mfc
out-of-the-box? Has anyone tried it?
--- Alberto Massari <[EMAIL PROTECTED]> wrote:
> Hi Paul,
> have you tried removing the "#define new DEBU
Hi Paul,
have you tried removing the "#define new DEBUG_NEW" definition? When that
macro is enable, all attempts to use a placement new will fail (regardless
if Xerces is involved or not)
Alberto
At 22.06 22/12/2004 -0800, Paul Rivera wrote:
I compiled it with xerces-c-2.6.0 and I'm still
gettin
I compiled it with xerces-c-2.6.0 and I'm still
getting errors from XMemory.hpp. Some of the lines
which Visual Studio points out are:
void* operator new(size_t size);
void* operator new(size_t size, const char* file, int
line);
void operator delete(void* p, const char* file, int
line);
void* ope
Hey,
Has this been fixed in xerces-c++-2.6.0? If yes,
maybe I could just download it.
Yes, and there have been lots of other improvements, if you can,
download it.
Else, can you tell me
how to fix this? If its a patch file, I have a couple
of questions.
1.) do I run it with "patch -p2 <
Hi! My application is having compilation errors due to
the XMemory.cpp and XMemory.hpp. I'm using
xerces-c++-2.4.0. I've gone through a couple of posts
and found out that it was due to the preprocessor
directive visual studio uses with debug mode:
#ifdef _DEBUG
#define new DEBUG_NEW
#endif
Ha
