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,73175d2d01a1b1dd
X-Google-NewGroupId: yes
X-Google-Attributes: gida07f3367d7,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Received: by 10.68.50.133 with SMTP id c5mr27545095pbo.2.1317113873249;
        Tue, 27 Sep 2011 01:57:53 -0700 (PDT)
Path: 
 lh7ni5860pbb.0!nntp.google.com!news1.google.com!news4.google.com!feeder.news-service.com!aioe.org!.POSTED!not-for-mail
From: "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>
Newsgroups: comp.lang.ada
Subject: Re: subprogram must not be deeper than access type
Date: Tue, 27 Sep 2011 10:58:21 +0200
Organization: cbb software GmbH
Message-ID: <4a6e5qupjkkm.r0diwisnx60m.dlg@40tude.net>
References: <slrnj7trhq.i18.lithiumcat@sigil.instinctive.eu>
 <818752663338654817.822041rmhost.bauhaus-maps.arcor.de@news.arcor.de>
 <slrnj80ieh.i18.lithiumcat@sigil.instinctive.eu>
 <wccmxdr772s.fsf@shell01.TheWorld.com>
 <15r7hdzgyr0fc.1djn7vwy23dfg$.dlg@40tude.net>
 <wccehz3jn48.fsf@shell01.TheWorld.com>
 <1uqthqxzri6j3.i18ifhbwmzdc.dlg@40tude.net>
 <wccy5xa95r2.fsf@shell01.TheWorld.com>
Reply-To: mailbox@dmitry-kazakov.de
NNTP-Posting-Host: FbOMkhMtVLVmu7IwBnt1tw.user.speranza.aioe.org
Mime-Version: 1.0
X-Complaints-To: abuse@aioe.org
User-Agent: 40tude_Dialog/2.0.15.1
X-Notice: Filtered by postfilter v. 0.8.2
Xref: news1.google.com comp.lang.ada:18154
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Date: 2011-09-27T10:58:21+02:00
List-Id: <comp.lang.ada>

On Mon, 26 Sep 2011 20:41:05 -0400, Robert A Duff wrote:

> "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de> writes:
> 
>> On Mon, 26 Sep 2011 12:15:51 -0400, Robert A Duff wrote:
>>
>>> And it's just weird that if you say "X, Y : array...;"
>>> "X := Y;" and "if X = Y ..." are illegal.  Textual replacement is
>>> a wrong way to define semantics.
>>
>> But structural type matching is more wrong than that.
> 
> Mostly true.  But if the opposite of "structural typing"
> is "by name", then it makes no sense.  There's no name for
> that type, here.

There is a name, the programmer just didn't reveal it to us.

>> 1. Strictly heap access types, manually allocated/deallocated, no
>> accessibility checks, no calls to Finalize outside Unchecked_Deallocation.
> 
> Not even when the access type is finalized?

Yes, it is the user's responsibility to deallocate objects. I can also
imagine cases where controlled objects could be purposely allocated, but
never freed, e.g. compiler tables of tokens.

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de