Minimize number of methods
From CSSEMediaWiki
(Difference between revisions)
JaninaVoigt (Talk | contribs) (→See also) |
WarwickIrwin (Talk | contribs) m (Noted opposing force) |
||
| Line 2: | Line 2: | ||
This heuristic ensures that you can always find the method that you are looking for, and enhances reusability. This is tied to the idea of [[You ain't gonna need it]] - don't implement methods until you need them. | This heuristic ensures that you can always find the method that you are looking for, and enhances reusability. This is tied to the idea of [[You ain't gonna need it]] - don't implement methods until you need them. | ||
| + | |||
| + | An opposing force is [[Behavioral completeness]]. | ||
== See also == | == See also == | ||
Revision as of 23:16, 22 July 2009
- Minimize the number of messages in the protocol of a class. --Riel's Heuristic 2.3, Arthur Riel 1996
This heuristic ensures that you can always find the method that you are looking for, and enhances reusability. This is tied to the idea of You ain't gonna need it - don't implement methods until you need them.
An opposing force is Behavioral completeness.
