From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00
	autolearn=unavailable autolearn_force=no version=3.4.4
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!news.eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!news.unit0.net!takemy.news.telefonica.de!telefonica.de!newsfeed.arcor.de!newsspool1.arcor-online.net!news.arcor.de.POSTED!not-for-mail
Date: Mon, 18 Nov 2013 14:05:45 +0100
From: "G.B." <rm-dash-bau-haus@dash.futureapps.de>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7;
 rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
Newsgroups: comp.lang.ada
Subject: Re: strange behaviour of utf-8 files
References: <73e0853b-454a-467f-9dc7-84ca5b9c29b2@googlegroups.com>
 <1ghx537y5gbfq.17oazom68d4n6.dlg@40tude.net>
 <9d00683c-949c-4e88-a161-ebd78b350d39@googlegroups.com>
 <1w23uq33ul2i8$.wzjpp3evot36.dlg@40tude.net>
 <5288c584$0$6639$9b4e6d93@newsspool2.arcor-online.net>
 <k4o32tkp8lu4.1fuul1c08z90n$.dlg@40tude.net>
 <52891372$0$6636$9b4e6d93@newsspool2.arcor-online.net>
 <10ec0vuld83fy.1t7bduzwsrfe.dlg@40tude.net>
 <5289d34e$0$6637$9b4e6d93@newsspool2.arcor-online.net>
 <th9m0f0l1bgl$.1cx73kba9l2ks.dlg@40tude.net>
In-Reply-To: <th9m0f0l1bgl$.1cx73kba9l2ks.dlg@40tude.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Message-ID: <528a10a9$0$6564$9b4e6d93@newsspool4.arcor-online.net>
Organization: Arcor
NNTP-Posting-Date: 18 Nov 2013 14:05:45 CET
NNTP-Posting-Host: 30fe5f32.newsspool4.arcor-online.net
X-Trace: 
 DXC=8KTnZ55i_PLC4i^e1BZ=_H4IUK<Cl32<A4Fo<]lROoRA8kF<OcfhCOKi^]>]GbD7bOnc\616M64>JLh>_cHTX3jM;;XM6dnh;NB
X-Complaints-To: usenet-abuse@arcor.de
Xref: news.eternal-september.org comp.lang.ada:17718
Date: 2013-11-18T14:05:45+01:00
List-Id: <comp.lang.ada>

On 18.11.13 11:24, Dmitry A. Kazakov wrote:

>> In order to be able to integrate software (libraries, sources) that
>> use international characters.
>
> Why cannot it be integrated without these bugs?

Character literals are not bugs. Ada lacks means of
expressing programmer's intent here, that much is true.
Encoding could be specified by an aspect, just like 'Size.
The language is buggy here, when matched against ubiquitous
real world programming situations.

> It is like saying that Ada programs must use System.Address in order to be
> integrated with machine code.

Yes. Machine code without machine addresses would be magic.

> We don't want such kind of integration.

We can't say: we don't want character literals, or string literals.

People use international character literals. Compiling programs
that use international characters as per the Ada LRM
should work without much ado and without all the FUD-induced
avoidance, and without compiler difficulties.

To suggest only using ASCII is rather like suggesting
to not use FPT, arguing that using FPT leads to results that
can differ when switching from Intel to ARM or to PowerPC.