Comment on Design Issues for Foreign Function Interfaces (2004)Comments−metagameOP4yPrevious summary of this article, from a thread with otherwise no activity and with an author that no longer posts on HN, said more elegantly than I could dream of saying: https://news.ycombinator.com/item?id=1047559−rurban4yThe author is still active, here. The author is not really a lisper, just a normal polyglot, who happens to like lisp.Beware that the standard libffi was written for Visual Basic. Which has one of the easiest FFI's. Did I write that? Forgot.−metagameOP4yI was talking about mahmud, actually, the user who summed up your article.Thanks for the article!
Comments
Previous summary of this article, from a thread with otherwise no activity and with an author that no longer posts on HN, said more elegantly than I could dream of saying: https://news.ycombinator.com/item?id=1047559
The author is still active, here. The author is not really a lisper, just a normal polyglot, who happens to like lisp.
Beware that the standard libffi was written for Visual Basic. Which has one of the easiest FFI's. Did I write that? Forgot.
I was talking about mahmud, actually, the user who summed up your article.
Thanks for the article!