From: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org
Subject: Re: 21.3.50 for Cygwin: patch 5
Date: 09 Jan 2003 00:52:33 +0100 [thread overview]
Message-ID: <5xn0mb42ta.fsf@kfs2.cua.dk> (raw)
In-Reply-To: <E18Vyi9-0007U6-00@fencepost.gnu.org>
Richard Stallman <rms@gnu.org> writes:
> There are other files in
> lwlib/ (e.g. xlwmenu.c) and src/ (e.g. gmalloc.c, mktime.c,
> and others) which uses __P as well.
>
> For gmalloc.c and mktime.c, this was probably because they were copied
> from Glibc, which can legitimately use names like __P. (There's one
> exception: unexalpha.c.)
>
> In some sense we ought to change these files not to use __P when
> moving the code outside Glibc, but that is unfortunate since it would
> require a fork.
>
> However, it would be better to use P_ instead in the other files.
> That is more consistent with the rest of Emacs, and with the C standard.
The problem is that P_ is defined in src/lisp.h, while __P is defined
in config.h (as defined by configure). I guess that's why __P is used
outside src/ (and some files in src/ as well).
Defining P_ in config.h (via configure) is of course possible, but
even if we change everything (except the Glibc originated files) to
use P_, we still will have the __P definition in config.h -- so IMO
there really isn't a great need to make this change.
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2003-01-08 23:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-06 18:36 [PATCHES] 21.3.50 for Cygwin: patch 5 Joe Buehler
2002-12-25 6:12 ` Eli Zaretskii
2002-12-26 13:15 ` Juanma Barranquero
2002-12-26 23:39 ` Richard Stallman
2002-12-27 7:46 ` Juanma Barranquero
2002-12-28 21:22 ` Richard Stallman
2003-01-03 16:19 ` Joe Buehler
2003-01-04 4:19 ` Richard Stallman
2003-01-05 0:31 ` Kim F. Storm
2003-01-05 16:45 ` Benjamin Riefenstahl
2003-01-06 0:13 ` Kim F. Storm
2003-01-06 13:45 ` Joe Buehler
2003-01-06 17:13 ` Richard Stallman
2003-01-07 9:47 ` Kim F. Storm
2003-01-07 18:44 ` Richard Stallman
2003-01-08 23:52 ` Kim F. Storm [this message]
2003-01-09 23:14 ` Richard Stallman
2003-01-10 9:49 ` Kim F. Storm
2003-01-10 19:44 ` Eli Zaretskii
2003-01-11 0:02 ` Kim F. Storm
2003-01-12 11:55 ` Richard Stallman
2003-01-11 0:22 ` Richard Stallman
2003-01-05 18:34 ` [PATCHES] " Richard Stallman
2003-01-04 10:07 ` 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
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=5xn0mb42ta.fsf@kfs2.cua.dk \
--to=storm@cua.dk \
--cc=emacs-devel@gnu.org \
/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).