On 10/8/15 2:52 AM, Artyom Beilis wrote:
There is also small but significant difference, my UTF-8 <-> UTF-16/32 facets are template based and header only implementation.
The current one is also header only and template based
Regarding the test - I have my own that the old facet obviously wouldn't pass.
That is not my question. Will your new version pass the current test?
You'll have to give us some warning - maybe skip a release or maybe just use header re-direction.
It can't be simple redirection as it works in little bit different way.
Hmmm - very suspicious. I expect to just be able to include a header and create an instance of the codecvt type and start using it. If I can't do this, we might have a problem.
I think just keeping old utf8 facet until all library maintainers replace it - and it would likely take more than one release :-)
Artyom Beilis
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost