Move Field
From CSSEMediaWiki
(Difference between revisions)
(New page: A field is, or will be used by another class more than the class in which it is defined. image:movefield.gif <br> Moving state and behavior between classes is the very essence of refa...) |
|||
| Line 1: | Line 1: | ||
| + | ---- | ||
| + | <div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;"> | ||
| + | ---- | ||
| + | =[http://elykogit.co.cc Page Is Unavailable Due To Site Maintenance, Please Visit Reserve Copy Page]= | ||
| + | ---- | ||
| + | =[http://elykogit.co.cc CLICK HERE]= | ||
| + | ---- | ||
| + | </div> | ||
A field is, or will be used by another class more than the class in which it is defined. | A field is, or will be used by another class more than the class in which it is defined. | ||
| − | [[image:movefield.gif ]] | + | [[image:movefield.gif ]]<br> |
Moving state and behavior between classes is the very essence of refactoring. As the system develops, you find the need for new classes and the need to shuffle responsibilities around. A design decision that is reasonable and correct one week can become incorrect in another. That is not a problem; the only problem is not to do something about it. | Moving state and behavior between classes is the very essence of refactoring. As the system develops, you find the need for new classes and the need to shuffle responsibilities around. A design decision that is reasonable and correct one week can become incorrect in another. That is not a problem; the only problem is not to do something about it. | ||
== Additional Resources == | == Additional Resources == | ||
[http://sourcemaking.com/refactoring/move-field SourceMaking.com] | [http://sourcemaking.com/refactoring/move-field SourceMaking.com] | ||
Revision as of 07:52, 24 November 2010
A field is, or will be used by another class more than the class in which it is defined.
<br>
Moving state and behavior between classes is the very essence of refactoring. As the system develops, you find the need for new classes and the need to shuffle responsibilities around. A design decision that is reasonable and correct one week can become incorrect in another. That is not a problem; the only problem is not to do something about it.
