From: Stephen Lindholm <lindholm@CS.Stanford.EDU>
To: gcc@gcc.gnu.org
Subject: Change in preprocessor behavior
Date: Mon, 30 Dec 2002 20:53:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.21.0212301419040.17036-100000@Xenon.Stanford.EDU> (raw)
The stringize and token-pasting operators seem to no longer work in the
"cpp" phases of compilation, but they worked in "cpp" in early versions of
gcc (2.95.3). I can't find it written that those operations must occur in
phases 1-4, but # and ## are "preprocessing-op-or-punc" and it would seem
that they should therefore be processed in phase 4.
Am I doing something wrong?
Using this example from the cpp info page:
#define COMMAND(NAME) { #NAME, NAME ## _command }
struct command commands[] =
{
COMMAND (quit),
COMMAND (help),
};
I get this as expected on an old version of cpp (2.95.3):
Xenon > cpp test2
# 1 "test2"
struct command commands[] =
{
{ "quit", quit_command } ,
{ "help", help_command } ,
};
and this on a new version of cpp (3.1):
thrush:~% cpp test2
# 1 "test2"
struct command commands[] =
{
{ #quit, quit ## _command },
{ #help, help ## _command },
};
next reply other threads:[~2002-12-30 22:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-30 20:53 Stephen Lindholm [this message]
2002-12-30 20:54 ` Neil Booth
2002-12-30 20:54 ` Neil Booth
2002-12-30 20:54 ` Stephen Lindholm
2003-01-02 21:04 ` Devang Patel
2003-01-02 20:42 ` Mike Stump
2003-01-02 21:02 ` Devang Patel
2003-01-04 20:19 ` Zack Weinberg
2002-12-31 10:24 Martin York
2022-06-21 0:34 Dave Blanchard
2022-06-21 7:28 ` Richard Biener
2022-06-21 12:57 ` Dave Blanchard
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=Pine.GSO.4.21.0212301419040.17036-100000@Xenon.Stanford.EDU \
--to=lindholm@cs.stanford.edu \
--cc=gcc@gcc.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.
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).