Re: DSO-style FFI

[Stefan Monnier]

> It seems to me that writing libffi support to Emacs isn't that difficult
> in and of itself.  I have no doubt that I could hack in something
> low-level without too much difficulty.

Could be.  I haven't seen anything concrete (and of course, providing
access to libffi is only one half of the problem, the other half is to
write the binding to lib<foo>, and my impression is that more
people would know how to do that if that part were written in C).

> The problems I see are A) that it would be trivial to use such an
> interface to crash or subvert emacs from elisp,

This is a fundamental property of anything that lets gives access to
"any" library.  DSO or FFI is in the same boat.  IOW, if we really
consider it as too dangerous, then we can't provide anything related to
an FFI or dynamic loading of code.

> and B) that such a binding will allow people to write non-free
> extensions to Emacs in just the way that RMS has specifically stated
> that he would like to avoid.

Presumably we can prevent it by checking (before loading the library)
that the library is compatible with the GPL (following the scheme
designed originally for gcc).

> This isn't to say that something that is not libffi itself could use
> libffi to create something safer.

Don't worry: as long as you want to be able to link libraries written in
languages like C, you can't make it safer.


        Stefan