all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jason Rumney <jasonr@gnu.org>
Cc: sridhar_ml@yahoo.com, emacs-devel@gnu.org
Subject: Re: 23.0.50 compile problem on Windows XP
Date: Fri, 05 Oct 2007 10:19:33 +0200	[thread overview]
Message-ID: <umyuy7z3e.fsf@gnu.org> (raw)
In-Reply-To: <4705F100.2000107@gnu.org> (message from Jason Rumney on Fri, 05 Oct 2007 09:08:32 +0100)

> Date: Fri, 05 Oct 2007 09:08:32 +0100
> From: Jason Rumney <jasonr@gnu.org>
> Cc: sridhar_ml@yahoo.com, emacs-devel@gnu.org
> 
> Eli Zaretskii wrote:
> > What constant? I don't see it in the MinGW headers, but maybe MSVC
> > headers are different.
> >   
> mingw only defines abs in stdlib.h

It defines a _function_ `abs', not a macro.  A macro is not defined
anywhere, AFAICS.

> > And I still didn't get an answer to my question from yesterday: What
> > is on and around line 182 of VC's math.h that causes the failure below?
> >   
> I have a different version of VC, but it seems it is the declaration of
> abs that causes the problem:
> 
>         int     __cdecl abs(__in int _X);
> 
> Since lisp.h has already been included, this gets expanded as the macro
> defined there, which causes a syntax error.

So we are talking about a function-vs-macro mess?  If so, I'd suggest
to rename the macro to something like `emacs_abs', because there's no
good solution to this that I know of.  Carefully crafted headers can
avoid this by taking function names in parens, like this:

      int     __cdecl (abs)(__in int _X);

but if they don't, there's nothing we can do to fix this in general.
Changing the order of headers is just a temporary kludge, IMHO; if we
do that, the problem will continue to haunt us.

  reply	other threads:[~2007-10-05  8:19 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-02 22:42 23.0.50 compile problem on Windows XP Sridhar Boovaraghavan
2007-10-03  8:00 ` Eli Zaretskii
2007-10-03  8:16   ` dhruva
2007-10-03  8:23     ` Jason Rumney
2007-10-03 10:01       ` dhruva
2007-10-03 12:10         ` Jason Rumney
2007-10-03 12:20           ` Jason Rumney
2007-10-03 12:59             ` dhruva
2007-10-04 18:03             ` Sridhar Boovaraghavan
2007-10-04 22:11               ` Jason Rumney
2007-10-05  0:46                 ` David Robinow
2007-10-05  8:02                   ` Eli Zaretskii
2007-10-05  1:17                 ` Sridhar Boovaraghavan
2007-10-05  8:06                   ` Eli Zaretskii
2007-10-05  8:00                 ` Eli Zaretskii
2007-10-05  8:11                   ` Jason Rumney
2007-10-05  8:30                     ` Eli Zaretskii
2007-10-06 13:14                       ` Richard Stallman
2007-10-13 12:49                         ` Eli Zaretskii
2007-10-05  9:31                 ` Eli Zaretskii
2007-10-05 10:00                   ` dhruva
2007-10-05 10:16                     ` Eli Zaretskii
2007-10-05  7:56           ` Eli Zaretskii
2007-10-05  8:08             ` Jason Rumney
2007-10-05  8:19               ` Eli Zaretskii [this message]
2007-10-05  8:21             ` dhruva
2007-10-05  8:31               ` Eli Zaretskii
2007-10-05  8:53                 ` dhruva
2007-10-03 12:19         ` Eli Zaretskii

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=umyuy7z3e.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jasonr@gnu.org \
    --cc=sridhar_ml@yahoo.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.