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=0.4 required=5.0 tests=BAYES_00,DATE_IN_PAST_24_48,
	FORGED_GMAIL_RCVD,FREEMAIL_FROM autolearn=no autolearn_force=no
	version=3.4.4
X-Google-Thread: a07f3367d7,d5b211b0c1ffcf3e
X-Google-Attributes: gida07f3367d7,public,usenet
X-Google-NewGroupId: yes
X-Google-Language: ENGLISH,ASCII-7-bit
Received: by 10.204.141.4 with SMTP id k4mr392981bku.6.1339692242668;
        Thu, 14 Jun 2012 09:44:02 -0700 (PDT)
Path: 
 e27ni47916bkw.0!nntp.google.com!news1.google.com!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
From: i3text@gmail.com
Newsgroups: comp.lang.ada
Subject: Re: Practicalities of Ada for app development
Date: Tue, 12 Jun 2012 13:10:27 -0700 (PDT)
Organization: http://groups.google.com
Message-ID: <3248f4fa-adc5-42e5-97f5-2f157192d0f5@googlegroups.com>
References: 
 <79c5c9f7-4b72-4990-8961-b3e2db4db79b@qz1g2000pbc.googlegroups.com>
 <a09a80a241191ef62e72aa46e2c449bc@dizum.com>
 <qpf3l5x1cv1t.1140hptaimkr9$.dlg@40tude.net>
NNTP-Posting-Host: 75.170.65.61
Mime-Version: 1.0
X-Trace: posting.google.com 1339531946 21559 127.0.0.1 (12 Jun 2012 20:12:26
 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Tue, 12 Jun 2012 20:12:26 +0000 (UTC)
Cc: mailbox@dmitry-kazakov.de
In-Reply-To: <qpf3l5x1cv1t.1140hptaimkr9$.dlg@40tude.net>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=75.170.65.61;
 posting-account=_xNmGgoAAADzVbG1LIrTaXAR97KD43ZC
User-Agent: G2/1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Date: 2012-06-12T13:10:27-07:00
List-Id: <comp.lang.ada>

On Saturday, June 9, 2012 2:36:13 AM UTC-7, Dmitry A. Kazakov wrote:
> On Sat,  9 Jun 2012 11:25:05 +0200 (CEST), Nomen Nescio wrote:
> > The string library is feature-poor, so you'll find yourself writing bas=
ic
> > libraries for constructs that are included in many languages.
>=20
> The constructs which should probably be forbidden in first place. It is
> amazing to see what programmers usually write in C++ or C# when faced
> trivial problems of parsing some simple input.

One of my primary concerns is handling UTF-8, UTF-32, and arbitrary local e=
ncodings. The two models I'm familiar with are the Unicode-aware approach o=
f Python 3 and the strings-as-binaries approach of Erlang. What are the maj=
or differences between C and Ada in how you must approach Unicode text proc=
essing?