From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: Andy Wingo <wingo@pobox.com>,
guile-devel@gnu.org, Greg Troxel <gdt@ir.bbn.com>
Subject: Re: Dynamic FFI vs Static FFI (was Re: About Guile crypto support)
Date: Tue, 12 Feb 2013 22:49:33 +0100 [thread overview]
Message-ID: <87txphnqxe.fsf@gnu.org> (raw)
In-Reply-To: <87halhxuey.fsf@tines.lan> (Mark H. Weaver's message of "Tue, 12 Feb 2013 13:24:05 -0500")
Mark H Weaver <mhw@netris.org> skribis:
> ludo@gnu.org (Ludovic Courtès) writes:
>
>> Mark H Weaver <mhw@netris.org> skribis:
>>
>>> At some point, it might make sense to create a more static FFI that
>>> works more like a C compiler does, splitting the job into compile-time
>>> and run-time phases. This static FFI would be strictly less powerful
>>> than the dynamic FFI, in a similar sense to how syntactic record APIs
>>> are less powerful than procedural ones. However, the static FFI would
>>> be sufficient in most cases, and would have some advantages.
>>
>> In my mind the “static FFI” is the C API, and the dynamic FFI is
>> (system foreign).
>>
>> To me, the main advantage of the latter is its simplicity of use and
>> deployment.
>
> Okay, but here I'm using "Static FFI" to mean something very different
> than the C API: I'm talking about a pure scheme-based API that would be
> quite similar to the API our current dynamic FFI, except that a lot of
> the work would be done at compilation time (probably during macro
> expansion).
Ah, OK, sorry for the confusion!
Ludo’.
next prev parent reply other threads:[~2013-02-12 21:49 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-03 12:55 About Guile crypto support Nala Ginrut
2013-02-03 15:37 ` Thien-Thi Nguyen
2013-02-04 1:14 ` Daniel Hartwig
2013-02-04 3:12 ` Nala Ginrut
2013-02-04 3:35 ` Daniel Hartwig
2013-02-04 4:15 ` Nala Ginrut
2013-02-04 23:03 ` Ludovic Courtès
2013-02-05 2:43 ` Nala Ginrut
2013-02-05 2:57 ` Noah Lavine
2013-02-06 13:58 ` Nala Ginrut
2013-02-05 15:48 ` Ludovic Courtès
2013-02-06 4:18 ` Daniel Hartwig
2013-02-06 4:28 ` Daniel Hartwig
2013-02-08 16:21 ` Ludovic Courtès
2013-02-09 1:37 ` Daniel Hartwig
2013-02-09 15:12 ` Ludovic Courtès
2013-02-09 17:02 ` Andy Wingo
2013-02-09 17:50 ` Mark H Weaver
2013-02-09 20:44 ` Noah Lavine
2013-02-09 21:53 ` Ludovic Courtès
2013-02-11 8:20 ` Andy Wingo
2013-02-11 9:15 ` Thien-Thi Nguyen
2013-02-11 10:46 ` Mike Gran
2013-02-11 13:14 ` Ludovic Courtès
2013-02-11 9:51 ` Nala Ginrut
2013-02-11 15:23 ` Greg Troxel
2013-02-12 1:12 ` Daniel Hartwig
2013-02-12 4:20 ` Nala Ginrut
2013-02-12 5:21 ` Daniel Hartwig
2013-02-12 7:40 ` Dynamic FFI vs Static FFI (was Re: About Guile crypto support) Mark H Weaver
2013-02-12 13:52 ` Ludovic Courtès
2013-02-12 18:24 ` Mark H Weaver
2013-02-12 21:49 ` Ludovic Courtès [this message]
2013-02-14 7:21 ` William ML Leslie
2013-02-15 13:34 ` Nala Ginrut
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87txphnqxe.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=gdt@ir.bbn.com \
--cc=guile-devel@gnu.org \
--cc=mhw@netris.org \
--cc=wingo@pobox.com \
/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.
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).