You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@xerces.apache.org by Milan Tomic <mi...@setcce.org> on 2004/04/06 10:28:59 UTC

Xerces 2.5 & PlatformSDK & VC++ 6

	I've just installed MS Windows PlatformSDK (August 2002) and
pointed Visual C++ 6 to use those directories. The problem is that
compiler now reports that DOMDocument is ambigious (also exists in
MSXML) and I have to add "xercesc_2_5::" in a front of every DOMDocument
declaration in my app. I have XERCES_CPP_NAMESPACE_USE macro defined.
How can I solve this?

Thank you.

Re: Xerces 2.5 & PlatformSDK & VC++ 6

Posted by Vitaly Prapirny <ma...@mebius.net>.
Hi,

Milan Tomic wrote:
> 
>         I've just installed MS Windows PlatformSDK (August 2002) and 
> pointed Visual C++ 6 to use those directories. The problem is that 
> compiler now reports that DOMDocument is ambigious (also exists in 
> MSXML) and I have to add "xercesc_2_5::" in a front of every DOMDocument 
> declaration in my app. I have XERCES_CPP_NAMESPACE_USE macro defined. 
> How can I solve this?
If you don't explicitly use MSXML headers in your project,
you can try to define WIN32_LEAN_AND_MEAN.

Good luck !
	Vitaly


---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org


Re: Xerces 2.5 & PlatformSDK & VC++ 6

Posted by Alberto Massari <am...@progress.com>.
At 10.28 06/04/2004 +0200, Milan Tomic wrote:

>         I've just installed MS Windows PlatformSDK (August 2002) and 
> pointed Visual C++ 6 to use those directories. The problem is that 
> compiler now reports that DOMDocument is ambigious (also exists in MSXML) 
> and I have to add "xercesc_2_5::" in a front of every DOMDocument 
> declaration in my app. I have XERCES_CPP_NAMESPACE_USE macro defined. How 
> can I solve this?

Unfortunately, you have to prepend either xercesc_2_5:: or 
XERCES_CPP_NAMESPACE_QUALIFIER before each occurrence of DOMDocument type. 
That's because the Platform SDK declares a global type DOMDocument and the 
compiler doesn't know which one to pick (the one in the global namespace or 
the one in the default namespace set by XERCES_CPP_NAMESPACE_USE)

Alberto 



---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org


Re: Xerces 2.5 & PlatformSDK & VC++ 6

Posted by "Jeroen N. Witmond" <jn...@xs4all.nl>.
>
> 	I've just installed MS Windows PlatformSDK (August 2002) and
> pointed Visual C++ 6 to use those directories. The problem is that
> compiler now reports that DOMDocument is ambigious (also exists in
> MSXML) and I have to add "xercesc_2_5::" in a front of every DOMDocument
> declaration in my app. I have XERCES_CPP_NAMESPACE_USE macro defined.
> How can I solve this?

I don't know how you can tell Visual C++ 6 to prefer the XercesC
DOMDocument above the MSXML one. But if it turns out that you have to use
a qualifier for DOMDocument, I'd advice you not to use
"xercesc_2_5::DOMDocument", as this binds you to the current version of
XercesC. Use either "XERCES_CPP_NAMESPACE_QUALIFIER DOMDocument" (without
colons), or "xercesc::DOMDocument" (with colons). The former has the
advantage of also compiling on compilers without support for namespaces,
and hence is more portable.

Regards,

Jeroen.

>
> Thank you.
>


---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org