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=ham autolearn_force=no version=3.4.4 X-Google-Thread: 103376,4e5770c49b971630 X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news2.google.com!news.glorb.com!news.mv.net!nntp.TheWorld.com!not-for-mail From: Robert A Duff Newsgroups: comp.lang.ada Subject: Re: High-Integrity OO and controlled types Date: Tue, 03 May 2011 12:51:00 -0400 Organization: The World Public Access UNIX, Brookline, MA Message-ID: References: <47nrp21n5a5b.1tmmgxawdp4ko$.dlg@40tude.net> <1f1l5vmsetr53.q4i4vnava7yv.dlg@40tude.net> NNTP-Posting-Host: shell01.theworld.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: pcls6.std.com 1304441460 22692 192.74.137.71 (3 May 2011 16:51:00 GMT) X-Complaints-To: abuse@TheWorld.com NNTP-Posting-Date: Tue, 3 May 2011 16:51:00 +0000 (UTC) User-Agent: Gnus/5.1008 (Gnus v5.10.8) Emacs/21.3 (irix) Cancel-Lock: sha1:oIIwmMwvvVRwg5pO0eafCRmLYM8= Xref: g2news1.google.com comp.lang.ada:19145 Date: 2011-05-03T12:51:00-04:00 List-Id: "Dmitry A. Kazakov" 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