From: Kevin Ryde <user42@zip.com.au>
To: guile-gtk@sources.redhat.com
Subject: Re: texinfo documentation
Date: Thu, 29 May 2003 23:37:00 -0000 [thread overview]
Message-ID: <877k89nx2w.fsf@zip.com.au> (raw)
In-Reply-To: <m3addabfnx.fsf@lumo.pacujo.net> (Marko Rauhamaa's message of "25 May 2003 19:33:22 -0700")
Marko Rauhamaa <marko@pacujo.net> writes:
>
> guile-gtk: (gdk-rectangle-intersect rect1 rect2) => rect or #f
>
> guile-gtk: (gdk-rectangle-union rect1 rect2) => rect
These two look sensible, and will suit typical rectangle arithmetic.
> guile-gtk: (gdk-string-to-compound str) => (string or #f
> encoding
> format)
Hmm. (bool encoding format string) would better match the C function,
in particular enough not to need to be described as a special case.
(Or only with a general note somewhere that gint returns that should
be understdood as gboolean are treated that way by guile-gtk.)
Obviously there's no need to be absolutely slavish, but every
difference is an inconsistency and a likely source of annoyance for
programmers.
next prev parent reply other threads:[~2003-05-29 23:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-12 1:21 Kevin Ryde
2003-05-12 1:52 ` Marko Rauhamaa
2003-05-23 22:01 ` Kevin Ryde
2003-05-23 23:36 ` Marko Rauhamaa
2003-05-23 23:57 ` Kevin Ryde
2003-05-24 0:05 ` Marko Rauhamaa
2003-05-24 2:19 ` Kevin Ryde
[not found] ` <m3llwwdhjf.fsf@lumo.pacujo.net>
2003-05-25 22:48 ` Kevin Ryde
2003-05-25 23:28 ` Marko Rauhamaa
2003-05-26 0:06 ` Kevin Ryde
2003-05-26 2:42 ` Marko Rauhamaa
2003-05-29 23:37 ` Kevin Ryde [this message]
2003-05-30 1:06 ` Marko Rauhamaa
2003-06-13 22:05 ` gdk-string-to-compound (was: texinfo documentation) Kevin Ryde
2003-07-07 22:30 ` gdk-string-to-compound Kevin Ryde
2003-05-29 23:43 ` texinfo documentation Kevin Ryde
2003-06-01 4:31 ` Marko Rauhamaa
2003-06-02 23:51 ` gdk-window-get-origin (was: texinfo documentation) Kevin Ryde
2003-07-07 22:29 ` gdk-window-get-geometry " Kevin Ryde
2003-05-26 0:07 ` gdk-rectangle-new " Kevin Ryde
2003-05-26 1:20 ` Marko Rauhamaa
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=877k89nx2w.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).