public inbox for guile-gtk@sourceware.org
 help / color / mirror / Atom feed
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>,
	gnucash-devel@gnucash.org
Subject: Re: g-wrap and guile-gnome/gtk
Date: Sun, 12 Nov 2000 13:54:00 -0000	[thread overview]
Message-ID: <87zoj4dfff.fsf@raven.localnet> (raw)
In-Reply-To: <Pine.LNX.4.10.10011121517370.8686-100000@soleil.gnome.org>

Ariel Rios <ariel@arcavia.com> writes:

> If there is a way of having a performance icnrease it would be even
> better ;) I am interested in doing the Corba /ORBit bindings using
> g-wrap or whatever new schema we came up with

Well, I think we can probably separate this into two issues.

  1) What should an API spec look like (say for gtk, glib, opengl,
     curses, etc.).

  2) How should the implementation work?  (i.e. we can potentially
     change that for performance later in any way we like without
     having to change the spec).

Also, after noticing the in, out, inout, arg bits of your latest .defs
proposal, it looks like it's somewhat mirroring other IDLs (of which,
I'm only really passingly familiar with ILU).

One thing I've wondered about for a while now is whether or not it
might make sense to mirror (in scheme forms) the semantics of one of
the IDLs (CORBA being the biggest elephant on the block).

However, on the other side of that fence, I also wonder, whether or
not there might be a legitimate place for a tool (and perhaps g-wrap
should be that tool), that's exclusively focused on providing very
well integrated, efficient, and clear (both in specification and in
execution) bindings for C APIs from guile.  Basically the question
comes down to "Is it possible in this case to server all masters
well?".

Or in more concrete terms, say I were to try to do something very
CORBA-esque with g-wrap's spec.  Would I end up with a tool that was
much more complex, harder to implement and understand, and didn't
really provide any substantial improvments as compared to a tool
that's specifically aimed at just the guile<->C API problem?

I don't really know, and I'd love to hear arguments either way.  To a
substantial extent, I'm not the best person to evaluate this argument,
since I have little or no experience with CORBA, though I've done
plenty of DO/RPC related work.

Thanks
-- 
Rob Browning <rlb@cs.utexas.edu> PGP=E80E0D04F521A094 532B97F5D64E3930

  reply	other threads:[~2000-11-12 13:54 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
2000-11-12 12:14         ` Ariel Rios
2000-11-12 13:54           ` Rob Browning [this message]
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=87zoj4dfff.fsf@raven.localnet \
    --to=rlb@cs.utexas.edu \
    --cc=ariel@arcavia.com \
    --cc=gnucash-devel@gnucash.org \
    --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).