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

On 8/27/2024 9:15 AM, Arne Vajhøj wrote:

On 8/27/2024 8:54 AM, Simon Clubley wrote:

On 2024-08-25, Dave Froble <davef@tsoft-inc.com> wrote:
If I had said "that there was no need for UTF-8 because we will just have
people use British English from now on", then how do you think that would
have come across ?
>
Yet you have just done the same David. You have just said that if it is
not used in US English then it is not important and the rest of the world
should just learn to restrict itself to US ASCII characters in their use
of filenames, etc.

 There is a difference between what end users see and the underlying
infrastructure that enables them to see it.
 The end users should be able to see all sort of languages.
 But end users are not doing $ SET DEF and $ TYPE anymore.
 They should not care about directory and file names.
 Hoff has stated a few times that VMS actually has implemented
UTF-8 support in filenames. Probably more than 20 years ago.
 Anyone been using tat feature in the last 20 years?
 I don't think so. Which hints about the value.

I never create filenames with æøå. I never deliberately
create filenames with spaces.
I try to stay out of trouble. :-)

VMS is in dire need for something that makes conversions
between DECMCS/ISO-8859-1 and UTF-8 easy for the traditional
native languages.
 But UTF-8 support in file names, usernames, logicals, program
identifiers is mostly a gimmick.

Java has supported unicode in identifier since forever.
public class UniMess {
public static void main(String[] args) {
int abc = 123;
int æøå = 456;
int \u1234\u4321 = 789;
System.out.printf("%d %d %d\n", abc, æøå, \u1234\u4321);
}
}
is valid code.
I never use that feature either. ASCII is good enough for my
identifiers.
I use ÆØÅ in String literals sometimes.
I use ÆØÅ in comments sometimes (like in my name!).
Arne