unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: joakim@verona.se
To: "Aurélien Aptel" <aurelien.aptel+emacs@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: FFI in Emacs
Date: Sat, 25 Aug 2012 20:20:19 +0200	[thread overview]
Message-ID: <m3sjba6dgc.fsf@chopper.vpn.verona.se> (raw)
In-Reply-To: <CA+5B0FPktU=v501Jm11DZUj7DSR-gaWAXTQBRK=ttk4LeSo5tQ@mail.gmail.com> ("Aurélien Aptel"'s message of "Sat, 25 Aug 2012 19:25:05 +0200")

Aurélien Aptel <aurelien.aptel+emacs@gmail.com> writes:

> Hi all,
>
> Joakim, thank you for your work! Did you make any progress since then?
> I was wondering, is anyone else working on this?
>
> The patch mentioned earlier to load dynamically compiled modules is
> not a FFI but it can be useful nonetheless. Why not have both?

I commited the GIR patch to the xwidget emacs repo. You can already do
interesting 
ings with it:

- create gnome objects dynamically(previously only hardcoded objects
were possible)

- dynamically call their methods, with an (early) lisp to C object
marshaller

Anyway, a FFI needs type information from somewhere, and with GIR you
get that from 
e library provider. Therefore GIR is IMHO more interesting than  plain
FFI. You can also provide GIR typelib wrappers that would benefit all
GIR implementations, not only the xwgir one in the xwidget branch.

Well maybe that wasnt so clear. Hear is a concrete example:
- you want to call the libmagic file info functions
- wrap libmagic in a tiny wrapper that provides gir typeinfo
- now you can call these libmagic functions from Emacs, and the xwgir
functions can figure out how to convert elisp data to the data needed by
the library.
- but now your friends using gir from python etc can also benefit your
work!

I think this is the right aproach, but it does not exclude a plain FFI
implementation.

--
Joakim Verona



  reply	other threads:[~2012-08-25 18:20 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-27 23:36 FFI in Emacs Aurélien Aptel
2012-06-27 23:47 ` Glenn Morris
2012-06-28  0:03   ` John Wiegley
2012-06-28  2:12     ` Glenn Morris
2012-06-28  3:43       ` Stefan Monnier
2012-06-28  4:51         ` John Wiegley
2012-06-28 15:27           ` Nix
2012-07-11  5:24         ` John Wiegley
2012-07-11  5:53           ` Helmut Eller
2012-07-11  6:43           ` Michael Albinus
2012-07-11 14:04             ` Burton Samograd
2012-07-11 14:07               ` Burton Samograd
2012-07-11  7:14           ` Stephen J. Turnbull
2012-07-11  7:44             ` Michael Albinus
2012-07-11 16:11             ` Eli Zaretskii
2012-07-11 17:08               ` Samuel Bronson
2012-07-11 17:49                 ` Eli Zaretskii
2012-07-11 18:23                   ` Stephen J. Turnbull
2012-07-11 18:30                     ` Eli Zaretskii
2012-07-11 16:05           ` Eli Zaretskii
2012-07-12 13:55           ` Stefan Monnier
2012-07-12 17:01             ` Samuel Bronson
2012-07-12 18:54             ` John Wiegley
2012-07-12 23:19             ` Sam Steingold
2012-07-13  2:20               ` Óscar Fuentes
2012-07-13  3:21                 ` Stephen J. Turnbull
2012-06-28  6:20       ` joakim
2012-07-11  9:40         ` joakim
2012-08-25 17:25           ` Aurélien Aptel
2012-08-25 18:20             ` joakim [this message]
2012-08-26  8:57               ` Ivan Kanis
2012-08-26 13:11                 ` joakim
2013-03-12 19:16             ` Aurélien Aptel
2013-03-12 21:50               ` Eli Zaretskii
2013-03-12 22:40                 ` Pascal J. Bourguignon
2013-03-13  7:41                   ` Andreas Schwab
2013-03-12 22:53                 ` Aurélien Aptel
2013-03-13  0:31                   ` Daniel Colascione
2013-03-13  3:55                   ` Eli Zaretskii
2013-03-22 19:44               ` BT Templeton
2013-03-23  1:51                 ` Leo Liu
2013-03-23  2:04                   ` Noah Lavine
2013-03-23 16:07                 ` Stefan Monnier
2013-03-23 18:33                   ` Yagnesh Raghava Yakkala

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3sjba6dgc.fsf@chopper.vpn.verona.se \
    --to=joakim@verona.se \
    --cc=aurelien.aptel+emacs@gmail.com \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).