24 May
2010
24 May
'10
8:08 p.m.
Artyom wrote:
No, it will not as Micorsoft would not agree. This is why C++0x gives us char16_t and char32_t.
Microsoft's disagreement can not make something more conforming than it actually is, IMO :) But I'm just nitpicking, and this point is not that relevant in practice, so let's put it off.
AFAIK actually wchar_t defined by C and it allowed even sizeof(wchar_t)==1
Sure it is allowed, but only as long as 1 byte is enough to encode all characters of supported locales: C99, 7.17 "wchar_t which is an integer type whose range of values can represent distinct codes for all members of the largest extended character set specified among the supported locales" Thanks, Gevorg