From: Marius Vollmer <mvo@zagadka.ping.de>
To: Mark Seaborn <mseaborn@argonet.co.uk>
Cc: guile-gtk@sourceware.cygnus.com
Subject: Re: Making gdk-event-area work
Date: Sun, 10 Sep 2000 07:40:00 -0000 [thread overview]
Message-ID: <87og1w2ud2.fsf@zagadka.ping.de> (raw)
In-Reply-To: <87its930mo.fsf@argbg34.argonet.co.uk>
Mark Seaborn <mseaborn@argonet.co.uk> writes:
> 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.
If that a static type system is intended to be used with Scheme, then
it is fundamentally broken. Pairs are used in a non-list manner all
the time, for association lists, for binary trees, etc.
> 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.
I think this fear is unfounded. There is no way that such a type
system could be used extensively with Scheme.
> 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.
Yes, that's a good point. We might want to change to using Goops, for
example, and have proper types for 2D-points and stuff. What about
names like
gdk-point-x car
gdk-point-y cdr
gdk-rect-pos car
gdk-rect-size cdr
gdk-rect-x caar
gdk-rect-y cdar
gdk-rect-w cadr
gdk-rect-h cddr
prev parent reply other threads:[~2000-09-10 7:40 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
2000-09-10 7:40 ` Marius Vollmer [this message]
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=87og1w2ud2.fsf@zagadka.ping.de \
--to=mvo@zagadka.ping.de \
--cc=guile-gtk@sourceware.cygnus.com \
--cc=mseaborn@argonet.co.uk \
/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).