|Version 26 (modified by benl, 7 years ago)|
The Disciplined Disciple Compiler (DDC)
This is the developer's wiki for the Disciplined Disciple Compiler.
A summary of the project is at http://www.haskell.org/haskellwiki/DDC.
Our end goal is to have a light-weight functional language based on Haskell's syntax but with direct support for strict evaluation and arbitrary destructive update. These two features give the programmer better control over runtime performance than most other functional languages can offer. Our target applications are the ones that you always find yourself writing C programs for, because existing functional languages are too slow, use too much memory, or don't let you update the data that you need to.
State of Play
This section records what the DDC developers are actively working on. If you're hacking on something DDC related then by all means add yourself here. Records are dropped off if they haven't been updated for more than a month.
Ben (benl23) -- updated 4th Feb 2010
- DDC has reached a stage where can reasonably be expected to compile programs, but the compiler itself is very slow and there are lots of bugs. I'm currently refactoring the representation of types (in Type.Exp) to use a Data.Map to hold type constraints instead of a flat list. Along the way I'm redoing some of the more naive parts of the type inferencer, which should result in a major performance improvement. Once the representation of types has stabilised I'll be able to see about checking #2 (checking the types of instance functions against their definitions) which is a major cause of confusing panic messages.
- I'm also fixing up the buildbots and testing framework. I've acquired an Intel Core2 Duo/3GB laptop (discus.ouroborus.net) which is now our dedicated build server.
The Language Definition is still evolving, but the wiki should be in sync with the development branch.
- Compiler commentary
- Development Builds
- Haddock Code Documentation
- Syntax Highlighting
- Coding Conventions
- Debugging Help
- Making Patches
How you can help
- Download out the compiler, write programs, and file bug reports!
- Write more test programs.
- Fix the bugs on the 0.1.3 Buglist
- Write more quick check tests.