From: Benjamin Riefenstahl <Benjamin.Riefenstahl@epost.de>
Subject: Re: 21.3.50 for Cygwin: patch 5
Date: 05 Jan 2003 17:45:16 +0100 [thread overview]
Message-ID: <m3wuljtujn.fsf@cicero.benny.turtle-trading.net> (raw)
In-Reply-To: <5xptrcjv3l.fsf@kfs2.cua.dk>
Pardon me for butting in.
storm@cua.dk (Kim F. Storm) writes:
> We already use P_ in most cases (under src/), and __P in a few other
> cases (mostly under lib-src/ and lwlib/).
>
> So it seems a bit odd that pop.c (as the only file) uses _P.
>
> I suggest we simply change pop.c to use __P like the other files in
> lib-src.
Both "__P" and "_P" are both firmly and totally in the compiler domain
(anything matching the regexp /^_[_A-Z]/ is). Compilers can use these
symbols however they see fit. "P_" OTOH is free for use in user
programs. So if a change is needed anyway, it should be to "P_"
(IMO).
so long, benny
next prev parent reply other threads:[~2003-01-05 16:45 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3wuljtujn.fsf@cicero.benny.turtle-trading.net \
--to=benjamin.riefenstahl@epost.de \
/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.