That assumes wchar_t holds UTF-16 (as XMLCh does). It might not. See http://www.losingfight.com/blog/2006/07/28/wchar_t-unsafe-at-any-size/ for a wchar_t story that would be amusing if it were fiction.
-----Original Message----- From: Keith Mendoza [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 19, 2007 11:48 AM To: [email protected] Subject: Re: WCHAR to XmlCh Actually the C99 standard defines a wchar_t type which can be used for wide characters. You probably will need to typecast your wchar_t* to XMLCh*. Keith On 9/19/07, Nawal Kishore Gupta <[EMAIL PROTECTED]> wrote: > > I think linux also has wchar with #include <wchar.h> > > > Alberto Massari wrote: > > > At 19.23 19/09/2007 +0530, Nawal Kishore Gupta wrote: > > > >> I am passing const WCHAR only > > > > > > WCHAR is a Windows type; how do you define it on Linux? > > > > Alberto > > > > > >> Regards, > >> > >> Nawal > >> > >> Wentao Deng wrote: > >> > >>> How do you call XercesDOMParser::parse? > >>> The parameter should be const XXX *, > >>> not const XXX *&. > >>> > >>> Regards, > >>> Wentao > >>> > >>> > >>> ----- Original Message ----- From: "Nawal Kishore Gupta" > >>> <[EMAIL PROTECTED]> > >>> To: <[email protected]> > >>> Sent: Wednesday, September 19, 2007 4:35 AM > >>> Subject: WCHAR to XmlCh > >>> > >>> > >>>> Dear All, > >>>> > >>>> What is the best way to covert WCHAR to XMLCh in Linux /Unix build. > >>>> > >>>> I am getting the following error: > >>>> error: no matching function for call to > >>>> `xercesc_2_7::XercesDOMParser::parse(const WCHAR*&)' > >>>> > >>>> but same thing works fine in Windows unicode and non unicode build. > >>>> > >>>> > >>>> Regards, > >>>> > >>>> Nawal > >>> > >
