From: Kevin Ryde <user42@zip.com.au>
To: guile-gtk@sources.redhat.com
Subject: Re: GError
Date: Fri, 06 Jun 2003 22:59:00 -0000 [thread overview]
Message-ID: <87smqmzuc3.fsf@zip.com.au> (raw)
In-Reply-To: <20030526172355.GA6014@lark>
Andy Wingo <wingo@pobox.com> writes:
>
> A quick search through gnome/defs shows the following occurences of GError:
You might be right, not many look terribly interesting things to
continue normal operations after.
If GError is uniformly the last parameter to the functions then if
initially omitted from the scheme procedures it could always be added
back later.
Or plan to accept only #f there for now, meaning disable the exception
throw.
next prev parent reply other threads:[~2003-06-06 22:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-24 11:49 GError Andy Wingo
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 ` Kevin Ryde [this message]
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=87smqmzuc3.fsf@zip.com.au \
--to=user42@zip.com.au \
--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).