1989
DOI: 10.1109/52.35588
|View full text |Cite
|
Sign up to set email alerts
|

Assuring good style for object-oriented programs

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
73
0
1

Year Published

1996
1996
2017
2017

Publication Types

Select...
6
2
2

Relationship

0
10

Authors

Journals

citations
Cited by 166 publications
(74 citation statements)
references
References 5 publications
0
73
0
1
Order By: Relevance
“…The framework is naturally compatible with objectoriented simulator development, in which the "least knowledge principle" [19], i.e., modules should hide details from each other, is obeyed. In our framework, if a module that computes a certain kind of quantity is initialized, the sparse pattern of the output gradient vector and the cached target column numbers depend only on the sparse pattern of input gradient vectors and the mathematical model contained in the module and do not include the details of how these input patterns are produced.…”
Section: The Feasibility Of the Backward Ad Frameworkmentioning
confidence: 97%
“…The framework is naturally compatible with objectoriented simulator development, in which the "least knowledge principle" [19], i.e., modules should hide details from each other, is obeyed. In our framework, if a module that computes a certain kind of quantity is initialized, the sparse pattern of the output gradient vector and the cached target column numbers depend only on the sparse pattern of input gradient vectors and the mathematical model contained in the module and do not include the details of how these input patterns are produced.…”
Section: The Feasibility Of the Backward Ad Frameworkmentioning
confidence: 97%
“…Highly coupled systems have long been recognized as hard to comprehend (Lieberherr and Holland 1989;Page-Jones 1980) because their modules cannot be considered in separation from each other.…”
Section: Motivationsmentioning
confidence: 99%
“…Examples include: the open/closed principle [34,32], the Liskov substitution principle [28,31], the acyclic dependencies principle [34,30], Favour composition over inheritance [26], the Law of Demeter [27], You ain't gonna need it (YAGNI) 2 and Tell, don't ask [3]. This lore is supplemented by design patterns and idioms, which provide prototypical solutions to common problems.…”
Section: Design Heuristicsmentioning
confidence: 99%