Alberto, thanks.
Jesse, could you please be a little more precise as to why the _T() macro
strings will be broken? As per my understanding, it is always better to use
_T("my string"). If _UNICODE is defined, then this will be taken as L"my
string" at compile time. If _UNICODE is not defined (ie for ANSI or MBCS) -
it will be treated as the plain literal string "my string".
My understanding (from the API documentation) is that most XERCES routines
have an unicode-compatible overloaded method. For eg, in case of
XMLString::catString() method, the available signatures are:
static void XMLString::catString (char* const target, const char* source)
static void XMLString::catString (XMLCh* const target, const XMLCh* source)
Now if I declare one of the parameters (say the source string) as
_T("...."), then for _UNICODE it will be a L"....", which will be treated as
"const XMLCh*". This will invoke the second function. If _UNICODE is not
defined, then it will map to "const char*" and the first one (of the two
overloaded functions above) will be invoked.
Please let me know if I am wrong in my assumption.
Thanks & Regards,
Deba
On 10/4/06, Jesse Pelton <[EMAIL PROTECTED]> wrote:
I'd recommend avoiding the _T() macro when calling Xerces routines
because, as Alberto points out, whether it generates the right kind of
string depends on the _UNICODE macro. If you ever change how you
compile, everything that uses _T() will be broken. You can future-proof
your code by using L"my string" where XMLCh* is required, and just "my
string" where char* is required.
-----Original Message-----
From: Alberto Massari [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 04, 2006 7:41 AM
To: [email protected]
Subject: Re: Query on Unicode Support for XERCES-C
Hi Deba,
At 12.31 04/10/2006 +0530, Debashis Tripathy wrote:
>Hi,
>
>I need to implement XERCES-C on a MFC project. I need to know the
extent of
>Unicode Support provided by XERECES. My question is, whenever I need to
pass
>a literal string (for eg: "my string") to one of the XRECES library
methods,
>can I pass a unicode string (eg _T("my string") or L"my string")
instead?
On Windows platforms, wherever you see XMLCh* you can use L"my
string" or _T("my string") if you have defined the _UNICODE macro.
>Also, wherever XERCES expects a parameter of type "const char*", is it
OK to
>pass a "const _TCHAR*" or "LPCTSTR" instead?
In this case _T("my string")/LPCTSTR/TCHAR* can only be used if the
_UNICODE macro is NOT defined.
Hope this helps,
Alberto
--
Debashis Tripathy
+91 9937026725 (Mobile)
+91 674 2396071 (Home)
+91 674 2320032 * 42371 (Work)
-----------------------------------------------------------------
Anything written on paper can affect history,
not life. Life is a different history.
