From: "Zack Weinberg" <zackw@stanford.edu>
To: Neil Booth <neil@daikokuya.demon.co.uk>
Cc: Mark Kettenis <kettenis@wins.uva.nl>,
libc-hacker@sources.redhat.com, gcc@gcc.gnu.org
Subject: Re: Preprocessor woes
Date: Fri, 05 Jan 2001 14:41:00 -0000 [thread overview]
Message-ID: <20010105144026.I268@wolery.stanford.edu> (raw)
In-Reply-To: <20010105214555.D740@daikokuya.demon.co.uk>
On Fri, Jan 05, 2001 at 09:45:55PM +0000, Neil Booth wrote:
> Mark Kettenis wrote:-
>
> > occur. Since the SHLIB_COMPAT macro uses the ISO C ## concatenation
> > operator, -traditional messes things up. Is there any chance at
> > convincing the GCC folks to provide a preprocessor that's backwards
> > compatible with cccp?
>
> Try using the portable CONCAT macros that GCC does. That's much
> simpler than rewriting tradcpp (which is what this would require).
Concatenation with ## has never worked in -traditional mode. The real
problem is something else.
zw
next prev parent reply other threads:[~2001-01-05 14:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-05 13:34 Mark Kettenis
2001-01-05 13:46 ` Neil Booth
2001-01-05 14:41 ` Zack Weinberg [this message]
2001-01-05 15:39 ` Mark Kettenis
2001-01-05 16:11 ` Richard Henderson
2001-01-05 16:56 ` Joe Buck
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=20010105144026.I268@wolery.stanford.edu \
--to=zackw@stanford.edu \
--cc=gcc@gcc.gnu.org \
--cc=kettenis@wins.uva.nl \
--cc=libc-hacker@sources.redhat.com \
--cc=neil@daikokuya.demon.co.uk \
/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.
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).