It is difficult and challenging to comprehend the internal aspects of a program. The internal aspects are seen as contrasts to end user aspects and interface aspects. Internal program documentation is relevant for almost any kind of software. The internal program documentation represents the original as well as the accumulated understanding of the program, which is very difficult to extract from the source program and its modifications over time. Elucidative Programming is a documentation technique that originally is inspired by Literate Programming. As an important difference between the two, Elucidative Programming does not call for any reorganization of the source programs, as required by Literate Programming tools. Elucidative Programming provides for mutual navigation in between program source files and sections of the documentation. The navigation takes place in an Internet browser applying a two-framed layout. In this paper we investigate the applicability of Elucidative Programming in a number of areas related to internal program documentation. It is concluded that Elucidative Programming can solve a number of concrete problems in the areas of program tutorials, frameworks, and program reviews. In addition we see positive impacts of Elucidative Programming in the area of programming education.

In this paper we present an integration of tool support for internal documentation in the modern IDE TogetherJ. The specific kind of internal documentation stems from the Elucidative Programming tradition where documentation and source code are separate entities tied together using hyperlinks. The tool supports the programmer in creating and managing internal documentation of Java source code. The hypertext-based documentation is presented in the IDE where a range of navigational features helps the programmer with finding relevant documentation for a given part of the source code. It is concluded that integration of such a tool is indeed possible as well as easy to do in an open IDE like TogetherJ. We expect that we can obtain similar results using other open IDEs.

Code generators are notoriously difficult to debug, yet their correctness is crucial. This paper demonstrates that concept assignment can be performed in an entirely syntax-directed manner for code generators and other highly structured program modules. Anomalies in this concept assignment indicate the possible existence of bugs. These insights enable the formulation of a new debugging technique for code generators. This paper describes the procedure, a practical implementation, and results from the application of this debugging technique to an experimental code generator.

The understanding of a program is a key aspect of software development. The understanding is a prerequisite for the initial development e#orts. This paper is concerned with the challenge of maintaining the program understanding with the purpose of supporting later phases in the program life time.

Categories and Subject Descriptors D.1.1 [Functional Programming]: Scheme, XML 1. INTRODUCTION XML [4] is a meta language, which is used to define high-level markup languages for a variety of different purposes. As for other high-level languages (such as high-level programming languages) there is a need to transform XML documents1 to lower-level languages. Often, but not necessarily, the target language is another XML language, such as XHTML [5]. Transformation of XML documents is of interest to the programming language community in general [24], and to the functional programming community in particular. A Haskell combinator library represent early work in the area [25].

Program documentation plays a vital role in almost all programming processes. Program documentation flows between separate tools of a modularized environment, and in between the components of an integrated development environment as well. In this paper we discuss the flow of program documentation between program development tools. In the central part of the paper we introduce a mapping of documentation flow between program development tools. In addition we discuss a set of locally developed tools which is related to program documentation. The use of test cases as examples in an interface documentation tool is a noteworthy and valuable contribution to the documentation flow. As an additional contribution we identify several circular relationships which illustrate feedback of documentation to the program editor from other tools in the development environment. 1.