DMCA
Reflection in Oberon (1997)
Cached
Download Links
- [www.ssw.uni-linz.ac.at]
- [www.oberon2005.ru]
- DBLP
Other Repositories/Bibliography
| Venue: | Proc. of the Joint Modular Languages Conference |
| Citations: | 3 - 0 self |
BibTeX
@INPROCEEDINGS{Steindl97reflectionin,
author = {Christoph Steindl},
title = {Reflection in Oberon},
booktitle = {Proc. of the Joint Modular Languages Conference},
year = {1997},
publisher = {Springer}
}
Share
 |
 |
 |
 |
||
OpenURL
Abstract
. We introduce metaprogramming facilities into the Oberon V4 system. Metaprogramming means that a module can access the structure of other modules (i.e., procedures, types, run-time data) at run time. We discuss how type safety can be enforced in an environment with strong typing. Finally we show how metaprogramming can be used to implement an easy-to-use database interface and conclude with a comparison with other metaprogramming systems for statically-typed programming languages. 1 Introduction In programs we distinguish between the data level and the program level. Variables are at the data level and can be accessed by the statements of a program. Modules, types and procedures are at the program level. They serve to structure a program but they are usually not viewed as data. Sometimes, however, programs want to inspect the components of other programs at the program level, for example, in order to answer the following questions: 1. What are the field names of a record type T decla...
