Topic
Program transformation
About: Program transformation is a research topic. Over the lifetime, 2468 publications have been published within this topic receiving 73415 citations.
Papers published on a yearly basis
Papers
More filters
01 Dec 1997
TL;DR: It is argued that runtime program transformation, partial evaluation, and dynamic compilation are essential tools for automated generation of flexible, highly interactive graphical interfaces and bridge the gap between a high-level, functional description and an efficient implementation.
Abstract: We argue that runtime program transformation, partial evaluation, and dynamic compilation are essential tools for automated generation of flexible, highly interactive graphical interfaces. In particular, these techniques help bridge the gap between a high-level, functional description and an efficient implementation. To support our claim, we describe our application of these techniques to a functional implementation of n-Vision, a real-time visualization system that represents multivariate relations as nested 3D interactors, and to Auto Visual, a rule-based system that designs n-Vision visualizations from high-level task specifications. n-Vision visualizations are specified using a simple functional language. These programs are transformed into a cached dataflow graph. A partial evaluator is used on particular computation-intensive function applications, and the results are compiled to native code. The functional representation simplifies generation of correct code, and the program transformations ensure good performance. We demonstrate why these transformations improve performance and why they cannot be done at compile time.
13 citations
24 Sep 2007
TL;DR: The overall methodology for the evolution of software towards new architectures is described and issues of the implementation of the approach based on existing tools are discussed.
Abstract: In this paper, we report on the development of a methodology for the evolution of software towards new architectures. In our approach, we represent source code as graphs. This enables the use of graph transformation rules, allowing the automation of the transformation process. Prior to its model representation, the source code is subject to a preparatory step of semi-automatic code annotation according to the contribution of each of its parts in the target architecture. This paper first describes the overall methodology and then focuses on the code annotation and model transformation parts. We also discuss issues of the implementation of the approach based on existing tools.
13 citations
TL;DR: This work studies the problem of suggesting code repairs at design time, based on the warnings issued by modular program verifiers, and introduces the concept of a verified repair, a change to a program's status quo.
Abstract: We study the problem of suggesting code repairs at design time, based on the warnings issued by modular program verifiers. We introduce the concept of a verified repair, a change to a program's sou...
13 citations
TL;DR: This work provides a pragmatic, transformation-based approach for expressing and tracking changes in rule-based programs in the course of program evolution, and designs an operator suite for the transformation of rule- based programs.
13 citations
Proceedings Article•
16 Jan 2006TL;DR: This paper verify mechanically that the source program and the CPS-transformed program have the same observable behavior, and formalizes the formalization of one-pass call-by-value CPS compilation using higher-order abstract syntax.
Abstract: In this paper, we study the formalization of one-pass call-by-value CPS compilation using higher-order abstract syntax. In particular, we verify mechanically that the source program and the CPS-transformed program have the same observable behavior. A key advantage of this approach is that it avoids any administrative redexes thereby simplifying the proofs about CPS-translations. The CPS translation together with its correctness proof is implemented and mechanically verified in the logical framework Twelf.
13 citations