You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
That opcode can be used for calling native code, but it was mainly intended for
testing native code generation from owl. It calls the machine code stored in a
byte vector, which is assumed to be a function of 3 arguments. A few old tests
are at
https://github.com/aoh/owl-lisp/blob/588fabfd69dbf1a5eb714961452586b00b8160a6/mi
sc/native.scm
Owl doesn't have a proper FFI at the moment. Feel free to post here if you have
need for one and I'll see what I can do, or if you have interest to work on it
yourself.
Original comment by aohelin on 18 May 2011 at 6:07
This will need to be added at a later, but changing status since I'll have to
study how this is handled in other languages first. I don't have enough
experience to decide which of the options would be good, so probably better to
steal a design that has worked elsewhere.
Original comment by aohelin on 21 Dec 2011 at 1:04
Some Scheme FFI systems I prefered:
chibi-scheme:
http://synthcode.com/scheme/chibi/#h1_CFFI
gambit-scheme:
http://www.iro.umontreal.ca/~gambit/doc/gambit-c.html#C_002dinterface
Original comment by zhangm...@google.com on 25 Dec 2011 at 7:10
Original issue reported on code.google.com by
wsxiaoys...@gmail.com
on 18 May 2011 at 2:58The text was updated successfully, but these errors were encountered: