Quoth Ryan Newton <[email protected]>,
...
> Anyway, in this case it wasn't *too *painful to just generate a bunch of
> extra boilerplate C functions for (1) creating a data structure to hold the
> arguments, (2) loading them in one at a time, and (3) deallocating the
> structure when the call is done. Yuck. But no extra dependencies.
If I understand you right, that's a better direction in my view -
and when I've done stuff like this I've allocated and marshalled the
data structure from the Haskell side fairly painlessly with
Foreign.Storable(poke) etc., and the .hsc preprocessor macros for
struct access (#poke, etc.)
Donn
_______________________________________________
Haskell-Cafe mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/haskell-cafe
