From: Kevin Ryde <user42@zip.com.au>
To: Andreas Rottmann <a.rottmann@gmx.at>
Cc: guile-gtk@sources.redhat.com, Ariel Rios <ariel@gnu.org>,
Rob Browning <rlb@defaultvalue.org>
Subject: Re: (gnome gtk) et al
Date: Fri, 23 May 2003 22:00:00 -0000 [thread overview]
Message-ID: <87llwxmiig.fsf@zip.com.au> (raw)
In-Reply-To: <873cj99z27.fsf@alice.rotty.yi.org>
Andreas Rottmann <a.rottmann@gmx.at> writes:
>
> (let ((error '(#f #f #f)))
I'd thought it might be worth having GError as a distinct type, for
stricter checking etc.
> (if (not (g-io-channel-new-file "/ENOENT" "r" error))
Calls would no doubt accept #f to mean NULL at the C level.
> (if (= (g-file-error-quark) (car error))
As a separate type it'd be "g-error-code" or whatever instead of car.
More long winded, but would maximize clarity.
> (format #t "file error (~S) opening /ENOENT: ~S\n"
Speaking of formatting, I suppose having g-set-error and friends take
printf style format strings would most closely match native glib. But
it'd probably require a more or less complete re-implementation of
printf taking scm arguments. Maybe someone has such a thing kicking
around already.
next prev parent reply other threads:[~2003-05-23 22:00 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030407144511.GA1489@lark>
2003-04-07 19:57 ` Ariel Rios
2003-04-07 20:15 ` Andreas Rottmann
2003-04-08 10:34 ` Marius Vollmer
2003-04-08 14:56 ` Stan Pinte
2003-04-08 20:03 ` Andreas Rottmann
2003-04-08 21:33 ` David Pirotte
2003-04-11 4:48 ` Steve Tell
2003-04-11 10:00 ` Andreas Rottmann
2003-04-09 15:24 ` Stan Pinte
2003-04-10 17:05 ` Andreas Rottmann
2003-04-10 17:10 ` David Pirotte
2003-05-06 6:52 ` Stan Pinte
2003-05-06 15:33 ` Marius Vollmer
2003-05-06 15:45 ` Stan Pinte
2003-05-07 13:07 ` Stan Pinte
2003-05-07 14:02 ` Stan Pinte
2003-05-07 14:10 ` Marius Vollmer
2003-05-07 14:38 ` Stan Pinte
2003-05-07 15:17 ` Stan Pinte
2003-05-07 18:16 ` Marius Vollmer
2003-05-08 11:43 ` Stan Pinte
2003-05-12 14:18 ` Stan Pinte
[not found] ` <1052750737.26632.4.camel@tosca.elektra.com.mx>
2003-05-12 16:48 ` Stan Pinte
2003-05-14 9:17 ` Andy Wingo
2003-05-16 14:26 ` Andreas Rottmann
2003-05-20 20:08 ` Andreas Rottmann
2003-05-23 22:00 ` Kevin Ryde [this message]
2003-05-26 13:04 ` Andreas Rottmann
2003-06-23 14:14 ` 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=87llwxmiig.fsf@zip.com.au \
--to=user42@zip.com.au \
--cc=a.rottmann@gmx.at \
--cc=ariel@gnu.org \
--cc=guile-gtk@sources.redhat.com \
--cc=rlb@defaultvalue.org \
/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).