3 ms·
This is silly... not only is the article inaccurate but the problem described is trivial to solve. As long as you know what encoding wchar_t uses and what encod
by jheriko 17y ago
This is silly... not only is the article inaccurate but the problem described is trivial to solve. As long as you know what encoding wchar_t uses and what encoding your data is stored in this is not a big problem, use one format internally and convert your data on the way in as appropriate. Trust me, I solved it with no prior knowledge, no formal education in less than a day, as a distraction during my day job... I did not have to re-write the entire library from scratch.
- BudVVeezer 17y agoInaccurate in what way? It may be trivial to solve, but it's certainly not an issue anyone should have to solve, if the C++ standards committee would have dictated size and encoding information along with the datatype.
- jheriko 17y agothe MS compiler uses wchar_t as UCS2, not UTF-16 for example all of the C++ types have platform dependence - expecting a specific number of bits or encoding for wchar_t would make an exception of it, and one that would be impossible to implement in practice.