On Friday, 10 January 2014 at 14:02:13 UTC, Regan Heath wrote:
IIRC wchar_t is actually UCS-2 (called Multibyte by devenv and various functions) which is a sub-set of UTF-16. So, calling a windows W function with wchar[] could also break.. just in far fewer cases than char[] with A functions.
IIRC Microsoft did change from UCS-2 to UTF-16 with Windows 2000 (maybe XP).