© Jørgen Steensgaard-Madsen, Copenhagen, 2006
Download and installation of dulce                                                  

Download and installation is fairly simple:
  1. Create an installation directory and make it your current directory.

  2. Get the compressed tar-file with source texts:
    Click here to download

  3. Unpack the file (in the installation directory)
    tar xzf dulce.tgz
    This will create a hierarchy below the installation directory with a structure as
    /common   A directory with source texts for the common core
      /parsers   Contains flex and bison sources for scanner and parsers
    /example   A subhierarchy with Howard Language contributions, e.g
      /statements   Contributions for (mostly) well-known structured statements
      /variables   Contributions for simple and array variables
      /types   Contributions for type operators, like Array, List, etc.
      /multiprogramming   Contributions for threading
      ...   several more contributions
      /demo   Contains an interpreter also called demo and a syntax file demo.ulc
      Note that a syntax file contains signatures for the computation primitives.
    The interpreter .../example/demo/demo is a test language for an empty contribution. Some of the non-empty contribution directories also contain a test language. Every test language is characterised by the contributions it requires, but cyclic dependencies are not supported.

  4. On a Linux system you may proceed as follows
    make system  builds an interpreter for 'an empty language'
    (cd example; make all)   builds demo/demo and libraries for all contributions
    On other platforms you may have to modify the Makefile to reflect the environment. The system depends crucially on extensions supported by GNU C's trampolines. It has been built on a Windows platform with Cygwin, but only with static linking.
    The sources are written to use the readline library. This has two consequences: (1) if you redistribute a compiled version you need to investigate the conditions for use of this library; (2) on some platforms you might have to include some version of curses or ncurses to link the program successfully. You can make the system independent of the readline library by commenting out one line in common/parsers/scanner.yy and make the system again.

  5. On a platform with an apache webserver you may want to build the htel interpreter and install it with some auxiliary scripts in the server's cgi-bin hierarchy:
    (cd example; make web)
    Of course you need proper privileges to do so.


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