Nil or export coupling only

From CSSEMediaWiki
(Difference between revisions)
Jump to: navigation, search
(See also)
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://egebyromedu.co.cc This Page Is Currently Under Construction And Will Be Available Shortly, Please Visit Reserve Copy Page]=
 +
----
 +
=[http://egebyromedu.co.cc CLICK HERE]=
 +
----
 +
</div>
 
:''Classes should only exhibit nil or export coupling with other classes, i.e. a class should only use operations in the public interface of another class or have nothing to do with that class'' --Riel's Heuristic 2.7, [[Arthur Riel 1996]]
 
:''Classes should only exhibit nil or export coupling with other classes, i.e. a class should only use operations in the public interface of another class or have nothing to do with that class'' --Riel's Heuristic 2.7, [[Arthur Riel 1996]]
  

Revision as of 05:22, 24 November 2010


Classes should only exhibit nil or export coupling with other classes, i.e. a class should only use operations in the public interface of another class or have nothing to do with that class --Riel's Heuristic 2.7, Arthur Riel 1996

Classes should only depend on the public methods of another class or nothing at all. Other forms of coupling give away implementation details of a class, which is bad for maintenance when implementations need to be changed.

Riel also states that class cohesion ensures that all elements of a class are related.

See also

Personal tools