Re: Protected Type compiler complaint

[Georg Bauhaus <rm.dash-bauhaus@futureapps.de>]

On 07.07.14 21:06, framefritti wrote:
> by its own nature a protected object acts as a communication mean between different tasks, so it is "natural" that it must be visible to "everyone" (although you could partially restrict its visibility by placing it inside a suitable child package).

By the nature of communication, a protected object used as a means
of communication just needs to be visible where needed. Its type
may be more global.
If tasks are started from within a subprogram doing auxiliary work
not useful anywhere else, chances are that their definition profits
from being local to the subprogram, possibly referring to local items.
Then there is no need that some PO exist outside the subprogram: