Sujet : Re: Upcoming gfortran 15 will contain unsigned numbers
De : ldo (at) *nospam* nz.invalid (Lawrence D'Oliveiro)
Groupes : comp.lang.fortranDate : 23. Nov 2024, 03:08:19
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <vhrdej$1dqca$4@dont-email.me>
References : 1 2 3 4 5 6
User-Agent : Pan/0.161 (Chasiv Yar; )
On Fri, 22 Nov 2024 19:40:19 -0600, Lynn McGuire wrote:
Come over here to Windows. UTF-16 is the name of the game. It is a
total pain.
Microsoft (and Sun, with Java) adopted Unicode at precisely the wrong
time, back when everybody believed the Unicode folks who said that it
would remain a fixed-length 16-bit code.
Microsoft is rumored to be working on a UTF-8 API for Win32 / Win64. I
will believe it when I see it.
Linux simply ignored the issue. Filespecs passed to the kernel are split
at ASCII “/” characters and terminated by NUL. And those are the only byte
values with special interpretations; file/directory names are free to
contain anything else. As a result, it works seamlessly with UTF-8.