TCHAR just resolves to wchar_t when you define _UNICODE and build. I was specifically talking about wchar_t so I didn't bother. In a real program, its only use is porting programs to non-Unicode...
Type: Posts; User: whiteflags
TCHAR just resolves to wchar_t when you define _UNICODE and build. I was specifically talking about wchar_t so I didn't bother. In a real program, its only use is porting programs to non-Unicode...
A couple of things:
First, not all unicode characters are just one character. To be specific, UNICODE unambiguously refers to glyphs as code points, and certain encodings will require different...
In C99 you can encode the data as a universal character name.
wchar_t beer_mug[] = L"\U0001f37a";
That creates a string which will contain the beer glyph, not counting the terminating 0.