Re: Ada202X: Easy to use "UML private"-like components

["Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>]

On Sat, 22 Jun 2013 04:16:55 -0700 (PDT), Martin wrote:

> On Friday, June 21, 2013 3:51:32 PM UTC+1, Dmitry A. Kazakov wrote:
>> On Fri, 21 Jun 2013 02:33:11 -0700 (PDT), Martin wrote:
>> 
>>> But no easy means of keeping member data private from children.
>> 
>> On the contrary, don't make them children.
> 
> But then I loose visibility of the classes protected operations...

No operation can be both protected and private, not even in UML...

The point is that Ada offers the same choice as UML does. However the roles
are different. UML follows C++ where it is the provider of the type who
must choose between public/protected/private. In Ada its public vs. not
public for this role. Protected vs. public is to be decided by the user,
i.e. much later.

It is a good approach IMO, because protected vs. private choice is
frequently far to premature for the provider. A too heavy burden to do, as
usage of C++ shows. In the end the most sound policy for C++ is to avoid
private operations except for the cases when Ada programmer would a
subprogram into the package body.

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de