Re: High-Integrity OO and controlled types

[Robert A Duff <bobduff@shell01.TheWorld.com>]

"Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de> writes:

> If Unchecked_Deallocation is called on each allocated object controlled or
> with controlled components, that would make keeping the list of allocated
> objects superfluous. I think that restrictions should work in this
> direction.

Yes, it would make sense to have such a feature.  I'm happy to add as
many restrictions as customers need.

>> And it's not just overhead (as in run-time efficiency) -- it's the complexity of
>> the run-time support.
>
> Well, but this applies to compile time support too, e.g. optimization and
> the GENERICS! Pragmatically, yes, certainly more complex the language thing
> is, more likely it is broken. But it is a compiler's property. I, as a
> software designer, am not in the position to decide, if the given compiler
> has bugs and which language features get spoiled. Thus it does not belong
> to a profile.
>
>> And it's not access types per se -- it's heap-allocated objects
>> (i.e. "new") that introduces most of the complexity.
>
> I agree, but that is not specific to controlled types.

Heap-allocation has some complexity.  When controlled types are added,
there's a whole new layer of complexity.

- Bob