Evolving a Reflective Language

Ducasse, Stephane; Denker, Marcus; Lienhard, Adrian

Document type :

Communication dans un congrès avec actes

DOI :

10.1145/1735935.1735949

Title :

Evolving a Reflective Language

Author(s) :

Ducasse, Stephane [Auteur]

Analyses and Languages Constructs for Object-Oriented Application Evolution [RMOD]
Denker, Marcus [Auteur]

Analyses and Languages Constructs for Object-Oriented Application Evolution [RMOD]
Lienhard, Adrian [Auteur]
Software Composition Group [Bern] [SCG]

Conference title :

International Workshop on Smalltalk Technologies

Conference organizers(s) :

ESUG

City :

Brest

Country :

France

Start date of the conference :

2009-08-31

Publisher :

ACM

Publication date :

2009

HAL domain(s) :

Informatique [cs]/Langage de programmation [cs.PL]

English abstract : [en]

Traits are method groups that can be used to compose classes. They do not have a runtime existence and are conceptually folded into the classes that use them. Traits have been implemented in different languages. While ...
Show more >Traits are method groups that can be used to compose classes. They do not have a runtime existence and are conceptually folded into the classes that use them. Traits have been implemented in different languages. While implementing them in Smalltalk, our first reflex was to take advantage of the fact that traits are not run-time entities: we optimized the implementation for space and hence shared methods between traits and classes. However, by doing so we broke the introspective API of Smalltalk. This paper illustrates a more general problem seen in all reflective systems: the implementation serves both as a model for execution and as the model that is exposed to the programmer. There is a conflict of interests between the information necessary for execution and the information the programmer is interested in. In addition, as soon as the implementation is exposed via reflection, we are not free to optimize. As the complete implementation is visible reflectively, there is no way to hide the optimizations. Few papers report errors and this is one of them. We report our experience facing the initial API mismatch, which has a significant impact on the system because the language is reflective (i.e., written in itself and causally connected). We present the new introspective API we put in place.Show less >

Language :

Anglais

Peer reviewed article :

Oui

Audience :

Internationale

Popular science :

Non

Collections :

Centre de Recherche en Informatique, Signal et Automatique de Lille (CRIStAL) - UMR 9189

Source :

Harvested from HAL

Files

https://hal.inria.fr/hal-00746130/document
Open access
Access the document

https://hal.inria.fr/hal-00746130/document
Open access
Access the document

document
Open access
Access the document

Duca09bTraitsAPI.pdf
Open access
Access the document

document
Open access
Access the document

Duca09bTraitsAPI.pdf
Open access
Access the document

Evolving a Reflective Language BibTeX CSV Excel RIS

Files

Evolving a Reflective Language

BibTeX

CSV

Excel

RIS