From: Mark Seaborn <mseaborn@argonet.co.uk>
To: guile-gtk@sourceware.cygnus.com
Subject: Re: Making gdk-event-area work
Date: Wed, 06 Sep 2000 13:32:00 -0000 [thread overview]
Message-ID: <87its930mo.fsf@argbg34.argonet.co.uk> (raw)
In-Reply-To: <87zolm66bm.fsf@zagadka.ping.de>
Marius Vollmer <mvo@zagadka.ping.de> writes:
> Mark Seaborn <mseaborn@argonet.co.uk> writes:
>
> > Here's a patch to make gdk-event-area work.
>
> Thanks! I have applied it.
Thanks.
[snip]
> > (Incidentally, converting rectangles to pairs of pairs isn't very
> > nice. Are there any plans to use a more abstract data type?)
>
> There are no plans, but also no big objections to change it, I think.
> What do you think is not nice about the current way?
Pairs are usually used to represent lists, and a lot of static type
systems only let you store lists in the cdr of a pair. It's true
there are times when improper lists are useful, but I don't like being
gratuitously incompatible with other type systems. I might want my
Scheme code to interoperate with them later.
It's also not very readable using `car', `cdr', etc. for this. I
suggest providing some accessor functions, `bbox-min-x', `bbox-min-y',
etc., and saying the representation might change in a later version.
> You could always build an abstraction on top of it.
I'd end up building abstractions on top of every library I use. :-)
--
Mark Seaborn
- mseaborn@bigfoot.com - http://members.xoom.com/mseaborn/ -
``We are quite lucky really this year because Christmas
falls on Christmas day'' -- Bobby Gould
next prev parent reply other threads:[~2000-09-06 13:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-04 3:37 Mark Seaborn
2000-09-05 11:41 ` Marius Vollmer
2000-09-06 13:32 ` Mark Seaborn [this message]
2000-09-10 7:40 ` Marius Vollmer
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=87its930mo.fsf@argbg34.argonet.co.uk \
--to=mseaborn@argonet.co.uk \
--cc=guile-gtk@sourceware.cygnus.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).