i think that the 486 issue is a non issue for Windows.
we also need full Borland support of Xerces for a cross platform product. i
would like to see an official set of project files become part of the
distribution.
Herb....
william.l.hopper@
us.abb.com To: [EMAIL PROTECTED]
cc:
03/28/01 02:21 AM Subject: Supporting C++Builder 4 and 5
issues
Please respond to
xerces-c-dev
I am trying to pull together updates for the BCB4 files in CVS and create a
similar BCB5 tree for C++Builder 5 and I would like the community's input
on a
few issues...
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?
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"?
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?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
