Path: ...!news.mixmin.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Lawrence D'Oliveiro <ldo@nz.invalid>
Newsgroups: comp.lang.fortran
Subject: Re: Upcoming gfortran 15 will contain unsigned numbers
Date: Tue, 15 Oct 2024 22:35:36 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 9
Message-ID: <vemqnn$1sd2k$4@dont-email.me>
References: <veg58f$kb8e$1@dont-email.me> <vemj62$1qt5b$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Wed, 16 Oct 2024 00:35:36 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="8e07f34fd508234a93a0d7f7570ee3ce";
	logging-data="1979476"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX188o+FGSK1uYD/DGSVP3JVd"
User-Agent: Pan/0.160 (Toresk; )
Cancel-Lock: sha1:cvhIRy/otZtzrCAvOb/XdCnmgQo=
Bytes: 1297

On Tue, 15 Oct 2024 15:26:42 -0500, Lynn McGuire wrote:

> Any plans to support UTF16 or UTF8 in gfortran ?

No UTF-16, please!

That was just a horrible backward-compatibility hack for the sake of those 
platforms (*cough* Java, Windows NT *cough*) that embraced Unicode as 
their native encoding just a little too soon.