public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Zack Weinberg <zack@codesourcery.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: preprocessor/7457: failure preprocessing ## directive Date: Wed, 31 Jul 2002 13:16:00 -0000 [thread overview] Message-ID: <20020731201602.26047.qmail@sources.redhat.com> (raw) The following reply was made to PR preprocessor/7457; it has been noted by GNATS. From: Zack Weinberg <zack@codesourcery.com> To: gnicholls@bluephoenixsolutions.com Cc: gcc-gnats@gcc.gnu.org Subject: Re: preprocessor/7457: failure preprocessing ## directive Date: Wed, 31 Jul 2002 13:15:00 -0700 On Wed, Jul 31, 2002 at 07:50:39PM -0000, gnicholls@bluephoenixsolutions.com wrote: > >Description: > The following construct fails compilation:- > #define LIB_SUFF ".so" > #define SV_MODULE_NAME_STR "libdrv"##LIB_SUFF The ## is completely unnecessary in this case. Remove it and your code will work again. The C standard specifies that the result of a token-paste is undefined if the two tokens cannot be combined into a single token. This is always true of two string constants. That is what the warning is telling you. zw
next reply other threads:[~2002-07-31 20:16 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-07-31 13:16 Zack Weinberg [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-08-01 5:46 Gregory Nicholls 2002-07-31 15:21 neil 2002-07-31 12:56 gnicholls
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=20020731201602.26047.qmail@sources.redhat.com \ --to=zack@codesourcery.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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: linkBe 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).