RE: OOP and ancestor access

[Brennan Young]

"Ken Prat" <[EMAIL PROTECTED]> wrote

> Maybe the problem is a conceptual one. The 'idea' of an accessor method ties
> you into the 'idea' that "here is my data -- do with it what you will".

Yes! Spot on! Accessors (of the get or set variety) are problematic in that
they tempt lazy encapsulation.

That's not to say you can't use accessors without ending up with a sloppy
design, just that it's easier for things to become 'leaky' when you do.

-- 
_____________

Brennan

[To remove yourself from this list, or to change to digest mode, go to
http://www.penworks.com/LUJ/lingo-l.cgi  To post messages to the list,
email [EMAIL PROTECTED]  (Problems, email [EMAIL PROTECTED])
Lingo-L is for learning and helping with programming Lingo.  Thanks!]