 * Compile environment:
    - stage0 builds a CDL3 compiler from generated C sources. This
      generation should be automated, together with insertion of
      copyright and licensing information in each file.
    - stage1 builds a CDL3 compiler from the CDL3 sources in the src
      directory. The paths/presence of these files is not correct yet
      (it messes up on some build environments and requires explicit
      copying).
    - stage2 should build the real compiler natively (with the native
      code generator if it exists), but this stage is not used/does not
      work yet. This could also be used when you want to build a cross
      compiler (trivial modification but 100% unsupported yet).
    - Everything in the automatic build environment expects to build the
      C code generator. Support for (native) assembler generation should
      be added.
    - Check for latex in order to (optionally) build the documentation.

 * General source modifications:
    - Remove the usage of cpp (should be trivial).
    - (Better) source comments.
    - The sources could use some name changes and indentation in my
      opinion.

 * Compiler technical changes:
    - Polymorphism checks do sometimes report ambiguity while there is
      none (as far as I can see).
    - Check the tail-recursion optimization, I suspect it not to find
      all tail recursions.
    - Check the import/export checks, or (in case this is correctly 
      implemented) modify the error message "import of blah after
      export".
    - Check the Sparc code generation if it still works. The code
      generation could use some lines of comment on the jumptable used
      for failing rules etc.
    - Only after the checking the Sparc code generation: fix the i386
      code generation as it breaks with recent binutils' gas.

 * New additions:
    - It would be nice to use the CDL3 routines as an add-on library to
      other programs. The current problem is that the RTS and the code
      generation assume that it is the CDL3 program that is in control.
      Things that should be looked into is the main() in the CDL3 RTS,
      the name generation of the (generated) routines and the names of
      the constructors and destructors. Some documentation and an
      example would be very usefull.
    - The documentation could use a bit more explanation on the routines
      in the standard CDL3 library.
