Re: C and C++, promotion, stabilization, migrationFor embedded

On 8/24/2024 10:12 PM, Stephen Hoffman wrote:

On 2024-08-23 23:34:18 +0000, Arne Vajhøj said:

And support for the latter fall in 3 groups:
* JVM languages (Java, Groovy etc.) and I believe Python - does support unicode and can read/write using any encoding including UTF-8
* C, C++, PHP - developer keeps track of what encoding a byte sequence is in but possible to explicit convert encodings
   (C/C++ has wchar_t but it is neither much used nor UTF-8 friendly AFAIK)

 Quoth the standard: "The width of wchar_t is compiler-specific and can be as small as 8 bits. Consequently, programs that need to be portable across any C or C++ compiler should not use wchar_t for storing Unicode text."

As usual the C standard is very vague in its definitions.
wchar_t may not be generally portable. But it is 16 or 32
bits on a few common platforms: Windows, Linux, various Unix,
VMS etc.. Most irritating is that it is 16 bit on Windows and
32 bit on the rest.
To get more well defined types then one could use char16_t/char32_t,
but I think library support sucks for those.
Arne