Should superclasses be abstract?

Hürsch, Walter L.

doi:10.1007/bfb0052174

Cited by 18 publications

(6 citation statements)

References 10 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…To simplify the approach we assume that only concrete objects are instantiated (No. 22), a restriction that is akin to the abstract superclass rule [11]. Further, we only consider single specialization (No.…”

Section: Ddi With Object Specializationmentioning

confidence: 99%

Dual Deep Instantiation and Its ConceptBase Implementation

Neumayr

Jeusfeld

Schrefl

et al. 2014

Advanced Information Systems Engineering

View full text Add to dashboard Cite

Abstract. Application integration requires the consideration of instance data and schema data. Instance data in one application may be schema data for another application, which gives rise to multiple instantiation levels. Using deep instantiation, an object may be deeply characterized by representing schema data about objects several instantiation levels below. Deep instantiation still demands a clear separation of instantiation levels: the source and target objects of a relationship must be at the same instantiation level. This separation is inadequate in the context of application integration. Dual deep instantiation (DDI), on the other hand, allows for relationships that connect objects at different instantiation levels. The depth of the characterization may be specified separately for each end of the relationship. In this paper, we present and implement set-theoretic predicates and axioms for the representation of conceptual models with DDI.

show abstract

Section: Ddi With Object Specializationmentioning

confidence: 99%

Dual Deep Instantiation and Its ConceptBase Implementation

Neumayr

Jeusfeld

Schrefl

et al. 2014

Advanced Information Systems Engineering

View full text Add to dashboard Cite

show abstract

“…A Operational semantics, definitions of lookup, subtypes, acyclic programs, and agreements Figures 14,15,16, and 17 list all the rewrite rules of FickleII. Fig.…”

Section: Conclusion and Further Workmentioning

confidence: 99%

A provenly correct translation of Fickle into Java

Ancona

Anderson

Damiani

et al. 2007

ACM Trans. Program. Lang. Syst.

View full text Add to dashboard Cite

Abstract. We present a translation from Fickle, a small object-oriented language allowing objects to change their class at run-time, into Java. The translation is provenly correct, in the sense that we have shown it to preserve the static and dynamic semantics. Moreover, it is compatible with separate compilation, since the translation of a Fickle class does not depend on the implementation of used classes. Based on the formal system, we have developed an implementation. The translation turned out to be a more subtle problem than we expected, and the proofs helped us uncover several subtle errors. In this paper, we discuss four different possible approaches we considered for the design of the translation and justify our choice, we present formally the translation and the proof of preservation of the static and dynamic semantics, and we discuss the prototype implementation. The language Fickle has undergone, and is still undergoing several phases of development. In this paper we are discussing the translation of FickleII.

show abstract

“…Grosberg [18] resolved this problem by saying that a class that has sub-classes may not have direct instances and, conversely, that a class that may be directly instantiated may not have sub-classes. H ursch [19] later formulated this as the abstract super-class rule, which his analysis determined was a good programming guideline.…”

Section: Squares Rectangles and Abstract Superclassesmentioning

confidence: 99%

An Aristotelian understanding of object-oriented programming

Rayside

Campbell

2000

SIGPLAN Not.

View full text Add to dashboard Cite

The folklore of the object-oriented programming community at times maintains that object-oriented programming has drawn inspiration from philosophy, speci cally that of Aristotle. We investigate this relation, rst of all, in the hope of attaining a better understanding of object-oriented programming and, secondly, to explain aspects of Aristotelian logic to the computer science research community (since it di ers from rst order predicate calculus in a number of important ways). In both respects we endeavour to contribute to the theory of objects, albeit in a more philosophical than mathematical fashion. ) Man is mortal. 2.Man is mortal. Socrates is a man.) Socrates is mortal. 3.Homo erectus stands upright. Homo sapiens evolved from homo erectus.

show abstract

Should superclasses be abstract?

Cited by 18 publications

References 10 publications

Dual Deep Instantiation and Its ConceptBase Implementation

Dual Deep Instantiation and Its ConceptBase Implementation

A provenly correct translation of Fickle into Java

An Aristotelian understanding of object-oriented programming

Contact Info

Product

Resources

About