Sujet : Re: C and C++, promotion, stabilization, migrationFor embedded
De : arne (at) *nospam* vajhoej.dk (Arne Vajhøj)
Groupes : comp.os.vmsDate : 24. Aug 2024, 00:34:18
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <vab69p$1356i$1@dont-email.me>
References : 1 2 3 4 5
User-Agent : Mozilla Thunderbird
On 8/23/2024 11:32 AM, Stephen Hoffman wrote:
OpenVMS has ~no concept of languages, either. Yeah, the C abd C++ I18N giblets, Java and its own little world, maybe using the existing and older ICU or maybe you ported a newer ICU, and the deprecated Terminal Fallback Facility (TFF) and National (Replacement) Character Set (NCS) giblets, sure. All of which make things more interesting for apps that want or need to deal with the UTF-8 and post-ASCII world.
Regarding UTF-8 support, then my take is that:
UTF-8 in file names, in usernames, in logicals, in identifiers and in
programs/scripts: not really needed.
UTF-8 in file content and in databases: very much needed.
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)
* the traditional native languages - very little support except what
can be done by calling C functions
Arne