From: "Lennart Borgman" <lennart.borgman.073@student.lu.se>
Cc: hunterd42@comcast.net, kobayays@otsukakj.co.jp, emacs-devel@gnu.org
Subject: Re: Hourglass only for X-windows?
Date: Sat, 12 Mar 2005 22:40:34 +0100 [thread overview]
Message-ID: <002b01c5274c$29a31ac0$0200a8c0@sedrcw11488> (raw)
In-Reply-To: 01c526ea$Blat.v2.4$9b90fba0@zahav.net.il
----- Original Message -----
From: "Eli Zaretskii" <eliz@gnu.org>
> > There is something I do not understand in your argument. How about
> > HAVE_MOUSE, HAVE_SOUND?
>
> These are configure-time definitions, unlike HAVE_HOURGLASS. They
> test the basic capabilities of the underlying platform, while
> HAVE_HOURGLASS tells something about Emacs support of the feature, not
> about its availability on the platform.
I see. Then it would maybe be better to call it HOURGLASS_SUPPORTED.
> Jason responded with a clear and eloquent explanation, and I can only
> say I agree with him 100%.
You both did and that made me wonder how we could come to so different
conclusions. It seems to me like you say (as above) that the constants are
telling something about the platform in itself. That is one use of them, a
technical use.
Another use of constants could be telling if a feature is support. Then the
constant is of course still platform dependend (but on next abstraction
level so to say). That is what I propose.
However Stefan just suggested to use stubs instead to make the code more
readable. That is what I also suggested, but I thought most people here
would like the HOURGLASS_SUPPORTED better at the moment since it is perhaps
quicker to implement right now. But that assumption might just be a mistake
by me?
prev parent reply other threads:[~2005-03-12 21:40 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-27 17:57 Hourglass only for X-windows? Lennart Borgman
2005-02-27 20:29 ` Eli Zaretskii
2005-02-28 0:20 ` Lennart Borgman
2005-02-28 4:38 ` Eli Zaretskii
2005-02-28 15:57 ` Lennart Borgman
2005-02-28 23:05 ` Eli Zaretskii
2005-03-01 0:17 ` Lennart Borgman
2005-03-10 23:33 ` Lennart Borgman
2005-03-11 13:28 ` Eli Zaretskii
2005-03-11 13:44 ` Jason Rumney
2005-03-11 15:51 ` Eli Zaretskii
2005-03-11 16:03 ` Lennart Borgman
2005-03-11 16:15 ` Eli Zaretskii
2005-03-11 16:43 ` Lennart Borgman
2005-03-11 17:25 ` Jan D.
2005-03-11 18:42 ` Lennart Borgman
2005-03-11 20:51 ` Eli Zaretskii
2005-03-12 1:03 ` Lennart Borgman
2005-03-12 2:11 ` Jason Rumney
2005-03-12 9:37 ` Lennart Borgman
2005-03-12 11:43 ` Jan D.
2005-03-12 13:41 ` Stefan Monnier
2005-03-12 15:41 ` Jason Rumney
2005-03-13 3:50 ` David Hunter
2005-03-14 11:28 ` YAMAMOTO Mitsuharu
2005-03-13 15:29 ` Richard Stallman
2005-03-12 10:01 ` Eli Zaretskii
2005-03-12 21:40 ` Lennart Borgman [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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='002b01c5274c$29a31ac0$0200a8c0@sedrcw11488' \
--to=lennart.borgman.073@student.lu.se \
--cc=emacs-devel@gnu.org \
--cc=hunterd42@comcast.net \
--cc=kobayays@otsukakj.co.jp \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).