Re: Preventing type extensions

[Cyrille <comar@eu.adacore.com>]

> The one that forbids redispatching in favour of class-wide operations.
> This can be done only in Ada, and can be a big plus for testing.

Well, I don't see anything unique to Ada in that respect except
terminology. In term of capabilities with regard to dispatching, at
least.

> For inlining, I was referring to the corresponding chapter of OOTiA

That's what I supposed.... There is little to be reused in that part
of the document...

> >> The workshop at the conference is the starting point for a document that
> >> will define appropriate restrictions ("Fairfax profile"). Starting such
> >> an effort during an Ada conference seems absolutely appropriate.
>
> > It seems a bit early, DO-178C hasn't been published yet and people
> > participating to such an effort will need time to access it once it is
> > published and understand it.
>
> I couldn't get my hands on DO-178C, but form what I heard it will be
> based (at least on the principles) on the work of OOTiA, which
> originated from the C++ community and ignores the possibilities offered
> by class-wide types - that was the starting point of this thread.

It is not the case. There is very little of OOTiA left in the OO
supplement. It was an input to the process but the subcommittee soon
realized that little could be reused. For one thing, most of the
material is at the level of "coding standard" material and thus not at
the right level for a standard such as DO-178.