Re: Possible GNAT problem with aliased parameters.

[Shark8 <onewingedshark@gmail.com>]

On Sunday, October 20, 2013 9:33:15 AM UTC-6, sbelm...@gmail.com wrote:
> As long as you are onto the heap anyway, why not just make the client create the array (with items on the heap) save a reference to that, and avoid all the headaches?

For what I'm doing the main use-case is reading from a text-file, building the structures, and passing that out to some game-"engine"/interface. -- I just wanted/needed a way to create the objects programatically to ensure the read/write are correct, and it seemed odd that the aliased parameters weren't working as expected.

> The use case I would like is essentially this, with some magic feature that lets you satisfy the accessibility check for local values since the code is obviously not creating dangling pointers.  After all, you can pass pointers safely by themselves (access parameters) and nested within a record (access discriminant), so there ought to be some mechanism that allows you to pass them around safely within an array, if for no other reason that consistency.

Interesting; I _think_ the reason that the access-discriminant works is that the record itself has a deeper level than the access, thus when the record leaves scope the access may or may not be viable: the access could have the same scope as the record, or the record nested inside the scope declaring the access.