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:a02:9688:: with SMTP id w8-v6mr3465187jai.16.1532711490518; Fri, 27 Jul 2018 10:11:30 -0700 (PDT) X-Received: by 2002:aca:eb15:: with SMTP id j21-v6mr151920oih.6.1532711490379; Fri, 27 Jul 2018 10:11:30 -0700 (PDT) Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.org!goblin3!goblin.stu.neva.ru!news.misty.com!border2.nntp.dca1.giganews.com!nntp.giganews.com!d7-v6no1955954itj.0!news-out.google.com!k71-v6ni2220itk.0!nntp.google.com!d7-v6no1955952itj.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Fri, 27 Jul 2018 10:11:30 -0700 (PDT) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=76.113.16.86; posting-account=lJ3JNwoAAAAQfH3VV9vttJLkThaxtTfC NNTP-Posting-Host: 76.113.16.86 References: <72ccb7fa-a9cb-42e6-8c29-3c06da281a45@googlegroups.com> <2212eb54-cb4a-446f-9cdf-287ef220e2c2@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: Subject: Re: Ada Distilled by Richard Riehle From: Shark8 Injection-Date: Fri, 27 Jul 2018 17:11:30 +0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Xref: reader02.eternal-september.org comp.lang.ada:53981 Date: 2018-07-27T10:11:30-07:00 List-Id: On Friday, July 27, 2018 at 8:30:36 AM UTC-6, rabbi...@gmail.com wrote: > > That's what I think; but there's also a surprising amount of it that's = about sets, too. >=20 > In what way? Off hand I can't see where I've used that at all. The most obvious one is the TYPE / SUBTYPE relationship: TYPE: A set of values, and a set of operations on those values. SUBTYPE: A TYPE with an additional set of restrictions constraining the val= ues. Another was the CASE statement and its required coverage. A third [IIRC; this may have been my own realization] had to do with visibi= lity being treated as a set [of sets]: if a name exists uniquely, then that= is legal; if there is no existence at all, it's a case of either mistaking= the name or forgetting to WITH the dependency; if there are multiple exist= ences then the compiler must error-out and demand a qualified name, renamin= g, or other such resolution. {Extendible to overloading; which is a set of = names distinguished usually by parameter- or return-types.} >=20 > > Would you happen to recall what Richard said that so convinced you abou= t it? >=20 > I don't recall his exact words. To me the fact that I can uniquely tailor= each type to the real world.