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,5799fe4f91b50de
X-Google-Attributes: gid103376,public
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!news1.google.com!newsread.com!newsprint.newsread.com!news.glorb.com!zen.net.uk!dedekind.zen.co.uk!news-peer-lilac.gradwell.net!nntp-peering.plus.net!ptn-nntp-feeder01.plus.net!ptn-nntp-spool01.plus.net!ptn-nntp-reader04.plus.net!not-for-mail
Date: Thu, 25 Nov 2004 17:49:44 +0000
From: RAMatthews <ramatthews@noone.nowhere>
User-Agent: Mozilla/5.0 (X11; U; Linux i586; en-US; rv:1.7.3) Gecko/20040913
X-Accept-Language: en, en-us
MIME-Version: 1.0
Newsgroups: comp.lang.ada
Subject: Re: Possible Memory Leak
References: <fealnc.6t.ln@127.0.0.1> <qaOdnRZE_70GNT7cRVn-qA@megapath.net>
In-Reply-To: <qaOdnRZE_70GNT7cRVn-qA@megapath.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Message-ID: <41a61b3c$0$43598$ed2e19e4@ptn-nntp-reader04.plus.net>
Organization: Customer of PlusNet plc (http://www.plus.net)
NNTP-Posting-Host: ddf653ac.ptn-nntp-reader04.plus.net
X-Trace: 
 DXC=j3i0Bb^g8R4S5CJbl3g4?<igd3Y`7Rb;>3_LeXC3B]S9@]gS<8ko6e=LV8[D6e9H0=Me?nf_Q`BE;LX8JLNYAd3=
X-Complaints-To: abuse@plus.net
Xref: g2news1.google.com comp.lang.ada:6471
Date: 2004-11-25T17:49:44+00:00
List-Id: <comp.lang.ada>

Randy Brukardt wrote:
> "R A Matthews" <ram@noone.nowhere> wrote in message
> news:fealnc.6t.ln@127.0.0.1...
> 
>>This is probably one for the language lawyers...
> 
> ...
> 
>>Is the Standard wrong?
> 
> 
> Yes. We ran across this when we were developing Claw; the (now) SofCheck
> front-end followed the Standard language to the letter, and its a mess. We
> tried to fix the wording in the Corrigendum, but it took a long time to get
> it right, so it had to wait for the Amendment (that is, Ada 2005). See
> AI-147. (You'll note that there is a lot more confused in this area than
> just 7.6.1(21).)
> 
>                 Randy Brukardt
> 

Thank you.

With AI-147 in mind, I will assume that for the type of problem
in my orginal posting:
1) Where a compiler uses a temporary for assignment, then Adjust
    and Finalize are applied so that the target variable is adjusted
    and no memory leaks occur.
2) It is not necessary to introduce an aliased component just to
    make this work - so no use of Inner_Type, as in my original
    posting.



Robert A. Matthews