Publications:MetaML and multi-stage programming with explicit annotations

From CERES
Jump to: navigation, search

Do not edit this section

Keep all hand-made modifications below

Title MetaML and multi-stage programming with explicit annotations
Author Walid Taha and Tim Sheard
Year 2000
PublicationType Journal Paper
Journal Theoretical Computer Science
HostPublication
DOI http://dx.doi.org/10.1016/S0304-3975(00)00053-0
Conference
Diva url http://hh.diva-portal.org/smash/record.jsf?searchId=1&pid=diva2:396142
Abstract We introduce MetaML, a practically motivated, statically typed multi-stage programming language. MetaML is a “real” language. We have built an implementation and used it to solve multi-stage problems. MetaML allows the programmer to construct, combine, and execute code fragments in a type-safe manner. Code fragments can contain free variables, but they obey the static-scoping principle. MetaML performs type-checking for all stages once and for all before the execution of the first stage. Certain anomalies with our first MetaML implementation led us to formalize an illustrative subset of the MetaML implementation. We present both a big-step semantics and type system for this subset, and prove the type system's soundness with respect to a big-step semantics. From a software engineering point of view, this means that generators written in the MetaML subset never generate unsafe programs. A type system and semantics for full MetaML is still ongoing work. We argue that multi-stage languages are useful as programming languages in their own right, that they supply a sound basis for high-level program generation technology, and that they should support features that make it possible for programmers to write staged computations without significantly changing their normal programming style. To illustrate this we provide a simple three-stage example elaborating a number of practical issues. The design of MetaML was based on two main principles that we identified as fundamental for high-level program generation, namely, cross-stage persistence and cross-stage safety. We present these principles, explain the technical problems they give rise to, and how we address with these problems in our implementation.