Previous Up Next

1  Introduction

Overview and structure

The order of the files corresponds to the order in which they appear in the compiler. more or less, at least.

Design principles and conventions

Changes to the module-version

In the structured version, I had split the packages for symbols and tables into two compilation units Symbol and Symboltable and used functors and module types. This allowed to postpone the definition of the actual symbols to a later time —within the semantic phase— but made the whole thing pretty obscure.

Building the compiler

We describe here the main “targets” one can do with the implementation. So in some sense it describes the targets of the makefile and how to use them. However, it gives also hints for the developer, how to change the makefile in case the compiler grows.

The code

1.1  Testing

In general

Is our test-concept something like unit-testing? If not, can one make the testing be even more systematic, perhaps one should use ounit.

1.2  Documentation

The documentation is based on a literate programming technology and uses ocamlweb.1 HTML-pages are generated via the LATEX-documet using hevea.2 Currently, ocamldoc is not used.

 ,
Previous Up Next