From: Michael Livshin <mlivshin@bigfoot.com>
To: Rob Browning <rlb@cs.utexas.edu>
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 09:42:00 -0000 [thread overview]
Message-ID: <s3snoxw0sp.fsf@bigfoot.com> (raw)
In-Reply-To: <87lmupf7je.fsf@raven.localnet>
Rob Browning <rlb@cs.utexas.edu> writes:
> Well, since everything's just scheme forms, and since the .defs files
> aren't even allowed to be general scheme syntax, this should be easy.
> We could probably even just write a translator script that was nothing
> more than a set of guile macros that rewrote and "displayed" their
> contents as g-wrap specs.
note that the .defs files are apparently supposed to become the
standard way to specify the bindable interface of the various
Gnome-affiliated C libraries. i.e. they are not just for Guile
anymore. so .defs -> .gwp translation approach seems like a very
sensible idea to me, whatever way you happen to implement it.
--
All ITS machines now have hardware for a new machine instruction --
CIZ
Clear If Zero.
Please update your programs.
next prev parent reply other threads:[~2000-11-12 9:42 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 [this message]
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
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=s3snoxw0sp.fsf@bigfoot.com \
--to=mlivshin@bigfoot.com \
--cc=guile-gtk@sourceware.cygnus.com \
--cc=jarios@usa.net \
--cc=mvo@zagadka.ping.de \
--cc=rlb@cs.utexas.edu \
--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).