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
X-Received: by 2002:a24:908:: with SMTP id 8-v6mr1407936itm.36.1530730767694;
        Wed, 04 Jul 2018 11:59:27 -0700 (PDT)
X-Received: by 2002:a54:4e94:: with SMTP id c20-v6mr620762oiy.5.1530730767489;
 Wed, 04 Jul 2018 11:59:27 -0700 (PDT)
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.org!feeder4.usenet.farm!feed.usenet.farm!weretis.net!feeder6.news.weretis.net!feeder.usenetexpress.com!feeder-in1.iad1.usenetexpress.com!border1.nntp.dca1.giganews.com!border2.nntp.dca1.giganews.com!nntp.giganews.com!d7-v6no1948565itj.0!news-out.google.com!l67-v6ni1905itl.0!nntp.google.com!u78-v6no1938109itb.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups: comp.lang.ada
Date: Wed, 4 Jul 2018 11:59:27 -0700 (PDT)
In-Reply-To: <eade8b90-f4d8-4113-a9d3-7fd0a16d79ad@googlegroups.com>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com;
 posting-host=47.185.195.62;
 posting-account=zwxLlwoAAAChLBU7oraRzNDnqQYkYbpo
NNTP-Posting-Host: 47.185.195.62
References: <70c11a71-3832-4f57-8127-f3f1c48a052f@googlegroups.com>
 <lytvpks65b.fsf@pushface.org>
 <64d8b4a1-a92c-4b90-b95c-e821749de969@googlegroups.com>
 <lya7rc9iw0.fsf@pushface.org>
 <887212304.552080112.848502.laguest-archeia.com@nntp.aioe.org>
 <87muvan83x.fsf@adaheads.home> <ly4lhiafs8.fsf@pushface.org>
 <1449870001.552246132.581310.laguest-archeia.com@nntp.aioe.org>
 <lyzhz98lvh.fsf@pushface.org>
 <b0d7482d-3c02-4e0b-8720-58ee5b65af03@googlegroups.com>
 <phg0h7$10dd$1@gioia.aioe.org>
 <c980d621-6d5d-4a23-8005-733bb024285d@googlegroups.com>
 <phg5nk$1a46$1@gioia.aioe.org> <phg6cg$1ba2$1@gioia.aioe.org>
 <bd52280b-662a-49b3-891d-e39044e2bf32@googlegroups.com>
 <phg8lo$1fnq$1@gioia.aioe.org>
 <phht7f$1vj2$1@gioia.aioe.org> <phhuei$1v6$1@gioia.aioe.org>
 <phi5hp$fbv$1@gioia.aioe.org> <phi5t5$g0q$1@gioia.aioe.org>
 <phib5i$pt9$1@gioia.aioe.org> <87efginb3c.fsf@adaheads.home>
 <eade8b90-f4d8-4113-a9d3-7fd0a16d79ad@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <ead50ae7-25cb-4ccf-8146-0e221714b68d@googlegroups.com>
Subject: Re: Strange crash on custom iterator
From: "Dan'l Miller" <optikos@verizon.net>
Injection-Date: Wed, 04 Jul 2018 18:59:27 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Xref: reader02.eternal-september.org comp.lang.ada:53608
Date: 2018-07-04T11:59:27-07:00
List-Id: <comp.lang.ada>

On Wednesday, July 4, 2018 at 1:06:17 PM UTC-5, Shark8 wrote:
> On Wednesday, July 4, 2018 at 11:51:20 AM UTC-6, Jacob Sparre Andersen wr=
ote:
> >=20
> > It would be nice if the encoding and character set of a string were
> > "implementation details".  I'm not sure how to do it, but I think it is
> > worth trying to find a solution for Ada.  (I think I was introduced to
> > how the KDE library does it once, but IIRC only encoding was abstracted
> > away.)
>=20
> Indeed so!
> This is the way we /should/ have strings; where [[Wide_]Wide_]String are =
all generic with things like 'character-set' and 'search' and 'encoding' as=
 formal parameters.
>=20
> Sadly this will likely never happen because it would break backwards comp=
atibility.

Then do it outside of the standardization process in a Boost-esque library =
on GitHub/GitLab/SourceForge to launch a de facto standard that establishes=
 ISO's vaunted =E2=80=98established industry practice=E2=80=99.  If C++ can=
 do it, then so can Ada.

That being said, I believe that a far better model than Boost's exists for =
the cream rising to the top.  Instead of battle-of-the-emails-establishes-k=
ing-of-the-hill dominance hierarchies (with all due respect to the esteemed=
 Jordan Peterson), I would recommend multiple concurrently-competing librar=
y designs, then a rigorous (repeated? annual?) bake-off among the competito=
rs, evaluating multiple criteria:  runtime performance, engineering-time de=
sign flexibility/tunabilty/ease-of-use, maintainability over time.  Oh, cal=
l them the Yellow, Blue, Red, and Green libraries.  Who did =E2=80=A2that=
=E2=80=A2 before for language definition?  =E2=80=A6  but for potential sta=
ndard library content instead this time.