public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: neil@gcc.gnu.org
To: alexandervpetrov@hotmail.com, gcc-bugs@gcc.gnu.org,
	gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org
Subject: Re: preprocessor/5513: considers non-nested macro as nested one
Date: Mon, 28 Jan 2002 05:49:00 -0000	[thread overview]
Message-ID: <20020128134948.17044.qmail@sources.redhat.com> (raw)

Synopsis: considers non-nested macro as nested one

State-Changed-From-To: open->closed
State-Changed-By: neil
State-Changed-When: Mon Jan 28 05:49:45 2002
State-Changed-Why:
    This is not a bug either.  I suggest you try
    
    www.comeaucomputing.com/tryitout
    
    with the -E option for independent verification before
    posting any more examples.  What software uses macros
    like this anyway?
    
    For PR/5498, the macro A has completely finished expanding
    and its expansion has been left (in order to get the ')')
    at the time that A comes up for re-expansion.  Hence it expands again.
    
    In this example (which is 5498 with an extra parenthesis)
    the original B is *still under expansion* when macro A
    is invoked, and so the token B in A's expansion
    is never considered for expansion, because that would
    be a nested expansion of B.  The opening parenthesis
    at the end of A is not even looked at when this
    decision to not expand B is made; B is still at
    the bottom of the macro stack.  See the difference?

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5513


             reply	other threads:[~2002-01-28 13:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-28  5:49 neil [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-01-28  5:06 alexandervpetrov

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=20020128134948.17044.qmail@sources.redhat.com \
    --to=neil@gcc.gnu.org \
    --cc=alexandervpetrov@hotmail.com \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --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).