Sure, once there is a relationship you can make pretty tree diagrams, but that is again, based on perspective.
And just as a draftsman will use a picture to create a piece of machinery, we can chart out software to ensure its cohesiveness and viability.
If you find that the system you're developing is too mutable, it may be that you're observing several different, but interrelated systems which are part of a larger whole.
So, theorhetically, is manipulating an objects inheritence based on how it is currently being percieved, a worthwhile cause for meditation?
This would be the object oriented version of GOTO spaghetti code.
Further, I seem to remember that part of perl objects get memoized by the compiler at some point in time (methods? ->can calls?), so horribly mutating an object like this might not do what you want, depending on what you've already done to it.
-
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.
|