public inbox for guile-gtk@sourceware.org
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: guile-gtk@sources.redhat.com
Subject: GError
Date: Sat, 24 May 2003 11:49:00 -0000	[thread overview]
Message-ID: <20030524113300.GB24132@lark> (raw)

Hi Andreas and Kevin,

Sorry I can't reply directly to the earlier emails, I was on holiday and
not on the list at that point.

I'd first like to thank you all for the interest in the GTK2 branch of
things, especially as expressed by code. That's great! More about that
in my next email.

With regards to GError, I think the solution you propose is too much
like C programming. Wouldn't it be nicer if, instead of forcing the
programmer to know about GErrors, if we simply threw an exception if the
GError is set? That would seem to me to be the more sensible
alternative. We can make the load-defs code recognize the presence of a
GError in the last argument position (as it always is) and then... Hmm,
it's a bit of a PITA in that the desired scheme function has fewer
arguments than the C function. I think that to support this fully, we
would have to extend g-wrap. What do you think about this idea?

And along the extending-g-wrap lines, I sent a mail to Rob Browning
asking him to accept the newer gw-standard-spec.scm into the distro, but
have not received a reply as of yet. Perhaps we need to try a bit
harder.

Anyway, do let me know what you think about all of this.

regards,

wingo.

             reply	other threads:[~2003-05-24 11:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-24 11:49 Andy Wingo [this message]
2003-05-25 23:16 ` GError Kevin Ryde
2003-06-02  6:51   ` GError Andy Wingo
2003-06-02  9:20     ` GError Andreas Rottmann
2003-06-06 22:59     ` GError Kevin Ryde
2003-07-22 14:22       ` GError Andy Wingo

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=20030524113300.GB24132@lark \
    --to=wingo@pobox.com \
    --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).