[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ELisp?
From: |
joakim |
Subject: |
Re: ELisp? |
Date: |
Sat, 12 Nov 2011 16:00:11 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.0.91 (gnu/linux) |
Ken Raeburn <address@hidden> writes:
> On Nov 11, 2011, at 04:46, address@hidden wrote:
>> Where is your public repository? I would be interested to have a look.
>
> Try git://raeburn.scripts.mit.edu/guile-emacs.git. But it's about two years
> old. :-(
> One of these days....
>
>> As a concrete example, one could use guiles libffi integration to offer
>> the same feature to Emacs. I could personally use it in my xwidgets
>> emacs branch to call dynamically into webkit rather than having to make
>> a c wrapper for each and every function.
>
> Hmm... this touches on a political issue I'd been avoiding thinking about.
> Namely, adding Guile to Emacs, with Guile's new FFI support, would make
> dynamically loading new executable code into Emacs easy, technically,
> including non-GPL code written specifically to extend Emacs. There's been a
> lot of resistance to that in the past. See for example
> http://lists.gnu.org/archive/html/emacs-devel/2003-07/msg00403.html .
Yes, this seems to have been resolved if the GCC scheme for identifying
GPL libraries is used. Basically GPL libraries expose a symbol declaring GPL
compliance.
>
> On the technical side (ignoring the political/legal angles), I wonder if it
> would be quicker to drop FFI support into Emacs directly, using an interface
> based on the Guile one, and use that for now, until the Emacs+Guile work is
> far enough along to merge. I suspect your xwidgets code would be ready for
> integration much sooner than that. :-)
Quicker, yes, but less interesting. I suppose I'm looking for an excuse
to do this :)
> Ken
--
Joakim Verona