Hi William,
I didn't see your earlier posting, but anyway, here's my $0.02.
>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?
It certainly seems so.
>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"?
I've tried both with and without redefining the typedef. If you don't, you
end
up with loads of explicit casts in Win32PlatformUtils.cpp. I've attached a
version
with these casts. They're all documented like this: //<BCB cast to 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?
Don't know; I only have W2K here, but I can have a look at home (I've got a
W98
machine there), if you want me to.
Hope this helps,
Evert
Win32PlatformUtils.cpp
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
