public inbox for guile-gtk@sourceware.org
 help / color / mirror / Atom feed
From: Marius Vollmer <mvo@zagadka.ping.de>
To: Rob Browning <rlb@cs.utexas.edu>
Cc: guile-gtk@sourceware.cygnus.com
Subject: Re: g-wrap and guile-gnome/gtk
Date: Wed, 15 Nov 2000 06:42:00 -0000	[thread overview]
Message-ID: <87aeb171wr.fsf@zagadka.ping.de> (raw)
In-Reply-To: <87lmupf7je.fsf@raven.localnet>

Rob Browning <rlb@cs.utexas.edu> writes:

> Marius Vollmer <mvo@zagadka.ping.de> writes:
> 
> > Build-guile-gtk is still a one-off hack and needs to be redone
> > completely to make it reasonably clean.  This includes the syntax
> > of the defs files themselves, but hopefully we can clean that up
> > in a backward compatible way because they are already defs files
> > out there that are distributed independently from guile-gtk.
> 
> 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.

Hmm, I'm more leaning towards keeping the existing syntax of the defs
files and using g-wrap as a back-end.  The defs file syntax is quite
specialized and not really general but that's actually a feature, I
think.  With a specialized syntax, tzhere is less opportunity for
making mistakes and it's easier for people to add their own things
confidently.  And when a defs file is just Scheme code, people can
> always fall back to the g-wrap features when the need arises.

> One thing we might want to decide is if it's OK that the API spec
> files are just scheme code.

Yes, I think that's the right thing.

> G-wrap handles it that way right now, but that could be changed.
> Allowing arbitrary scheme code does have its advantages since it's
> really easy to do things like conditional inclusion, and other
> things you haven't thought of, and so I tend to favor it, but it
> also has its weaknesses (like making it harder to spot and flag
> syntax errors), so I'd certainly be willing to consider the issue.

Reporting errors is a challange, but I think we can make that work.
Maybe Guile needs to be changed a bit, but this problem should be
quite general.  For example, I have a simulator that uses Scheme as
its description language and I want to report errors in user code in a
nice way.  I found a way to make this work, but it could be improved
with support from Guile itself.

      parent reply	other threads:[~2000-11-15  6: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
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 [this message]

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=87aeb171wr.fsf@zagadka.ping.de \
    --to=mvo@zagadka.ping.de \
    --cc=guile-gtk@sourceware.cygnus.com \
    --cc=rlb@cs.utexas.edu \
    /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).