On 7/16/20, 9:15 AM, "Francesco Pretto" <[email protected]> wrote:
> Are you really sure you want to pursue this direction? Well, I think there's very little chance, bordering on zero, that if there isn't the will to actually convert the internals to UTF-8 *now*, there isn't going to be. Even so, all it takes a 5.0 to move to UTF-8 if there's suddenly the will to do that. I don't see any doors closing forever. Heck, you can define XMLCh yourself and keep using it as a synonym for any touchpoints with Xerces if you really wanted to. If we don't commit to char16_t, then it's impossible to write non-Windows code that can make the assumption that it can use string literals and char16_t and count on that working, so that effectively makes a change pointless (obviously for custom builds, one can make the assumption now since it's possible to configure it to use char16_t already). However, since I'm not the one doing any of the work, I'll let people speak for themselves. -- Scott
