On Thu, 2013-02-14 at 18:21 +1100, William ML Leslie wrote: > On 13 February 2013 05:24, Mark H Weaver <m...@netris.org> wrote: > > Okay, but here I'm using "Static FFI" to mean something very different > > than the C API: I'm talking about a pure scheme-based API that would be > > quite similar to the API our current dynamic FFI, except that a lot of > > the work would be done at compilation time (probably during macro > > expansion). > > Maybe even something like LuaJIT FFI or python's CFFI - that can parse > C code at compile time to produce the data structures for the dynamic > FFI? >
I think that would be better. The reason why I don't use FFI is that we lack of convenient C struct parsing mechanism. Though it's not so hard to implement, designing proper APIs maybe take sometime. Anyway, I'd like to see a prototype, or maybe I could provide a naive one. ;-)
