Sorry I didn't see this post before. The answers are:
> 1. Am I correct that Visual C++ 6 does not declare the C++ standard type
> "wchar_t" as intrinsic like C++Builder does, which allows VC6 to think an
> "XMLCh" is the same, while C++Builder thinks they are different?
>
You'll need to make XMLCh unsigned short, not the intrinsic wchar_t. This is
what is now assumed by the parser, i.e. its always UTF-16.
> 2. Given the typedef problem above, is anyone building Xerces under
C++Builder
> ^without^ changing the "XMLCh" typedef in util\Compilers\BorlandCDefs.hpp
back
> to being "wchar_t"?
>
Unless wchar_t is UTF-16 on your compiler, you shouldn't use wchar_t.
> 3. MSDN, etc. indicates that the InterlockedCompareExchange API is not
> supported on Windows 95, only on later versions. Secondly, in the
> "compareAndSwap" method in util\Platforms\Win32\Win32PlatformUtils.cpp,
the
> inline assembler section ifdef'ed for VC++ uses instructions that, I
think, are
> only valid for 80486 and later processors. Is supporting Windows 95 the
reason
> we are not using the InterlockedCompareExchange API method? Additionally,
does
> Xerces have a stated list of supported processors?
>
I think that we've dropped Win95 now, right? If the InterlockedXXX() methods
are available on Win98 and we aren't supported Win95 anymore, then we should
toss the assembly I think.
--------------------------
Dean Roddey
The CIDLib C++ Frameworks
Charmed Quark Software
[EMAIL PROTECTED]
http://www.charmedquark.com
"Why put off until tomorrow what you can
put off until the day after tomorrow?"
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
