[
https://issues.apache.org/jira/browse/XERCESC-2206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17133718#comment-17133718
]
Scott Cantor commented on XERCESC-2206:
---------------------------------------
I think that would be great (for me), I just didn't want to speak for somebody
doing the work as to whether it's worth doing it but not releasing the result.
I'm well aware of the nightmare of those 16-bit APIs, believe me. It is
*mostly* possible to create a wide-string specialization for XMLCh, though it's
not 100% C++ compliant due to locales. Certainly will be hugely welcome to have
it for real once I can move to it.
> Use char16_t and unicode literals to replace various XMLCh types
> ----------------------------------------------------------------
>
> Key: XERCESC-2206
> URL: https://issues.apache.org/jira/browse/XERCESC-2206
> Project: Xerces-C++
> Issue Type: Bug
> Components: Miscellaneous
> Affects Versions: 3.3.0
> Reporter: Roger Leigh
> Assignee: Roger Leigh
> Priority: Major
> Fix For: 3.3.0
>
>
> Currently, XMLCh can be a variety of 16-bit types depending upon the
> platform, from wchar_t, uint16_t, unsigned short, to char16_t.
> To reduce the platform-specific variability, fix XMLCh to char16_t, and also
> permit the use of u"" unicode string literals in the codebase. This will
> allow replacement of Unicode constants with direct use of literals.
> This will additionally reduce the size of the test matrix with only one
> character variant to test.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org
For additional commands, e-mail: c-dev-h...@xerces.apache.org
