Re: Package's private parts and protected types

["Hibou57 (Yannick Duchêne)" <yannick_duchene@yahoo.fr>]

On 9 fév, 20:34, Hibou57 (Yannick Duchêne) <yannick_duch...@yahoo.fr>
wrote:
> Synchronized-and-the-like interface types are limited, so the built-in-
> place is indeed really built-in-place (no kind of conversion allowed
> at any stage). The initializer function have to return a class wide
> and return it using an extended return statement which is required to
> return the same exact type/subtype as the one function returns.
>
> This way of doing thing is not compatible with the implementation-
> hiding requirement, as it would require the implementation type to be
> exposed in the public part, so that I could define a public function
> returning this exact type.

I forget to underline : an extension aggregate which would have
otherwise make it possible to initialize a limited class wide type in
an extended return statement, does not work here, as we are to create
a task or protected object (I do not know such a thing as extension
aggregates for Protected and Task).