Re: Interresting difference in Normal-Returns/Expression-Functions and Extended-Returns.

["Randy Brukardt" <randy@rrsoftware.com>]

"Adam Beneschan" <adam@irvine.com> wrote in message 
news:f91ac67c-02c9-43fd-982c-a58567aa9a1b@googlegroups.com...
...
>"If the task is created by the evaluation of an allocator for a given
>access type, it depends on each master that includes the elaboration
>of the declaration of the ultimate ancestor of the given access type."
>
>The language here may be a bit sloppy, since for an anonymous access
>type, I'm not sure there's any such thing as "the declaration of
>... [a] given access type".

Wow, I think we've missed this Adam for a while! I'm pretty sure there is 
wording somewhere that says that where an anonymous access type is declared, 
but I'm not going to look it up right now. We spent way too much time 
rewriting this wording for Ada 2012, so I'm pretty sure it is consistent 
(now - the Ada 2005 wording was garbage).

...
>The moral: Whether or not you think anonymous access types are evil,
>anonymous access types to *tasks* definitely can have some surprising
>consequences (because of the task termination and dependency rules),
>and should be avoided.

You should extend this to anything that gets finalized, because you get the 
same sorts of issues with them. And since *everything* ought to be 
controlled (IMHO), ergo you have to avoid all anonymous access types. QED. 
:-)

                               Randy.