[
https://issues.apache.org/jira/browse/XERCESC-2206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17130670#comment-17130670
]
Roger Leigh commented on XERCESC-2206:
--------------------------------------
None of this is intended to cause any *API* break. But if there's any question
of needing it to be parallel installable, we could make this preparatory work
for a version 4.0 so that distributors can have xerces-c3 and xerces-c4
co-installable.
For the few bugfixes and security updates which need applying, it won't be too
much work to apply them to both branches.
My intent here is to make Xerces-C++ viable for the longer term by making it
transparently usable with contemporary compilers and standard libraries from
the last decade, rather than have it stuck in the pre-Standard mid-90s-era
which is mutually incompatible with the rest of the C++ world. I am not
suggesting using C++20 or C++17, or anything remotely bleeding edge. We would
be using a strictly limited subset of features, which currently would be:
char16_t, thread and eventually optional use of streams and the standard
exception types, and possibly ustring.
None of those changes are intended to cause any breakage for existing C++ code
using Xerces-C++. The char16_t change should be entirely transparent since
it's already in 3.2.x if the compiler supports it, and is tested against most
open source Xerces-C++ users. What it will enable is the guaranteed ability to
utilise unicode literals and string literals in code calling Xerces which will
make applications simpler and more readable.
> 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: [email protected]
For additional commands, e-mail: [email protected]
