[
https://issues.apache.org/jira/browse/XERCESC-2101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16049226#comment-16049226
]
Roger Leigh commented on XERCESC-2101:
--------------------------------------
- [Unix build
results|https://travis-ci.org/rleigh-codelibre/xerces-c/builds/242814234]
- [Windows build
results|https://ci.appveyor.com/project/rleigh-codelibre/xerces-c/build/1.0.92]
All builds have passed using a mixture of old and new compilers using the
previous defaults and char16_t, respectively.
Overall, this is a fairly trivial change to a typedef with the changes to the
supporting build infrastructure to detect and enable it. It enables the use of
{{u"Unicode string"}}, which offers a significant usability improvement for end
users of the library API, as well as a potential minor performance improvement
by removing the need to transcode from 8-bit strings. No need to transcode to
wide strings for every element and attribute name, it's all handled at compile
time by the compiler.
> Add support for XERCES_XMLCH_T = char16_t
> -----------------------------------------
>
> Key: XERCESC-2101
> URL: https://issues.apache.org/jira/browse/XERCESC-2101
> Project: Xerces-C++
> Issue Type: Improvement
> Reporter: Vemund Handeland
> Priority: Minor
> Attachments:
> 0001-Add-Windows-support-for-XERCES_XMLCH_T-char16_t.patch,
> 0002-cmake-Check-for-char16_t.patch, 0003-autoconf-Check-for-char16_t.patch,
> char16_t.diff
>
>
> Attached diff contains the required changes for msvc. The diff is from my
> local git repo created from the 3.1.4 release.
> Added new macro XERCES_USE_CHAR16_T.
> User can enable the support by define this macro both when building the
> library and her own application.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org
For additional commands, e-mail: c-dev-h...@xerces.apache.org
