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 Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!news.eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!aioe.org!.POSTED!not-for-mail From: Victor Porton Newsgroups: comp.lang.ada Subject: Re: We should introduce aliased types Date: Fri, 01 Aug 2014 22:16:32 +0300 Organization: Aioe.org NNTP Server Message-ID: References: NNTP-Posting-Host: AnnUDmZwVERVUXyHDyOl5A.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7Bit X-Complaints-To: abuse@aioe.org User-Agent: KNode/4.12.4 X-Notice: Filtered by postfilter v. 0.8.2 Xref: news.eternal-september.org comp.lang.ada:21376 Date: 2014-08-01T22:16:32+03:00 List-Id: Victor Porton wrote: > I think we should introduce aliased types to allow self-referencing > objects and objects which we can access for object's internal purposes: > > type T is aliased > record > Ptr: access all T; > end; > > Every value of an aliased type should be aliased (whether we specify that > the particular value if aliased or don't specify). > > Then we could create a self-referencing object by a code (say in > Initialize) like this: > > declare > X: T; > begin > X.Ptr = X.Unchecked_Access; > end; One situation in which we need aliased types (not a single aliased variable) is Initialize() procedure for controlled types. -- Victor Porton - http://portonvictor.org