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,FREEMAIL_FROM autolearn=unavailable autolearn_force=no version=3.4.4 X-Received: by 2002:a6b:280d:: with SMTP id o13-v6mr919226ioo.130.1530718908542; Wed, 04 Jul 2018 08:41:48 -0700 (PDT) X-Received: by 2002:aca:2b06:: with SMTP id i6-v6mr495328oik.0.1530718908335; Wed, 04 Jul 2018 08:41:48 -0700 (PDT) Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.org!news.linkpendium.com!news.linkpendium.com!news.snarked.org!border2.nntp.dca1.giganews.com!nntp.giganews.com!d7-v6no1791642itj.0!news-out.google.com!l67-v6ni1747itl.0!nntp.google.com!d7-v6no1791639itj.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Wed, 4 Jul 2018 08:41:48 -0700 (PDT) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=90.197.114.51; posting-account=L2-UcQkAAAAfd_BqbeNHs3XeM0jTXloS NNTP-Posting-Host: 90.197.114.51 References: <70c11a71-3832-4f57-8127-f3f1c48a052f@googlegroups.com> <62e38ee4-f72f-4ed8-bef1-952040fb7f8d@googlegroups.com> <64d8b4a1-a92c-4b90-b95c-e821749de969@googlegroups.com> <887212304.552080112.848502.laguest-archeia.com@nntp.aioe.org> <87muvan83x.fsf@adaheads.home> <1449870001.552246132.581310.laguest-archeia.com@nntp.aioe.org> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <5de5f768-40bf-4518-a647-22788658de74@googlegroups.com> Subject: Re: Strange crash on custom iterator From: Lucretia Injection-Date: Wed, 04 Jul 2018 15:41:48 +0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Xref: reader02.eternal-september.org comp.lang.ada:53596 Date: 2018-07-04T08:41:48-07:00 List-Id: On Wednesday, 4 July 2018 15:37:40 UTC+1, Dan'l Miller wrote: > The difficulty is that =E2=80=A2no one=E2=80=A2 has the single =E2=80=A2s= olution=E2=80=A2 for this problem or these concomitant problems. Not even = J-P. Rosen is a possessor of complete solution in his Wide_Wide_String reco= mmendation, because his replies seem to factually-incorrectly imply that th= ere exists a fully-normalized single-codepoint character in Unicode/ISO1064= 6 for each grapheme/letter. JP Rosen told me to go read the AI on the matter, which I did. He states th= ey talked about it, there's not much talking in the AI at all! Bob Dewar st= ates they shouldn't really abuse the *String types by subtyping and does ex= actly that by introducing a package he wrote to handle UTF using those subt= ypes. The rest of the AI is about how to fit that into the standard. Back then, they should've chosen the Unicode standard over the ISO10646 as = it's freely available, yes the encodings are interchangeable, but that's no= t really the point.=20 They should've decided to obsolete the current mess, the same way they did = with ASCII and made String and Unbounded_String UTF-8 encoded. They could s= till have the old latin based strings as compatibility types. They should'v= e made all source be encoded the same way, which they did anyway for the is= o spec. Then defined a bunch of iterators for the types based on code points, graph= eme clusters, word/line boundaries, bidi, etc. Then taken out all references to characters as that concept isn't really ap= plicable to Unicode as a "character" can be one or more code points.