From: "Randy Brukardt" <randy@rrsoftware.com>
Subject: Re: interfaces and limited/controlled/limited-controlled types
Date: Thu, 25 Jan 2018 22:58:49 -0600
Date: 2018-01-25T22:58:49-06:00 [thread overview]
Message-ID: <p4eci9$ao7$1@franka.jacob-sparre.dk> (raw)
In-Reply-To: ea190839-2f83-4dbb-9064-8d6f535cc1d0@googlegroups.com
"Mehdi Saada" <00120260a@gmail.com> wrote in message
news:ea190839-2f83-4dbb-9064-8d6f535cc1d0@googlegroups.com...
> Is it only because of history and compatibility issues, that
> Limited_Controlled and Controlled aren't rewrote as interfaces ?
> Like: T_type is limited new Ancestor_type with Controlled
> or T_type is new Ancestor_type with Limited_Controlled
>
> Or is there a semantic issue too ?
A compatibility issue IS a semantic issue! Yes, the main reason is
compatibilty. We've looked at ways to allow Root_Streams_Type to be an
interface (same problem), and the levels of semantic trouble that occurs
makes it a dubious proposition (at least so far). The issue is still open:
AI12-0023-1, but it hasn't been worked on since 2012, so I wouldn't hold out
much hope that anything will happen here. The last meeting notes discuss
some of the problems involved
(http://www.ada-auth.org/ai-files/minutes/min-1206.html#AI023).
Randy.
next prev parent reply other threads:[~2018-01-26 4:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-25 16:21 interfaces and limited/controlled/limited-controlled types Mehdi Saada
2018-01-25 22:00 ` Robert Eachus
2018-01-26 4:58 ` Randy Brukardt [this message]
2018-01-26 8:28 ` Dmitry A. Kazakov
2018-01-26 11:17 ` Alejandro R. Mosteo
2018-01-27 7:12 ` Randy Brukardt
2018-01-27 14:04 ` Jere
2018-01-27 14:38 ` Dmitry A. Kazakov
2018-01-27 18:28 ` Jere
2018-01-29 23:05 ` Randy Brukardt
2018-01-29 23:03 ` Randy Brukardt
2018-01-31 11:54 ` Alejandro R. Mosteo
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox