© Jørgen Steensgaard-Madsen, Copenhagen, 2006
Making Howard Language Contributions                                                  

Incremental construction of interpreters is emphasised with dulce. This motivates the term contributor, rather than language implementor, for a person using dulce to build an interpreter. It also motivates the sequence of presentation below, which depends on a particular work organisation: a development tree with special files in the top and contributions provided in subdirectories, called contribution directories. Simple naming conventions eases the otherwise tedious tasks of managing compilation and linking of semantic libraries and test languages.
An appropriate development plan is to have a number of directories each one holding the files of a language contribution. These can be subdirectories of a directory containing in addition a few special files with information shared by the contributions as well as makefiles for the developer.
A contributor will most likely select a small language for testing the contribution, e.g. draw on a contribution providing file operations. The makefile in a contribution directory simply mentions the contributions needed for the language of testing and leaves the building of the interpreter for it to make. A final interpreter can then be characterised as a language for testing an empty contribution.


Demo language
·Implementation tool

·Interpreter construction

Contribution directory
Make commands
Auxiliary files
Toplevel files

File translated from TEX by TTH, version 3.33.
On 18 Oct 2006, 16:47.
SourceForge.net Logo