Move Field
From CSSEMediaWiki
(Difference between revisions)
m (Reverted edits by Ebybymic (Talk); changed back to last version by Paul Williams) |
|||
| Line 1: | Line 1: | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
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] | ||
Latest revision as of 03:10, 25 November 2010
A field is, or will be used by another class more than the class in which it is defined.
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.
