2 ms·
...which isn't the end of the world, since ICU comes with a bunch of stuff that makes life bearable when developing international software, like language-aware
by timr 17y ago
...which isn't the end of the world, since ICU comes with a bunch of stuff that makes life bearable when developing international software, like language-aware collation and regular expressions. If you're going to be developing real i18n software in C++, you're always going to be using ICU or something like it. There's no reason to bother with std::locale.
In fact, I'm guessing that Apple never got around to fixing this because they probably don't use std::locale for real i18n work internally.
(update: the ICU homepage says that Mac OSX uses ICU internally -- http://site.icu-project.org/ http://site.icu-project.org/)
- fauigerzigerk 17y agoSeems my post was very unclear and I apologize for that. What I meant to say is: Try to avoid POSIX locales at all cost. Use ICU!