From: "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>
Subject: Re: changing rules for anonymous access types to named ones
Date: Tue, 3 Apr 2018 10:41:10 +0200
Date: 2018-04-03T10:41:10+02:00 [thread overview]
Message-ID: <p9ven5$10kk$1@gioia.aioe.org> (raw)
In-Reply-To: ab5cde73-e1fa-412c-ae47-4d1f07adabe0@googlegroups.com
On 02/04/2018 23:09, Jean-Claude Rostaing wrote:
>> general access type to solve the compilation error:
> Yeah, but it's ugly and I won't write "access all" if if I'm not really gonna use a pointer on the stack...
> I think it's a compiler issue, as like I said, I found no rules about access types, in the interface issue. Also, the interface are said to be pretty much equivalent to "type blablabla is abstract tagged null record"....
Interface = abstract type - representation - bodies of operations
There should have been none in this form, just abstract types + multiple
inheritance.
P.S. Interfaces should be anonymous, e.g. T'Interface, the interface of
the type T. So that you could derive from T dropping its representation
and implementations of all operations. For example:
type My_Custom_Integer is new Integer'Interface with record
-- Whatever I see appropriate to represent integer
end record;
-- overriding all operations, since they are inherited abstract
--
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de
next prev parent reply other threads:[~2018-04-03 8:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-02 16:39 changing rules for anonymous access types to named ones Jean-Claude Rostaing
2018-04-02 18:04 ` Jere
2018-04-02 21:09 ` Jean-Claude Rostaing
2018-04-03 8:41 ` Dmitry A. Kazakov [this message]
2018-04-03 11:29 ` Jean-Claude Rostaing
2018-04-03 12:44 ` Dmitry A. Kazakov
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox