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

[Simon Wright <simon@pushface.org>]

Martin <martin@thedowies.com> writes:

> Yes, but I'd rather go through set/get - direct access to attributes
> is content coupling...that's evil!! :-) and they're useful for
> breakpoints etc to see which call stack is setting a particular
> value...
>
> ...the other big problem, is that what you see on a OMD or CD wrt
> visibilties is not what you get in the code.

I would have thought it'd make more sense to provide accessors for the
public attributes (and not for the others) while keeping the public
attributes themselves private (protected?), since derived(?) classes
_should_ be able to see the protected attributes?

But, that said, it doesn't seem unreasonable to map the model's
attribute visibilities to accessor visibilities. What else should you
do?