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:b548:: with SMTP id
 e69-v6mr872509iof.70.1530031855998;
        Tue, 26 Jun 2018 09:50:55 -0700 (PDT)
X-Received: by 2002:a9d:296a:: with SMTP id d97-v6mr115443otb.1.1530031855741;
 Tue, 26 Jun 2018 09:50:55 -0700 (PDT)
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.org!feeder.erje.net!2.eu.feeder.erje.net!newsfeed.xs4all.nl!newsfeed8.news.xs4all.nl!85.12.16.69.MISMATCH!peer02.ams1!peer.ams1.xlned.com!news.xlned.com!peer02.am4!peer.am4.highwinds-media.com!peer01.iad!feed-me.highwinds-media.com!news.highwinds-media.com!d7-v6no914443itj.0!news-out.google.com!z3-v6ni656iti.0!nntp.google.com!u78-v6no913821itb.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups: comp.lang.ada
Date: Tue, 26 Jun 2018 09:50:55 -0700 (PDT)
In-Reply-To: <lyzhzhtv5j.fsf@pushface.org>
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: <5e86db65-84b9-4b5b-9aea-427a658b5ae7@googlegroups.com>
 <foqjvhF8kskU1@mid.individual.net>
 <776f3645-ed0c-4118-9b4d-21660e3bba4b@googlegroups.com>
 <pg9bd9$eo9$1@gioia.aioe.org> <87602fbu2g.fsf@nightsong.com>
 <pgad3n$1sop$1@gioia.aioe.org> <87po0mziqt.fsf@nightsong.com>
 <pgbm5e$c1l$1@gioia.aioe.org> <87fu1izfgs.fsf@nightsong.com>
 <pgd1hq$ca2$1@gioia.aioe.org> <878t75nwad.fsf@adaheads.home>
 <pgqas8$mjm$1@dont-email.me> <pgqnt3$6rv$1@gioia.aioe.org>
 <fpcb15Fk3saU1@mid.individual.net> <pgqtq4$hon$1@gioia.aioe.org>
 <pgqv45$k7b$1@gioia.aioe.org> <pgr15g$nhb$1@gioia.aioe.org>
 <c43110cb-9dd3-4b3c-a0f2-533d27108ab3@googlegroups.com>
 <pgsqso$1ecd$2@gioia.aioe.org>
 <15b6f89f-997b-45ac-86b4-2e614bb624c2@googlegroups.com>
 <28a46046-e7eb-4306-bc39-72bc751831ae@googlegroups.com>
 <lyzhzhtv5j.fsf@pushface.org>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <ebcd41ce-672a-4102-a999-65dc7e477a70@googlegroups.com>
Subject: Re: Ada Successor Language
From: "Dan'l Miller" <optikos@verizon.net>
Injection-Date: Tue, 26 Jun 2018 16:50:55 +0000
Content-Type: text/plain; charset="UTF-8"
X-Received-Bytes: 3278
X-Received-Body-CRC: 619647338
Xref: reader02.eternal-september.org comp.lang.ada:53334
Date: 2018-06-26T09:50:55-07:00
List-Id: <comp.lang.ada>

On Tuesday, June 26, 2018 at 10:38:50 AM UTC-5, Simon Wright wrote:
> ric.wai88@gmail.com writes:
> 
> > I hope I can opt to be out-side of this "Ada" community who seem bent
> > on wasting copious time determining overly contrived ways of
> > destroying Ada from the inside out.. Apparently because Ada's
> > carefully enforced discipline is too inconvenient, or something.
> 
> I agree with you. It feels as though we have a few people around who
> enjoy wild flights of fancy.

I agree.  Ada does not need records with external-to-record tags.  (What the heck would we call these, btw?  Untagged tagged records?  Tagged untagged records?)

In a more general case, what Ada needs slightly more that is vaguely on a similar topic is satisfying Steelman requirement 3-3F, one of the very few Steelman requirements that Ada83 didn't live up to:
 https://www.dwheeler.com/steelman/steeltab.htm#3-3F

Presumably the external-to-record tag could be such a constant field of the record, where that field does not occupy storage in the record, as 3-3F requires permitting.

(But Steelman 3-3F does nothing to rectify my fear that the compiler would choose the wrong strong type and thus choose the wrong external-to-record tag in certain situations, importing C++ slicing into Ada.)