Evolving a Reflective Language

Ducasse, Stephane; Denker, Marcus; Lienhard, Adrian

Type de document :

Communication dans un congrès avec actes

DOI :

10.1145/1735935.1735949

Titre :

Evolving a Reflective Language

Auteur(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]

Titre de la manifestation scientifique :

International Workshop on Smalltalk Technologies

Organisateur(s) de la manifestation scientifique :

ESUG

Ville :

Brest

Pays :

France

Date de début de la manifestation scientifique :

2009-08-31

Éditeur :

ACM

Date de publication :

2009

Discipline(s) HAL :

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

Résumé en anglais : [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 ...
Lire la suite >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.Lire moins >

Langue :

Anglais

Comité de lecture :

Oui

Audience :

Internationale

Vulgarisation :

Non

Collections :

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

Source :

Harvested from HAL

Fichiers

https://hal.inria.fr/hal-00746130/document
Accès libre
Accéder au document

https://hal.inria.fr/hal-00746130/document
Accès libre
Accéder au document

document
Accès libre
Accéder au document

Duca09bTraitsAPI.pdf
Accès libre
Accéder au document

document
Accès libre
Accéder au document

Duca09bTraitsAPI.pdf
Accès libre
Accéder au document

Evolving a Reflective Language BibTeX CSV Excel RIS

Fichiers

Evolving a Reflective Language

BibTeX

CSV

Excel

RIS