From: Joe Buehler <jbuehler@hekimian.com>
Subject: Re: 21.3.50 for Cygwin: patch 5
Date: Mon, 06 Jan 2003 08:45:33 -0500 [thread overview]
Message-ID: <avc180$u28$1@main.gmane.org> (raw)
In-Reply-To: <5xadifkudi.fsf@kfs2.cua.dk>
Kim F. Storm wrote:
> True, but the specific problem is with cygwin and the _P in pop.c;
> there doesn't seem to have been reported similar problems with __P, so
> we have two options:
>
> 1) a small, localized change in pop.c (_P => __P)
> 2) a wider, non-localized change (_P and __P => P_)
>
> Actually, doing 1 now doesn't mean that we cannot do 2 later...
FYI, I just checked some of the machines I have access to. AIX 4.3 and
5.1 both have NLctype.h that defines _P. HPUX 10.20, 11.0 and 11i
all have _P defined in ctype.h. SunOS 5.8 has _P defined in
/usr/include/iso/ctype_iso.h. It looks like this is some sort of legacy
thing for character classes.
Joe Buehler
next prev parent reply other threads:[~2003-01-06 13: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
2003-01-06 0:13 ` Kim F. Storm
2003-01-06 13:45 ` Joe Buehler [this message]
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
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='avc180$u28$1@main.gmane.org' \
--to=jbuehler@hekimian.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).