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 Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.org!gandalf.srv.welterde.de!news.jacob-sparre.dk!franka.jacob-sparre.dk!pnx.dk!.POSTED.rrsoftware.com!not-for-mail From: "Randy Brukardt" Newsgroups: comp.lang.ada Subject: Re: Strange crash on custom iterator Date: Thu, 5 Jul 2018 13:08:34 -0500 Organization: JSA Research & Innovation Message-ID: References: <70c11a71-3832-4f57-8127-f3f1c48a052f@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> <87efginb3c.fsf@adaheads.home> Injection-Date: Thu, 5 Jul 2018 18:08:35 -0000 (UTC) Injection-Info: franka.jacob-sparre.dk; posting-host="rrsoftware.com:24.196.82.226"; logging-data="23223"; mail-complaints-to="news@jacob-sparre.dk" X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.5931 X-RFC2646: Format=Flowed; Response X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.7246 Xref: reader02.eternal-september.org comp.lang.ada:53658 Date: 2018-07-05T13:08:34-05:00 List-Id: "Dmitry A. Kazakov" wrote in message news:phj5j9$bju$1@gioia.aioe.org... > On 2018-07-04 20:06, Shark8 wrote: >> On Wednesday, July 4, 2018 at 11:51:20 AM UTC-6, Jacob Sparre Andersen >> wrote: >>> >>> 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.) >> >> 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. >> >> Sadly this will likely never happen because it would break backwards >> compatibility. > > It would break nothing. Old package will become renamings of new > instances. Well, except for dire deforestation should new RM be ever > printed... That's not possible. As you like to say, String /= String'Class. The new libraries would almost all take String'Class (or whatever stand-in there is). Randy.