: <[EMAIL PROTECTED]>
cc:
Subject: RE: Disabling C++ Namespace
Have you looked for forward declarations of DOM_Node?
Adam Heinz
Development Consultant
Exstream Software
-Original Message-
From: Stephanie L Milchak [mailto:[EMAIL PROTECTED]
Sent
On Tue, 2003-12-23 at 09:09, Stephanie L Milchak wrote:
> But the DOM_* class isn't what causes the linking error... when I
> disable the namespace in xerces I have no errors. I still haven't
> solved any problems.
Are you certain you are linking to the correct xerces lib?
Here is the contents
[EMAIL PROTECTED]
cc
12/23/2003 08:55
AMSubject
Have you looked for forward declarations of DOM_Node?
Adam Heinz Development Consultant Exstream Software
-Original Message-From: Stephanie L Milchak
[mailto:[EMAIL PROTECTED]Sent: Tuesday, December 23, 2003 10:51
AMTo: [EMAIL PROTECTED]Subject: RE: Disabling
C++ NamespaceI
t; <[EMAIL PROTECTED]>
12/23/2003 10:08 AM
Please respond to xerces-c-dev
To: <[EMAIL PROTECTED]>
cc:
Subject: RE: Disabling C++ Namespace
I think the problem doesn't lie in the declaration of the function, but in its
I think the problem doesn't lie in the
declaration of the function, but in its invocation. I suspect that you
have a non-XERCES_CPP_NAMESPACE:: forward declaration of DOM_Node somewhere and
that is causing the linker to look for PrintDOMTree(class DOM_Node instead of PrintDOMTree(class
XERC
to xerces-c-dev
To: <[EMAIL PROTECTED]>
cc:
Subject:RE: Disabling C++ Namespace
Well, if you look in the headers, the documentation is incorrect (just
submitted as bug 25727). Alberto suggested that you use:
XERCES_CPP_NAMESPACE_BEGIN
class Inpu
qualify DOM_Node to the xerces namespace.
Thanks,
Stephanie Milchak
Software Engineer
WebSphere Business Integration
Research Triangle Park, NC
"Adam Heinz" <[EMAIL PROTECTED]>
12/23/2003 09:49 AM
Please respond to xerces-c-dev
To: <[EMAIL PROTECTED]&
Exstream Software
-Original Message-From:
Stephanie L Milchak [mailto:[EMAIL PROTECTED]Sent: Tuesday,
December 23, 2003 9:33 AMTo:
[EMAIL PROTECTED]Subject: RE: Disabling C++
Namespace
Using xercesc:: is correct
according to the apache documentation: http://xml.apache.org/xerces
MAIL PROTECTED]>
12/23/2003 09:23 AM
Please respond to xerces-c-dev
To: <[EMAIL PROTECTED]>
cc:
Subject: RE: Disabling C++ Namespace
You need to use XERCES_CPP_NAMESPACE:: instead of xercesc::, since that is just wrong (see util/Xer
You need to use XERCES_CPP_NAMESPACE:: instead of xercesc::, since that
is just wrong (see util/XercesVersion.hpp). The namespaces are named
according to the release version; the namespace macro expands to something like
xercesc_2_3.
Adam Heinz Development Consultant Exstream Software
t; <[EMAIL PROTECTED]>
12/23/2003 08:53 AM
Please respond to xerces-c-dev
To: <[EMAIL PROTECTED]>
cc:
Subject: RE: Disabling C++ Namespace
All the DOM_* classes have been moved into dom/deprecated, so I would suggest migrating
To:
<[EMAIL PROTECTED]> cc:
Subject: RE: Disabling C++
Namespace Your prototype is not in the Xerces
namespace, so the linker is looking for function(obj*) when it needs
function(Xerces::obj*). XERCES_CPP_NAMESPACE use doesn't m
search Triangle Park, NC
"Adam Heinz" <[EMAIL PROTECTED]>
12/22/2003 12:30 PM
Please respond to xerces-c-dev
To: <[EMAIL PROTECTED]>
cc:
Subject: RE: Disabling C++ Namespace
Your prototype is not in the Xerces name
At 09.25 22/12/2003 -0700, Stephanie L Milchak wrote:
Okay, let's say that I have this in my header file:
[...]
XERCES_CPP_NAMESPACE_USE
// I now have to qualify this class since it's defined in another xerces
file.
class xercesc::InputSource;
If you want to specify that InputSource is in the Xe
ere Business
IntegrationResearch Triangle Park, NC
"Adam Heinz"
<[EMAIL PROTECTED]>
12/22/2003 12:01 PM Please respond to xerces-c-dev
To:
<[EMAIL PROTECTED]> cc:
To: <[EMAIL PROTECTED]>
cc:
Subject: RE: Disabling C++ Namespace
If you're already including Xerces headers in your header, why not just include the needed headers rather than use a class prototype?
Adam Heinz
Development Consultant
Exstream Software
If you're already including Xerces headers in your header, why not just
include the needed headers rather than use a class
prototype?
Adam Heinz Development Consultant Exstream Software
rs to have to be aware that xerces was upgraded.
Thanks,
Stephanie Milchak
Software Engineer
WebSphere Business Integration
Research Triangle Park, NC
"Adam Heinz" <[EMAIL PROTECTED]>
12/22/2003 11:05 AM
Please respond to xerces-c-dev
To: <[EMAIL PROTEC
Could you give me a code sample from one of your
interface header files?
Adam Heinz Development Consultant Exstream Software
-Original Message-From: Stephanie L Milchak
[mailto:[EMAIL PROTECTED]Sent: Monday, December 22, 2003 10:49
AMTo: [EMAIL PROTECTED]Subject: RE: Disablin
919.543.4069
Research Triangle Park, NC
"Adam Heinz" <[EMAIL PROTECTED]>
12/22/2003 10:46 AM
Please respond to xerces-c-dev
To: <[EMAIL PROTECTED]>
cc:
Subject: RE: Disabling C++ Namespace
If you foll
If you follow your #includes with XERCES_CPP_NAMESPACE_USE, you don't
have to qualify all of your variables. For example:
#include #include
#include
#include
XERCES_CPP_NAMESPACE_USE
Adam Heinz Development Consultant Exstream
Software
22 matches
Mail list logo
