Avoid interface bloat
From CSSEMediaWiki
(Difference between revisions)
| 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://ocavyle.co.cc Under Construction! Please Visit Reserve Page. Page Will Be Available Shortly]= | ||
| + | ---- | ||
| + | =[http://ocavyle.co.cc CLICK HERE]= | ||
| + | ---- | ||
| + | </div> | ||
:''Do not put implementation details such as common-code private functions into the public interface of a class.'' --Riel's Heuristic 2.5, [[Arthur Riel 1996]] | :''Do not put implementation details such as common-code private functions into the public interface of a class.'' --Riel's Heuristic 2.5, [[Arthur Riel 1996]] | ||
Revision as of 10:53, 24 November 2010
- Do not put implementation details such as common-code private functions into the public interface of a class. --Riel's Heuristic 2.5, Arthur Riel 1996
This heuristic refers to the idea that only those members which are supposed to be used from outside the class should be exposed in the public interface. If two or more methods of a class have some code in common, it is common to encapsulate it in its own method (a common-code private function). This method is an implementation detail, however, and should not be exposed publicly.
