From: storm@cua.dk (Kim F. Storm)
Cc: Eli Zaretskii <eliz@is.elta.co.il>,
jasonr@btinternet.com, andrewi@gnu.org, jay_finger@hotmail.com,
emacs-devel@gnu.org
Subject: Re: [jay_finger@hotmail.com: Two problems in Emacs-21.2.91 on Windows]
Date: 24 Oct 2002 11:35:07 +0200 [thread overview]
Message-ID: <5xof9kp4c4.fsf@kfs2.cua.dk> (raw)
In-Reply-To: <20021024095449.AB61.LEKTU@terra.es>
Juanma Barranquero <lektu@terra.es> writes:
> On Thu, 24 Oct 2002 09:13:26 +0200 (IST), Eli Zaretskii <eliz@is.elta.co.il> wrote:
>
> > We could use some header that is common to all platforms, with a suitable
> > ifdef if needed.
>
> I agree, if:
>
> - There's a suitable .h file (I mean, not lisp.h or any non-UI oriented
> .h file, which would be ugly).
dispextern.h seems like a good choice. It actually uses XColor in a prototype...
I suggest adding the following near the top of the file:
#ifdef HAVE_X_WINDOWS
#include <X11/Xlib.h>
#ifdef USE_X_TOOLKIT
#include <X11/Intrinsic.h>
#endif /* USE_X_TOOLKIT */
+ #else /* !HAVE_X_WINDOWS */
+
+ /* X-related stuff used by non-X gui code. */
+
+ typedef struct {
+ unsigned long pixel;
+ unsigned short red, green, blue;
+ char flags;
+ char pad;
+ } XColor;
+
#endif /* HAVE_X_WINDOWS */
>
> - It's already (directly or indirectly) included in the relevant .c
> files.
>
dispextern.h is included by all files using XColor!
> But I'm *really* not arguing. If you know of such a .h file, I'm not
> opposing to do it your way if people feels is better.
Avoiding [verbatim] duplication of code or defs always make me feel better :-)
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2002-10-24 9:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-23 13:37 [jay_finger@hotmail.com: Two problems in Emacs-21.2.91 on Windows] jasonr
2002-10-23 13:43 ` Juanma Barranquero
2002-10-23 16:41 ` Eli Zaretskii
2002-10-24 6:42 ` Juanma Barranquero
2002-10-24 7:13 ` Eli Zaretskii
2002-10-24 8:06 ` Juanma Barranquero
2002-10-24 9:35 ` Kim F. Storm [this message]
2002-10-24 8:40 ` Juanma Barranquero
2002-10-24 17:28 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2002-10-24 8:25 jasonr
2002-10-23 13:44 jasonr
2002-10-23 7:10 Richard Stallman
2002-10-23 12:06 ` Juanma Barranquero
2002-10-23 16:19 ` Andrew Choi
2002-10-23 16:47 ` Juanma Barranquero
2002-10-23 16:43 ` Eli Zaretskii
2002-10-24 6:47 ` Juanma Barranquero
2002-10-25 7:51 ` Juanma Barranquero
2002-10-23 12:13 ` Juanma Barranquero
2002-10-28 5:57 ` Harald.Maier.BW
2002-10-28 17:52 ` Juanma Barranquero
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=5xof9kp4c4.fsf@kfs2.cua.dk \
--to=storm@cua.dk \
--cc=andrewi@gnu.org \
--cc=eliz@is.elta.co.il \
--cc=emacs-devel@gnu.org \
--cc=jasonr@btinternet.com \
--cc=jay_finger@hotmail.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.
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).