From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: FFI support for disjoint types
Date: Sat, 20 Nov 2010 22:59:30 +0100 [thread overview]
Message-ID: <m3r5efzmf1.fsf@unquote.localdomain> (raw)
In-Reply-To: <87bp5vx1zq.fsf@gnu.org> ("Ludovic Courtès"'s message of "Thu, 11 Nov 2010 17:24:09 +0100")
On Thu 11 Nov 2010 17:24, ludo@gnu.org (Ludovic Courtès) writes:
> (define-wrapped-pointer-type class?
> wrap-class unwrap-class print-class)
Looks great! Would be a great addition to system foreign.
> (with-syntax ((type-name (datum->syntax #'pred (gensym)))
> (%wrap (datum->syntax #'wrap (gensym))))
> #'(begin
> (define-record-type type-name
> (%wrap pointer)
> pred
> (pointer unwrap))
You wouldn't need to do the gensym dance if we fixed Andreas' bug
(https://savannah.gnu.org/bugs/?31472), I don't think...
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2010-11-20 21:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-11 16:24 FFI support for disjoint types Ludovic Courtès
2010-11-20 21:59 ` Andy Wingo [this message]
2010-11-21 22:36 ` Ludovic Courtès
2011-01-30 22:30 ` Ludovic Courtès
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=m3r5efzmf1.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--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).