Issue No. 03 - May/June (1999 vol. 25)
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/32.798327
<p><b>Abstract</b>—Interfaces—the collection of procedures and data structures that define a library, a subsystem, a module—are syntactically poor programming languages. They have state (defined both by the interface's data structures and internally), operations on this state (defined by the interface's procedures), and semantics associated with these operations. Given a way to incorporate interface semantics into compilation, interfaces can be compiled in the same manner as traditional languages such as ANSI C or FORTRAN. This paper makes two contributions. First, it proposes and explores the metaphor of <it>interface compilation</it>, and provides the beginnings of a programming methodology for exploiting it. Second, it presents M<scp>agik</scp>, a system built to support interface compilation. Using M<scp>agik</scp>, software developers can build optimizers and checkers for their interface languages, and have these extensions incorporated into compilation, with a corresponding gain in efficiency and safety. This organization contrasts with traditional compilation, which relegates programmers to the role of passive consumers, rather than active exploiters of a compiler's transformational abilities.</p>
Interface compilation, programming methodology, high-level languages, compiler optimization, interface checking, interface optimization.
D. R. Engler, "Interface Compilation: Steps Toward Compiling Program Interfaces as Languages," in IEEE Transactions on Software Engineering, vol. 25, no. , pp. 387-400, 1999.