Developers only: wchar_t EPIC FAIL

Please skip this, unless you have a clue what wchar_t means.

"For most characters they were only wasting one byte (as opposed
to three bytes in UTF-32), but could still assume most characters
where just 16-bits (as opposed to UTF-8 which escaped anything
not ASCII). Life was good."

"Meanwhile, Unix vendors had decided that wasting one byte was
insufficient, and that wasting three bytes per character was
definitely the way to go."



Article is here: http://www.losingfight.com/blog/2006/07/28/wchar_t-unsafe-at-any-size/

Maybe it's time to stop smoking pot while setting up new standards