public inbox for guile-gtk@sourceware.org
 help / color / mirror / Atom feed
From: Rob Browning <rlb@defaultvalue.org>
To: Andreas Rottmann <a.rottmann@gmx.at>
Cc: guile-gtk@sources.redhat.com, guile-gtk-general@gnu.org
Subject: Re: guile-gobject/g-wrap status update
Date: Mon, 06 Oct 2003 15:34:00 -0000	[thread overview]
Message-ID: <87zngez8fh.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <87y8vy7tey.fsf@alice.rotty.yi.org> (Andreas Rottmann's message of "Mon, 06 Oct 2003 17:13:54 +0200")

Andreas Rottmann <a.rottmann@gmx.at> writes:

> [BTW: There seem to be two guile-gtk mailing lists ATM - I guess
> people should migrate to the one at GNU...]
>
> I'm ATM working at implementing "glueless" wrapping for g-wrap,
> i.e. instead of using a dedicated C wrapper for each wrapped function
> creating an applicable smob that invokes a general marshaller which in
> turn calls the C function via libffi.

Interesting.  A couple of questions come to mind.  First, how portable
is libffi?  Will it cover all the existing architectures?  Also, do we
know what the overhead's likely to be?  I suppose the performance
argument could go either way when comparing to the existing approach
since the existing one-function-per-wrapper approach may well have
poorer interactions with the memory hierarchy.  In any case, I do want
to preserve the ability for people who want to, to be able to have
close to minimal ffcall overhead using g-wrap.  When calling from
interpreted languages, you may have a lot more leeway before you
noticably affect performance, but in the long run, I'm hoping guile
will also provide some form of compilation.

On a related front, I've decided to just use CVS at savannah, so I
should be setting that up over the next week (plus or minus -- I have
family coming to visit).  It also probably makes sense to have a place
where those interested can discuss "what should happen next" with
g-wrap.  I'm happy to have that discussion on an existing list if that
would be appropriate, or to create a new one.  I've had some ideas I'd
like to discuss, and to compare and contrast (to the extent that they
overlap) with the above.

Thanks

-- 
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592  F9A0 25C8 D377 8C7E 73A4

  reply	other threads:[~2003-10-06 15:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-06 15:11 Andreas Rottmann
2003-10-06 15:34 ` Rob Browning [this message]
2003-10-06 22:59   ` Andreas Rottmann

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=87zngez8fh.fsf@raven.i.defaultvalue.org \
    --to=rlb@defaultvalue.org \
    --cc=a.rottmann@gmx.at \
    --cc=guile-gtk-general@gnu.org \
    --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).