Re: Possible GNAT problem with aliased parameters.

[sbelmont700@gmail.com]

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?

type Paths is array (Positive range <>) of Maze_Ptr;

type Maze (p : access constant Paths) is ...

function Create (x : aliased Paths) is
begin
   return Maze'(p => x'access);
end Create;

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.

-sb