Re: [Q] non-limited record and "self-pointer"

["Robert I. Eachus" <rieachus@comcast.net>]

Stephen Leake wrote:


> This definitely looks like a compiler bug. Perhaps because Container
> is tagged, Read_Only_Set is being labeled "aliased". But that's not in
> the ARM.

I don't see that.  3.10(9) says in part: "Finally, the current instance 
of a limited type, and a formal parameter or generic formal object of a 
tagged type are defined to be aliased."

Note that this applies to parameters, not to objects.  So a type 
definition can include a self reference as in the example, and the 
compiler should only object if you declare an object of the type that is 
not aliased.

However there is a big bug here that should be fixed in Ada 0Y.  If 
parameters of a type are aliased, it doesn't make any sense to require 
users to declare objects of the type as explicitly aliased.  But that's 
the way it currently is, and I have some code now that has aliased in 
object declarations all over the place.  I also feel the same way about 
objects with aliased components.  Is there really any benefit to not 
making objects of a type with aliased components always aliased?


-- 
                                           Robert I. Eachus

"The war on terror is a different kind of war, waged capture by capture, 
cell by cell, and victory by victory. Our security is assured by our 
perseverance and by our sure belief in the success of liberty." -- 
George W. Bush