vyzo

Ah, you can use `___PSTATE`. Can you try the following: ``` return ___make_pair(___PSTATE, row, col); ```

Notice you need 3 underscores for `___make_pair` and `___PSTATE`.

You can declare struct types for ffi, but accessors and mutators will need to be written by hand. We can probably concoct some macros that would automate the process. Btw,...

You can use any gambit module, but you'll have to write a small interface stub to define the exported symbols. See https://github.com/vyzo/gerbil/blob/master/src/std/text/base64.ssi for an example. There is no direct integration...

It's already straightforward to use pure Gambit code in Gerbil, all you need is the .ssi file to specify the exported symbols for the expander. And it works the other...

Also, you can always drop down to pure gambit in a Gerbil module with the `begin-foreign` form; that's what we use for inline ffi.

I should point out that the simplest way to cross compile is to compile a static executable with `-s -S`, which will generate a gambit scheme source file you can...

You still want it in Gerbil source? There is no easy way to save the expanded output of the compilation process, best we have is expanding to Gambit source.

You can easily get the expanded source however from the module context -- `module-context-code`, which you could write to a file.

So to recap: import your source file directoy with `import-module` and then use `module-context-code` in the resulting module context object to get the code, which you can then write to...