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?
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
