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,FORGED_MUA_MOZILLA
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Thread: 103376,40843b637af826a
X-Google-NewGroupId: yes
X-Google-Attributes: gida07f3367d7,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Received: by 10.180.93.6 with SMTP id cq6mr5653194wib.2.1354095825096;
        Wed, 28 Nov 2012 01:43:45 -0800 (PST)
Path: 
 ha8ni62191wib.1!nntp.google.com!proxad.net!feeder1-2.proxad.net!feeder.erje.net!eu.feeder.erje.net!newsfeed.datemas.de!weretis.net!feeder4.news.weretis.net!news.teledata-fn.de!newsfeed.arcor.de!newsspool2.arcor-online.net!news.arcor.de.POSTED!not-for-mail
Date: Wed, 28 Nov 2012 10:43:52 +0100
From: Georg Bauhaus <rm.dash-bauhaus@futureapps.de>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7;
 rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
Newsgroups: comp.lang.ada
Subject: Re: IBM 437 encoded String to UTF-16 Wide_String
References: <11112110-03b1-4977-ba80-00204926ea23@googlegroups.com>
 <68663891-14ad-4780-a00d-1cc48ed75323@googlegroups.com>
 <027679a1-dc5e-4888-9dd1-2a4ccf32e66c@googlegroups.com>
 <mv2j5fu41fb6.rc23cjp3s2bs$.dlg@40tude.net>
In-Reply-To: <mv2j5fu41fb6.rc23cjp3s2bs$.dlg@40tude.net>
Message-ID: <50b5dcd0$0$6581$9b4e6d93@newsspool3.arcor-online.net>
Organization: Arcor
NNTP-Posting-Date: 28 Nov 2012 10:43:44 CET
NNTP-Posting-Host: 6f8248a4.newsspool3.arcor-online.net
X-Trace: 
 DXC=Ni_JJWPXXN2_A0jCfgHO6>McF=Q^Z^V384Fo<]lROoR18kF<OcfhCO;N;4mkgO5a?;nc\616M64>:Lh>_cHTX3j=6n\on<dGZY6
X-Complaints-To: usenet-abuse@arcor.de
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Date: 2012-11-28T10:43:44+01:00
List-Id: <comp.lang.ada>

On 28.11.12 09:52, Dmitry A. Kazakov wrote:
> No. IMO the most convenient way would be to fix the language in order to
> have Wide_Wide_String'Class of which String, Wide_String, Wide_Wide_String,
> UTF8_String etc were members.

If there isn't anything special about {Wide_}Character,
a Vector of Character might be an alternative, though hated
by haters of generics, I should think.

As a practical alternative, why not add a generalized
std::valarray<type T = (<>)> to the language instead
of fixing it?