Markku Sakkinen. "Comments on "the Law of Demeter" and C++". ACM SIGPLAN Notices, 23(12):38--44, 1988.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....programming, including Flavors, Smalltalk 80, CLOS, C and Eiffel. 4. LH89c] We discuss tools for preventive maintenance of software which is written following the object oriented paradigm. Initial ideas on preventive maintenance of object oriented systems were presented in [LHR88] Sak88] LH89b] These papers describe a set of guidelines called the Law of Demeter .Demeter is the name of the object oriented CASE system we are working on [LR88a] Lie88] We discuss the implications of the Law for software maintenance. In the second part of the paper we discuss the advantages ....

....systems were presented in [LHR88] which describes a set of guidelines called the Law of Demeter . Demeter is the name of the object oriented CASE system we are developing [LR88a] Lie88] Lie92] As a result of this publication we have received much feedback, as well as a detailed critique from [Sak88] In this paper we expand on the initial ideas and present a new perspective with which to view the Law. This perspective is based on client supplier relationships between methods and classes and allows a cleaner description of the benefits of the Law. This paper is also a reply to [Sak88] which ....

[Article contains additional citation context not shown here]

Markku Sakkinen. Comments on "the Law of Demeter" and C++. SIGPLAN Notices, 23(12):38--44, December 1988.

....means less complexity. This was indeed a good assumption; but it has to be stated explicitly. Consider the program in Fig. 8. In this program there is no code for class Line. This is considered to be bad style, violating the Law of Demeter (for functions) which is discussed in several publications [LHR88, Sak88, LH89b, LH89a, Cas90, WBJ90]. 2.3 Extension and application So far we only dealt with pure class dictionary graphs. However, in practice we also use optional parts, repetition vertices (for possibly empty and non empty lists) and explicit inheritance 13 Triangle = one Line two Line three Line. Line = start Point ....

Markku Sakkinen. Comments on "the Law of Demeter" and C++. SIGPLAN Notices, 23(12):38--44, December 1988.

....produced automatically for them. A propagation pattern is a view of an integrated (and properly extended) domain model. Schema evolution is an important topic for object oriented data bases [DZ91] Propagation patterns facilitate evolution of the dynamic part of a schema. Markku Sakkinen writes in [Sak88]: The methods of a class should not depend in any way on the structure of any class, except the immediate top level structure of their own class. With propagation patterns we can now go further and require that in addition to Sakkinen s view of the Law of Demeter, methods only depend on the ....

Markku Sakkinen. Comments on "the Law of Demeter" and C++. SIGPLAN Notices, 23(12):38--44, December 1988.

....operations of the current object s class, the classes of its immediate subparts and of the classes of argument objects of O and the classes of objects created by O. This leads to a programming style which follows closely the part of structure of classes and is generally considered beneficial [Sak88,WJ90,Cas90]. The Law of Demeter promotes information restriction (a generalization of information hiding) The public interface of a class C may only be used in classes which are closely related to C. A set of method specifications that comply with the Law of Demeter will span a class dictionary subgraph ....

Markku Sakkinen. Comments on "the Law of Demeter" and C++. SIGPLAN Notices, 23(12):38--44, December 1988.

....of Demeter. The implication of this proof is that the Law of Demeter does not restrict what a programmer can solve, it only restricts how he or she solves it. We have also formulated interpretations of the Law for multiple programming languages [LH89b] Third party commentary on the Law includes [Boo91, Sak88, Bud91, Gra91]. The thesis of Casais [Cas90] examines the Law in depth and assesses its favorable impact on the problem of providing automatic support for rewriting code in response to changes in the class hierarchy. A slight dissenting voice was raised by Wirfs Brock et. al [WBW89] who prefer a function ....

....suppliers. As before, every class in an object oriented program is a potential supplier of any method. However, it is best to limit the suppliers to a method to a small set of preferred classes. To define these preferred suppliers we introduce the concept of an acquaintance class of a method ([Sak88], HB77] A precise definition of an acquaintance relies on a class version of the supplier concept. Informally, a method s supplier class is a class whose methods are called in the method. The definitions make a distinction between the classes associated with the declaration of the method and ....

[Article contains additional citation context not shown here]

Markku Sakkinen. Comments on "the Law of Demeter" and C++. SIGPLAN Notices, 23(12):38--44, December 1988.

No context found.

Markku Sakkinen. "Comments on "the Law of Demeter" and C++". ACM SIGPLAN Notices, 23(12):38--44, 1988.

No context found.

Markku Sakkinen. Comments on "the Law of Demeter" and C++. SIGPLAN Notices, 23(12):38--44, December 1988.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC