From: Rob Browning <rlb@cs.utexas.edu>
To: Ariel Rios <ariel@arcavia.com>
Cc: Marius Vollmer <mvo@zagadka.ping.de>, Ariel Rios <jarios@usa.net>,
guile-gtk@sourceware.cygnus.com,
Miroslav silovic <silovic@zesoi.fer.hr>
Subject: Re: g-wrap and guile-gnome/gtk
Date: Sun, 12 Nov 2000 12:09:00 -0000 [thread overview]
Message-ID: <87hf5ddkbf.fsf@raven.localnet> (raw)
In-Reply-To: <Pine.LNX.4.10.10011121404010.8430-100000@soleil.gnome.org>
Ariel Rios <ariel@arcavia.com> writes:
> > Well, I want to make it clear that I'm not hung up on g-wrap as it is.
> > If we need to change things, or even if we decide that we need to work
> > on some other common effort, it sounds to me like a joint solution
> > would benefit everyone.
>
> I am especially interested in knowing how fast do libraries
> binded using g-wrap is.
Well, since Marius told me that guile-{gtk,gnome} is basically using
an earlier version of g-wrap's guts, I'd guess, since I don't think
I've really changed anything performance related, that the performance
should be roughly equivalent.
> We can even have some macros to deal with the defs file if necessary...
Right.
--
Rob Browning <rlb@cs.utexas.edu> PGP=E80E0D04F521A094 532B97F5D64E3930
next prev parent reply other threads:[~2000-11-12 12:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-11 9:30 Fwd: [g-wrap and guile-gnome/gtk] Ariel Rios
2000-11-11 12:11 ` g-wrap and guile-gnome/gtk Marius Vollmer
2000-11-12 9:02 ` Rob Browning
2000-11-12 9:42 ` Michael Livshin
2000-11-12 11:07 ` Ariel Rios
2000-11-12 12:09 ` Rob Browning [this message]
2000-11-12 12:14 ` Ariel Rios
2000-11-12 13:54 ` Rob Browning
2000-11-15 6:42 ` Marius Vollmer
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=87hf5ddkbf.fsf@raven.localnet \
--to=rlb@cs.utexas.edu \
--cc=ariel@arcavia.com \
--cc=guile-gtk@sourceware.cygnus.com \
--cc=jarios@usa.net \
--cc=mvo@zagadka.ping.de \
--cc=silovic@zesoi.fer.hr \
/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).