If this is but one viewpoint, then it is a viewpoint that I like hearing from. :-)
I still have much thinking to do with regards to this notion. But I do
think one of OO's non-explicitly recognized advantages is that of managing
coupling. The object is an interface to a set of coupled code, relieving
both the object writer and the object user from having to manage that
aspect of code complexity themselves.
And, one of OO's disadvantages is not recognizing this explicitly, because
we then we could have much more meaningful discussions about such
controversies as: Are getter/setter methods evil when used from outside the
object? from inside the object? Should objects be divorced from their UI
via a controller? encapsulate their UI? or provide proxy UI objects? How do
we reconcile full encapsulation with inheritance?
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Outside of code tags, you may need to use entities for some characters:
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
|
|
