Inheriting Multiple and Repeated Parts in Timor.

Keedy, James Leslie; Heinlein, Christian; Menger, Gisela

doi:10.5381/jot.2004.3.10.a1

Cited by 8 publications

(21 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Technically, reuse variables in Timor also reduce this dependency, but in their paper [19], the authors do not present this insight.…”

Section: Reducing Hierarchy Dependenciesmentioning

confidence: 96%

A Higher Abstraction Level Using First-Class Inheritance Relations

Dooren¹,

Steegmans²

2007

ECOOP 2007 – Object-Oriented Programming

View full text Add to dashboard Cite

Although classes are a fundamental concept in object-oriented programming, a class itself cannot be built using general purpose classes as building blocks in a practical manner. High-level concepts like associations, bounded values, graph structures, and infrastructure for event mechanisms which form the foundation of a class cannot be reused conveniently as components for classes. As a result, they are implemented over and over again.We raise the abstraction level of the language with a code inheritance relation for reusing general purpose classes as components for other classes. Features like mass renaming, first-class relations, high-level dependencies, component parameters, and indirect inheritance ensure that maximal reuse can be achieved with minimal effort.A case study shows a reduction of the code between 21% and 36%, while the closest competitor only reduces the size between 3% and 12%.

show abstract

“…Technically, reuse variables in Timor also reduce this dependency, but in their paper [19], the authors do not present this insight.…”

Section: Reducing Hierarchy Dependenciesmentioning

confidence: 96%

A Higher Abstraction Level Using First-Class Inheritance Relations

Dooren¹,

Steegmans²

2007

ECOOP 2007 – Object-Oriented Programming

View full text Add to dashboard Cite

show abstract

“…Timor's rich type system allows types to be defined in terms of the inheritance paradigm [11,12,15] and/or as "adjectival" types [14,16]. But since the methods of such types (even the bracket methods of qualifying types) can be regarded as instance methods and makers, they need not be discussed in detail here.…”

Section: Other Timor Typesmentioning

confidence: 99%

Persistent Objects and Capabilities in Timor.

Keedy¹,

Espenlaub²,

Heinlein³

et al. 2007

JOT

Self Cite

View full text Add to dashboard Cite

The paper describes how the idea of persistent objects is integrated into the Timor programming language. The strategy adopted allows types to be instantiated at two levels: as "files", i.e. objects accessible at the operating system level, and as local objects within files, which resemble objects found in conventional object oriented programs. File objects (with associated methods) can be instantiated and manipulated via capabilities, which are accessible both internally and via the operating system. Local objects are accessible via references, which are not visible at the operating system level. PERSISTENT OBJECTS AND CAPABILITIES IN TIMOR104 J OURNAL OF OBJECT TECHNOLOGY V OL. 6, NO. 4 PERSISTENT OBJECTS AND CAPABILITIES IN TIMOR 106 J OURNAL OF OBJECT TECHNOLOGY V OL. 6, NO. 4 final op String name(String name); final enq String name(); and the abstract reference spouse corresponds to the methods: final op Person* spouse(Person* spouse); final enq Person* spouse(); PERSISTENT OBJECTS AND CAPABILITIES IN TIMOR 122 J OURNAL OF OBJECT TECHNOLOGY

show abstract

“…Other approaches that aim at reconciling the partially conflicting concepts of aggregation and inheritance are parts inheritance in Timor [19] and compound references in [30].…”

Section: Inheritance and Aggregationmentioning

confidence: 99%

“…The proposed solutions range from totally rejecting multiple inheritance (e. g., in Smalltalk [11]) over restricting it to inheritance of interfaces (e. g., in Java [1]) to supporting it in a rather general way (e. g., in Eiffel [26], C++ [33], and Timor [19,20]) with quite different syntactical and semantical forms. In any case, however, numerous specialized language constructs and partially sophisticated rules are required to support at least the most frequently occurring cases in practice.…”

Section: Inheritance and Aggregationmentioning

confidence: 99%

Open Types and Bidirectional Relationships as an Alternative to Classes and Inheritance.

Heinlein¹

2007

JOT

Self Cite

View full text Add to dashboard Cite

Open types are presented as a simple yet powerful data model for statically typed procedural and object-oriented programming languages, that overcomes the limitations of the traditional record-oriented model. The basic idea is to separate type definitions from the definitions of their attributes in order to allow incremental definitions of the latter. Furthermore, bidirectional relationships are introduced as pairs of mutually inverse attributes whose values will be kept consistent automatically. Finally, anonymous and automatic attributes are presented as a simple extension of attributes that unifies the concepts of aggregation, inheritance (including subtype polymorphism), and user-defined type conversions. Since open types do not possess methods in the objectoriented sense, global virtual functions are used as an alternative and more flexible means to define behaviour, while modules are employed to achieve information hiding and type-safe separate compilation. The basic implementation ideas of open types as a language extension for C++ are described.

show abstract

Inheriting Multiple and Repeated Parts in Timor.

Cited by 8 publications

References 8 publications

A Higher Abstraction Level Using First-Class Inheritance Relations

A Higher Abstraction Level Using First-Class Inheritance Relations

Persistent Objects and Capabilities in Timor.

Open Types and Bidirectional Relationships as an Alternative to Classes and Inheritance.

Contact Info

Product

Resources

About