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
Path: 
 g2news2.google.com!news2.google.com!npeer03.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!nx01.iad01.newshosting.com!newshosting.com!newspeer.monmouth.com!newsswitch.lcs.mit.edu!nntp.TheWorld.com!not-for-mail
From: Robert A Duff <bobduff@shell01.TheWorld.com>
Newsgroups: comp.lang.ada
Subject: Re: put of access type
Date: Fri, 21 Aug 2009 20:07:32 -0400
Organization: The World Public Access UNIX, Brookline, MA
Message-ID: <wccmy5semnv.fsf@shell01.TheWorld.com>
References: <oham855g1rctflnjnoabr77kk4jngm479m@4ax.com>
 <tepiq2z1i4ya.1lxwo4nf59zlk$.dlg@40tude.net>
 <8sho8596j3qnja38id9ipejk0opkcn5b5m@4ax.com>
 <c9aec6d6-4e9b-4bf6-9586-68a237175c9d@i18g2000pro.googlegroups.com>
 <h6hvcc$2ni$1@munin.nbi.dk> <4a8cea9c$1@news.post.ch>
 <h6kp73$rbe$1@munin.nbi.dk> <wccr5v5xlza.fsf@shell01.TheWorld.com>
 <h6n4fg$i4b$1@munin.nbi.dk>
NNTP-Posting-Host: shell01.theworld.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Trace: pcls4.std.com 1250899652 16330 192.74.137.71 (22 Aug 2009 00:07:32
 GMT)
X-Complaints-To: abuse@TheWorld.com
NNTP-Posting-Date: Sat, 22 Aug 2009 00:07:32 +0000 (UTC)
User-Agent: Gnus/5.1008 (Gnus v5.10.8) Emacs/21.3 (irix)
Cancel-Lock: sha1:lnBRtecTB6YrAG3Itj9i2cjgZm0=
Xref: g2news2.google.com comp.lang.ada:7957
Date: 2009-08-21T20:07:32-04:00
List-Id: <comp.lang.ada>

"Randy Brukardt" <randy@rrsoftware.com> writes:

> "Robert A Duff" <bobduff@shell01.TheWorld.com> wrote in message 
> news:wccr5v5xlza.fsf@shell01.TheWorld.com...
> ...
>> I think that still works fine in Ada 95/2005 for pool-specific access
>> types (which is the only kind that existed in Ada 83).  The only
>> relevant language change is that you can convert from pool-specific to
>> general.  So you have to be able to take your offset, and produce a
>> "full" address, or whatever a general access type is represented as.  As
>> far as I can see, the addition of user-defined storage pools to the
>> language is irrelevant here.
>
> I don't see how this could work. There is no call-back to the storage pool 
> when converting from pool-specific to general access, so how could the pool 
> make the conversion?

I'm lost.  You said Ada 83 compilers can represent access types as
offsets from some known place.  I agree.  And I claim Ada 95/2005
compilers can do the same.  Nothing to do with storage pools, which did not
exist in Ada 83.

- Bob