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!nntp-feed.chiark.greenend.org.uk!ewrotcd!newsfeed.xs3.de!io.xs3.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: grassroots thoughts on access types Date: Thu, 8 Feb 2018 19:23:47 -0600 Organization: JSA Research & Innovation Message-ID: References: <5d9134c9-a7d4-468e-8685-ebbb393eabea@googlegroups.com> Injection-Date: Fri, 9 Feb 2018 01:23:47 -0000 (UTC) Injection-Info: franka.jacob-sparre.dk; posting-host="rrsoftware.com:24.196.82.226"; logging-data="26522"; 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; Original X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.7246 Xref: reader02.eternal-september.org comp.lang.ada:50333 Date: 2018-02-08T19:23:47-06:00 List-Id: "Mehdi Saada" <00120260a@gmail.com> wrote in message news:5d9134c9-a7d4-468e-8685-ebbb393eabea@googlegroups.com... > In my corrected exercices, I can read: > > package P_Token.F is > type T_Ptr_Token is access all T_Token'Class; > end P_Token.F; > > package body P_Token.Operateur.F is > > type T_Ptr_Token_Operateur is access all T_Token_Operateur; > > function Set_Ptr (Elem : in T_Operateur) return T_Ptr_Token is > Ptr_Token : T_Ptr_Token_Operateur; > begin > Ptr_Token := new T_Token_Operateur; > Initialisation(Ptr_Token.all,Elem); > return Ptr_Token.all'access; -- @@@ HERE You could also have written: return T_Ptr_Token(Ptr_Token); Generally, type conversions for general access types are equivalent to ".all'Access". > end Set_Ptr; > > end P_Token.Operateur.F; > > and > > I understand the line marked (took me several minutes though ;-) ) but not > the logic. Instead of > function Set_Ptr (Elem : in T_Operateur) return T_Ptr_Token is > Ptr_Token : T_Ptr_Token_Operateur; > can we write: > function Set_Ptr (Elem : in T_Operateur) return T_Ptr_Token is > Ptr_Token : T_Ptr_Token; > ? What's the difference regards to implementation, memory usage or > anything ? > T_TOKEN is a null tagged record type, T_TOKEN_OPERATEUR has one more > enumerative component. No difference that I can see. T_Ptr_Token_Operateur seems like a totally unnecessary type to me, since the allocator would work just as well with T_Ptr_Token. (But I haven't tried this in an actual compiler, so I might have forgotten something subtle.) Randy.