Re: Passing indefinite types

[Stephen Leake <stephen_leake@stephe-leake.org>]

sbelmont700@gmail.com writes:

> Does anyone know of a slick way to pass several locally declared,
> indefinite types to a subprogram without resorting to the heap or
> Unchecked_Access? 

Could you show some almost legal code?

> An array of indefinite types is obviously not possible, an array of
> named access types is subject to accessibility problems, and wrapping
> the object in an 'accessor' (i.e. a null record with an access
> discriminant) turns right back into a problem of an array of
> indefinite types. I can always declare a procedure that takes a bunch
> of individual parameters, but this seems like a kludge, and doesn't
> solve the problem if the number of items might vary. It would be nice
> if there was some way to establish that a discriminated record is in
> fact a fixed size, 

Is it fixed, or does it vary? you point out several solutions for fixed.

> or perhaps if an array of anonymous access types had the same
> accessibility as access discriminants. 

I gather the subprogram you are calling is at library level, or at least
at a less deep accessibility level than the objects? While the local
objects are on the stack. 

How is the subprogram declared? If it takes several parameters each of
different indefinite type, then you are fine. If it takes a record of
indefinite types, then they all must be access types, and
Unchecked_Acess is ok, as long as the subprogram promises not to copy
the pointer.

I wonder if it would be possible to write an aspect or other constraint
that asserts "no pointers are copied"?

-- 
-- Stephe