public inbox for guile-gtk@sourceware.org
 help / color / mirror / Atom feed
From: Kevin Ryde <user42@zip.com.au>
To: guile-gtk@sources.redhat.com
Subject: Re: Compiling guile-gobject experiences
Date: Fri, 19 Sep 2003 00:19:00 -0000	[thread overview]
Message-ID: <87d6dx3a14.fsf@zip.com.au> (raw)
In-Reply-To: <87pti4n9jq.fsf@zagadka.ping.de>

Marius Vollmer <mvo@zagadka.de> writes:
>
> There are already libraries out there for this.  I think "libffi" and
> "libffcall" would be the search terms.

Looks good.  A wrapped function might be able to be an apply-able smob
with a pointer to the C func and some bits and bytes saying what its
arguments are like.

  reply	other threads:[~2003-09-19  0:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-02 17:17 Andreas Rottmann
2003-08-04 16:25 ` Andy Wingo
2003-08-04 16:58   ` Andreas Rottmann
2003-08-07  8:09     ` Andy Wingo
2003-08-07 11:18       ` Andreas Rottmann
2003-09-12 23:02   ` Kevin Ryde
2003-09-13 12:43     ` Marius Vollmer
2003-09-19  0:19       ` Kevin Ryde [this message]
2003-09-14 19:47     ` Andreas Rottmann
2003-09-15 17:59       ` GOOPS slowness [was: Compiling guile-gobject experiences] Andreas Rottmann
2003-09-19  0:18       ` Compiling guile-gobject experiences Kevin Ryde

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

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

  git send-email \
    --in-reply-to=87d6dx3a14.fsf@zip.com.au \
    --to=user42@zip.com.au \
    --cc=guile-gtk@sources.redhat.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).