It sounds plausible to have shared-library C-code that is
statically linked to Haskell code but it also sounds as if
there could be subtle (beyond me), important distinctions here?
Our local who knows most about autotools typically manages
to remove (define) one of the undef' Haskell library labe
Printable pdf-version at:
http://www.math.utu.fi/icalp04/icalp-call.pdf
___
CALL FOR PAPERS - ICALP'04
31st International Colloquium on
Automata, Languages and Programming
July 12
[The following GPLed program may be of interest to you if:
- You want examples of programs written in Haskell that do something
useful.
- You sometimes hack C code as well as Haskell and want to make
your code smaller, faster or better structured.
- You want a library of code for parsing and m
> In article <[EMAIL PROTECTED]>,
> "Simon Marlow" <[EMAIL PROTECTED]> wrote:
>
> > There is a new release of Haddock, version 0.6. This
> version has several
> > improvements over the previous release; the full list is below.
>
> Excellent! I was stuck on implicit parameters for awhile.
We are pleased to announce Chameleon version 03-11.
Latest version can be downloaded via
http://www.comp.nus.edu.sg/~sulzmann/chameleon/
The current version is a substantial improvement over previous versions.
New/Improved features include:
* Compilation of Chameleon to (plain) Haskell.
