Thanks for the clarification Roger!
Kind regards,
Mark
-Original Message-
From: rle...@codelibre.net [mailto:rle...@codelibre.net]
Sent: 24 January 2018 11:40
To: c-users@xerces.apache.org
Subject: Re: How to build with XMLCh = wchar_t on Windows platform.
On 2018-01-24 09:30, Mark
On 2018-01-24 09:30, Mark Douglas wrote:
As a side note, we have a lot of 32-bit C++ code that needs
conversion, but this is going to take time (other 3rd party libraries
involved). If you were to drop 32-bit support, this could become an
issue for us in the short-term. I'm not sure if there are
Hi Roger,
Thanks again for your feedback. Most useful.
In this particular case, our application is only reading/writing our own
internal configuration files, so no user input as such. So I should be good not
having to transcode. All the characters in our files are UTF-8 only.
Thanks for
Hi Roger,
I think Microsoft have had wchar_t as a type way before char16_t was introduced
(as far back as I can remember, which is getting shorter as I get older :)). At
the time, Microsoft were well known for doing things the 'Microsoft way' and
not following standards very well. So maybe
On 2018-01-23 14:12, Mark Douglas wrote:
Hi Roger,
Thank you very much for this valuable feedback! As I'm new to CMake, I
didn't find the options of disabling char16_t (at least I wasn't
looking for the right thing to start with!).
I think the default policy of using char16_t, if it is
Hi Roger,
Thank you very much for this valuable feedback! As I'm new to CMake, I didn't
find the options of disabling char16_t (at least I wasn't looking for the right
thing to start with!).
I think the default policy of using char16_t, if it is available, is a good
choice - cross platform
On 2018-01-23 12:03, Mark Douglas wrote:
Hi,
This is my first mail to this group, so hopefully I've come to the
correct place!
Yes, it is!
I'm currently attempting to build and use Xerces C++ 3.2.0 in my
application, but I'm having an issue where XMLCh is defined as
char16_t (not compatible
