Re: Taking 'Access of single task/protected object

["Jeffrey R. Carter" <spam.jrcarter.not@spam.not.acm.org>]

On 01/07/2016 09:18 AM, G.B. wrote:
> It seems impossible to take the 'Access (or 'Unchecked_Access)
> of a single task object, since it cannot be made aliased.
> And, I guess, as it is not of a named type, so that there
> is no way to express even an anonymous access type.
> 
>   task Single is
>      entry Something;
>   end Single;
> 
>   ...some_context (access_discriminant => Single'Access)...

I don't see how you could declare the discriminant, since it requires an access
definition, which requires a designated subtype.

Suppose you could do this somehow. Then every object of the type with the
discriminant would point to the same task. So there would be no need for the
discriminant, since the operations of the type could simply call the entries of
the task directly.

Presumably the desire is to have multiple single tasks, all with an entry
Something, so that the operations of the type can call different tasks. In this
situation, there would be a finite set of known single tasks, so the type could
hold the task ID of the appropriate task, and operations could select the task
to call based on the ID.

-- 
Jeff Carter
"My brain hurts!"
Monty Python's Flying Circus
21