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:a6b:2c4f:: with SMTP id s76-v6mr648653ios.117.1530708384131; Wed, 04 Jul 2018 05:46:24 -0700 (PDT) X-Received: by 2002:aca:75c9:: with SMTP id q192-v6mr397981oic.3.1530708383893; Wed, 04 Jul 2018 05:46:23 -0700 (PDT) Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.org!border1.nntp.ams1.giganews.com!border2.nntp.ams1.giganews.com!nntp.giganews.com!newsfeed.xs4all.nl!newsfeed9.news.xs4all.nl!85.12.16.68.MISMATCH!peer01.ams1!peer.ams1.xlned.com!news.xlned.com!peer01.am4!peer.am4.highwinds-media.com!peer02.iad!feed-me.highwinds-media.com!news.highwinds-media.com!u78-v6no1653454itb.0!news-out.google.com!z3-v6ni1824iti.0!nntp.google.com!u78-v6no1653449itb.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Wed, 4 Jul 2018 05:46:23 -0700 (PDT) In-Reply-To: <7180e44d-6e11-4df3-ae01-96829298c03c@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> <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> <1ce9b9c8-b9cb-4ff4-b4c7-fe4827fea15b@googlegroups.com> <1f634e80-a1e7-4fb1-8cdf-5db6a773f36d@googlegroups.com> <9524b7ed-b3c4-4775-9e62-7455bf1633c1@googlegroups.com> <7180e44d-6e11-4df3-ae01-96829298c03c@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: Subject: Re: Strange crash on custom iterator From: "Dan'l Miller" Injection-Date: Wed, 04 Jul 2018 12:46:24 +0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Received-Bytes: 3853 X-Received-Body-CRC: 1356657200 Xref: reader02.eternal-september.org comp.lang.ada:53581 Date: 2018-07-04T05:46:23-07:00 List-Id: On Tuesday, July 3, 2018 at 8:59:59 PM UTC-5, Lucretia wrote: > On Wednesday, 4 July 2018 02:26:52 UTC+1, Dan'l Miller wrote: >=20 > > > I know the difference between code points and octets and their arrays= . I was saying that UTF_String is > > > not a valid subtype of String because String is Latin 1 and UTF_Strin= g is a superset of 7-bit ASCII, not > > > 8-bit Latin 1. > >=20 > > Well, there are 2 ways of looking at UTF-8: before versus after parsing= . > >=20 > > is not a superset: > > One is whether each 8-bit value in Latin-1 has the same value in the UT= F-8 octet-by-octet representation =E2=80=A2prior=E2=80=A2 to parsing. Usin= g this analysis, all of the upper 128 values have a different meaning than = in Latin-1. >=20 > You're answering a question that wasn't asked. > =20 > > is a superset: > > But the other way of looking at UTF-8 is what character is represented = by the multi-byte encoding =E2=80=A2after=E2=80=A2 parsing. In this view, = the lowest 256 values of Unicode/ISO10646 conform to Latin-1 (with some qui= bbling over whether the mark-parity control codes from 16#80 to 16#9F have = precisely the same meaning versus reserved/unencoded at various editions of= various standards). >=20 > And again, wasn't asked. It is quite on-topic though. This difference of looking at it from the pre= -parsed versus post-parsed perspectives is at the heart of the difference o= f opinion of Luke/Dmitry (String) versus J-P. Rosen (Wide_String and Wide_W= ide_String) arising throughout this thread.