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=-0.3 required=5.0 tests=BAYES_00, REPLYTO_WITHOUT_TO_CC autolearn=no 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!news1.google.com!news3.google.com!feeder1-2.proxad.net!proxad.net!feeder2-2.proxad.net!newsfeed.arcor.de!newsspool3.arcor-online.net!news.arcor.de.POSTED!not-for-mail From: "Dmitry A. Kazakov" Subject: Re: High-Integrity OO and controlled types Newsgroups: comp.lang.ada User-Agent: 40tude_Dialog/2.0.15.1 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Reply-To: mailbox@dmitry-kazakov.de Organization: cbb software GmbH References: <679e3217-98dd-43c1-86f6-2038a029c3ea@b19g2000yqg.googlegroups.com> <94f3a272-d071-4a74-bfbd-8f2b4c2347cf@m10g2000yqd.googlegroups.com> <1iafnr1rbueaw.1bo3gcx227hx7.dlg@40tude.net> Date: Tue, 3 May 2011 19:37:01 +0200 Message-ID: NNTP-Posting-Date: 03 May 2011 19:36:59 CEST NNTP-Posting-Host: 59b79bf2.newsspool4.arcor-online.net X-Trace: DXC=FFoem4^HK0nUoRk[hk2Wal4IUK On Tue, 03 May 2011 12:53:13 -0400, Robert A Duff wrote: > "Dmitry A. Kazakov" writes: > >> There are three meaning of being controlled: >> >> 1. Ada 83 used it to refer memory allocation (pragma Controlled) >> 2. Since Ada 95 it is both >> 2.a. An ability to influence initialization and finalization >> 2.b. An ability to have a [non-generic] class > > I am unaware of 2.b. I know there are two meanings: 1 and 2.a. OK, 2.b (T'Class) is actually allowed for any tagged type. >> Yes, things need to be sorted out. > > Shrug. Nobody uses pragma Controlled, so I don't see a huge problem > with the terminology. I think that Maciej meant that initialization and finalization is orthogonal to an ability to form a class (or being tagged as one possible implementation of this). I agree with that, but in my view both should be allowed to all types anyway. If Ada reached that level of regularity I would like you not care about separation, but unfortunately it has not. Moreover many (not me) think that taggedness should be kept isolated, so the restriction goes. If this separation is to be maintained, one should make initialization and finalization independent on that. So, my opinion depends on path the language roadmap. -- Regards, Dmitry A. Kazakov http://www.dmitry-kazakov.de