From: Mark H Weaver <mhw@netris.org>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: Should we add scm_to_pointer, or just use SCM_POINTER_VALUE?
Date: Thu, 02 Feb 2012 17:10:20 -0500 [thread overview]
Message-ID: <8739asc2er.fsf@netris.org> (raw)
In-Reply-To: <878vkluepk.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Thu, 02 Feb 2012 22:07:19 +0100")
ludo@gnu.org (Ludovic Courtès) writes:
> Adding ‘scm_to_pointer’ is nice, but ‘SCM_POINTER_VALUE’ is also meant
> to be public (and should be documented.)
Okay.
> I’m curious: why would one want to use the FFI’s C API?
Apparently he wanted to create a C callback to a Scheme procedure (using
procedure->pointer), but wanted to do the rest from C.
Mark
prev parent reply other threads:[~2012-02-02 22:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 6:20 Should we add scm_to_pointer, or just use SCM_POINTER_VALUE? Mark H Weaver
2012-02-01 10:59 ` Andy Wingo
2012-02-02 21:07 ` Ludovic Courtès
2012-02-02 21:49 ` Andy Wingo
2012-02-02 22:10 ` Mark H Weaver [this message]
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=8739asc2er.fsf@netris.org \
--to=mhw@netris.org \
--cc=guile-devel@gnu.org \
--cc=ludo@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.
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).