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/4923: Concatenation appears to handle whitespace incorrectly
Date: Fri, 16 Nov 2001 23:56:00 -0000	[thread overview]
Message-ID: <20011121223602.3236.qmail@sourceware.cygnus.com> (raw)

The following reply was made to PR preprocessor/4923; it has been noted by GNATS.

From: Zack Weinberg <zack@codesourcery.com>
To: s0009525@chelt.ac.uk
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: preprocessor/4923: Concatenation appears to handle whitespace incorrectly
Date: Wed, 21 Nov 2001 09:24:54 -0800

 On Wed, Nov 21, 2001 at 04:30:06PM -0000, s0009525@chelt.ac.uk wrote:
 > #define FOO(x) x
 > #define BAR    FOO(abc) ## def
 > BAR
 > 
 > /* cpp < test.h */
 > 
 > # 1 ""
 >  abc  def
 
 This behavior is correct.  The concatenation operator acts before the
 macro FOO is expanded.  At that point the tokens on either side of ##
 are ")" and "def".  Pasting them together produces an invalid token,
 ")def", which triggers undefined behavior - we choose to pretend the
 ## never happened.  Then "FOO ( abc )" gets expanded to produce "abc".
 Since "abc" and "def" were not concatenated, cpp has to put a space
 between them so they are interpreted sa separate tokens.
 
 gcc 3.x will warn you when this happens:
 
 $ cpp-3.0 test.c
 test.c:5:1: warning: pasting ")" and "def" does not give a valid 
 preprocessing token
 # 5 "test.c"
 abc def
 
 zw


             reply	other threads:[~2001-11-21 22:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-16 23:56 Zack Weinberg [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-11-19 20:36 'Zack Weinberg'
2001-11-19 20:32 Baum, Nathan I
2001-11-19 20:27 'Zack Weinberg'
2001-11-18 16:50 Baum, Nathan I
2001-11-17  0:46 rodrigc
2001-11-17  0:44 rodrigc
2001-11-16 23:46 s0009525

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=20011121223602.3236.qmail@sourceware.cygnus.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: 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).