2 ms·
Yes, the article title is wildly unfair. But an article titled "the g++ std::locale implementation under Mac OSX is broken" isn't nearly as interesting as clai
by timr 17y ago
Yes, the article title is wildly unfair. But an article titled "the g++ std::locale implementation under Mac OSX is broken" isn't nearly as interesting as claiming that C++ might not be able to support Unicode.
I mean, really...C++ can work with individual bits; it can obviously support Unicode strings. The problem here is one of making the compiler aware of the details of the platform on which it's being used. The blame here appears to lie on Apple:
http://lists.apple.com/archives/darwin-dev/2008/Mar/msg00015.html http://lists.apple.com/archives/darwin-dev/2008/Mar/msg00015...
http://lists.apple.com/archives/unix-porting/2006/Dec/msg00007.html http://lists.apple.com/archives/unix-porting/2006/Dec/msg000...
- gchpaco 17y agoYes, that's right, for those just tuning in, this has been broken since at least 2006. Probably earlier. I'm just speechless.
- deleted 17y ago[deleted]