From: "G.B." <bauhaus@futureapps.invalid>
Subject: Re: UTF-8 Output and "-gnatW8"
Date: Tue, 29 Mar 2016 10:39:07 +0200
Date: 2016-03-29T10:39:07+02:00 [thread overview]
Message-ID: <nddep9$4uv$1@dont-email.me> (raw)
In-Reply-To: <6406289c-06a8-46d1-a633-8a1c8a22f79b@googlegroups.com>
On 29.03.16 00:48, Michael Rohan wrote:
> It does, however, feel like there is something missing where it's "difficult" to have a Wide_String literal without having to have extra meta data for compiler (-gnatW8) or having a relatively cumbersome concatenation of Wide_Character's based on code points. BTW, the performance of GNAT for such a concatenated string is pretty dismal.
That source character set issue is probably resolved in no time
once NATO, inasmuch as it is a software organization, will require
that compilers automatically detect UTF-16.
next prev parent reply other threads:[~2016-03-29 8:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-24 17:23 UTF-8 Output and "-gnatW8" Michael Rohan
2016-03-24 22:09 ` Randy Brukardt
2016-03-24 22:34 ` Michael Rohan
2016-03-25 19:15 ` Randy Brukardt
2016-03-25 5:54 ` rieachus
2016-03-25 19:18 ` Randy Brukardt
2016-03-28 22:48 ` Michael Rohan
2016-03-29 7:44 ` Dmitry A. Kazakov
2016-03-29 8:39 ` G.B. [this message]
2016-03-29 22:35 ` Randy Brukardt
2016-04-04 10:52 ` G.B.
2016-04-05 0:39 ` Randy Brukardt
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox