Re: Gem 39 - compiler specific?

[Robert A Duff <bobduff@shell01.TheWorld.com>]

Adam Beneschan <adam@irvine.com> writes:

> However, one could make that case that if you declare a pool-specific
> access type, then by definition it should point to something that's in
> a pool; and that if you want an access that could point to an
> arbitrary address (as Access_To_Address_Conversions would let you do),
> you should use a general access type.

The term "pool specific" is a misnomer.  It's got nothing to do with
"storage pools".  This is my fault -- I was trying to reduce the amount
of terminology in Ada 95, by using the new term, but I must have been
confused when I did that.

The correct term should be "collection-specific", using the Ada 83 term
"collection".

So instead of your "in a pool" above, I'd put it this way: A
pool-specific (sic) access value has to point to some object
created by "new" for that access type.  (Well, I'm ignoring
derived access types, which are vanishingly rare in practice.)
It can't (legitimately) point to a stack object, a component
of another object, or an object created by "new" for some other
type.

- Bob