Delegation by object composition

Bettini, Lorenzo; Bono, Viviana; Venneri, Betti

doi:10.1016/j.scico.2010.04.006

Cited by 15 publications

(24 citation statements)

References 31 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…However, runtime type errors ("message-not-understood") can arise when no delegates are able to process the forwarded message [222] and also combining delegation with a static type discipline poses some problems [132]. In [33], a language is presented for incomplete objects (instances of abstract classes), providing object composition, dynamic method redefinition and delegation. All these operations are type safe, and possible ambiguities due to method name clashing are checked statically.…”

Section: Diversity In Implementationmentioning

confidence: 99%

Software diversity: state of the art and perspectives

Schaefer

Rabiser²,

Clarke

et al. 2012

Int J Softw Tools Technol Transfer

Self Cite

137

View full text Add to dashboard Cite

Abstract. Diversity is prevalent in modern software systems to facilitate adapting the software to customer requirements or the execution environment. Diversity has an impact on all phases of the software development process. Appropriate means and organizational structures are required to deal with the additional complexity introduced by software variability. This introductory article to the special section "Software Diversity -Modeling, Analysis and Evolution" provides an overview of the current state of the art in diverse systems development and discusses challenges and potential solutions. The article covers requirements analysis, design, implementation, verification and validation, maintenance and evolution as well as organizational aspects. It also provides an overview of the articles which are part of this special section and address particular issues of diverse systems development.

show abstract

Section: Diversity In Implementationmentioning

confidence: 99%

Software diversity: state of the art and perspectives

Schaefer

Rabiser²,

Clarke

et al. 2012

Int J Softw Tools Technol Transfer

Self Cite

137

View full text Add to dashboard Cite

show abstract

“…CompObJ relies on the approach that has been presented in [6]. However, there is a significant difference regarding the model of classes and objects.…”

Section: Introductionmentioning

confidence: 99%

“…However, there is a significant difference regarding the model of classes and objects. In [6] we had two separate hierarchies, standard classes (i.e., basically Java classes defined with the extends clause) and incomplete classes (with the abstracts clause for the superclass); for instance, standard classes could not inherit from incomplete classes. In CompObJ we unify the two concepts, in order to enhance the flexibility of classes and, in particular, of the objects.…”

Section: Introductionmentioning

confidence: 99%

“…In CompObJ we unify the two concepts, in order to enhance the flexibility of classes and, in particular, of the objects. As a consequence, with CompObJ we overcome the restrictions that were in [6] concerning the shape of object compositions, the nature of objects involved in a composition, and in particular the subtyping among objects. In [6] we only allowed an incomplete object to be composed with a complete object and the latter had to provide all the methods required by the former; thus, object compositions could produce complete objects only.…”

Section: Introductionmentioning

confidence: 99%

“…As a consequence, with CompObJ we overcome the restrictions that were in [6] concerning the shape of object compositions, the nature of objects involved in a composition, and in particular the subtyping among objects. In [6] we only allowed an incomplete object to be composed with a complete object and the latter had to provide all the methods required by the former; thus, object compositions could produce complete objects only. Instead, to add practicality to our approach, in CompObJ object composition can also produce incomplete objects and can compose two incomplete objects.…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Object reuse and behavior adaptation in Java-like languages

Bettini

Venneri

2011

Proceedings of the 9th International Conference on Principles and Practice of Programming in Java

Self Cite

View full text Add to dashboard Cite

Inheritance, which is a basic mechanism in mainstream objectoriented languages, introduces a strong coupling which limits modularity and code reuse. Furthermore, static class hierarchies cannot easily deal with unpredictable dynamic adaptations of the object behavior. In order to overcome these limitations, we propose new linguistic constructs for composing objects in a Java-like language. Objects are intended as featherweight components which can be used in multiple compositions, and object types specify not only the implemented functionalities, but also the required methods, which will be provided by other components during composition. Thus the language supports flexible object reuse and adaptation of the object behavior at run time. The static type discipline guarantees that method calls on well-typed object compositions are safe.

show abstract