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-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,ce667ecdc314f22 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-03-07 13:52:22 PST Path: supernews.google.com!sn-xit-03!supernews.com!cyclone2.usenetserver.com!news-out.usenetserver.com!news.tele.dk!193.174.75.178!news-fra1.dfn.de!news-koe1.dfn.de!news-han1.dfn.de!news.fh-hannover.de!news.cid.net!news.enyo.de!news1.enyo.de!not-for-mail From: Florian Weimer Newsgroups: comp.lang.ada Subject: Re: Releasing Aliased Variables Date: 07 Mar 2001 22:31:54 +0100 Organization: Enyo's not your organization Message-ID: <87snkpxo39.fsf@deneb.enyo.de> References: <3AA692A8.F1283C27@netscape.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Xref: supernews.google.com comp.lang.ada:5521 Date: 2001-03-07T22:31:54+01:00 List-Id: Byron Kauffman writes: > I'm having a problem understanding what defining a variable as aliased > does. Is there a problem with releasing an aliased pointer? Can or > should you even alias a pointer? What is an 'aliased pointer'? Aliased objects are required if you want to obtain an access value (using the Access attribute). They don't need to be deallocated themselves, in contrast to objects created by an allocator.