Re: Package's private parts and protected types

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

On 8 fév, 11:20, "Dmitry A. Kazakov" <mail...@dmitry-kazakov.de>
wrote:
> On Mon, 8 Feb 2010 00:30:12 -0800 (PST), Martin wrote:
> > This is true of task types too.
>
> I don't think so. The task specification does not expose barriers and local
> variables of its body. But the protected type specification does its
> private operations and components:
I still think so :p
What about a task entry which should be accessible by some entities of
the package implementation ? I'm not talking about these task's
private entries intended for Requeue, I'm talking about an entry which
should be publicly available while still being available, not only
from the task itself, and also from the package body which hold the
task implementation.

> Obviously to me, the syntax should have been like:
>
>    type T is protected private; -- or "protected with private"
>    entry Foo (X : in out T);
>    function Bar (X : T) return Boolean;
> private
>    type T is protected record
>       ...
So, with absolute majority, the Gang Of Three voted there is a flaw
here

Yes, I would have enjoyed too a "protected [with] private".

>    end T;  -- I don't like "end record" either.
This makes me remind I will have to later reply to another thread
where you also talking about some other stuff you don't like