Using Metaobject Protocols to Separate Functional and Non- Functional Concerns: An Example

One of the key ideas underlying the DeVa conceptual framework is the notion of using reflection as a general approach to implementing non-functional requirements such as dependability and distribution transparency in a way that is transparent to application programmers [Stroud 1993]. In this paper, we use the example of atomic data types to explain why we believe that reflection is an appropriate way of implementing these kinds of non-functional requirements transparently by contrasting a conventional implementation of atomic data types with a reflective implementation [Stroud & Wu 1995]. We also discuss the kind of support that needs to be provided by reflective language systems for this kind of programming.