public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: struppi@acm.org
To: gcc-gnats@gcc.gnu.org
Subject: c++/8783: Macros in #include directive not expanded correctly
Date: Mon, 02 Dec 2002 04:16:00 -0000	[thread overview]
Message-ID: <20021202121501.29615.qmail@sources.redhat.com> (raw)


>Number:         8783
>Category:       c++
>Synopsis:       Macros in #include directive not expanded correctly
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Dec 02 04:16:01 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     struppi@acm.org
>Release:        unknown-1.0
>Organization:
>Environment:
Debian GNU/Linux 3.0 (woody), gcc 3.2.1/cpp-3.2
>Description:
The macro isn't expanded any more. Expected to include file onetwothree.h during compile, but an error is reported:

p.cc:5:16: warning: extra tokens at end of #include directive
p.cc:5:41: one: No such file or directory

With cpp included in gcc 2.95.4 the macro expands correctly.
>How-To-Repeat:
cpp-3.2 p.cc
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="p.cc"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="p.cc"

CiNkZWZpbmUgbWtfY3BwX3N0cih4KSBta19jcHBfc3RyXyh4KQojZGVmaW5lIG1rX2NwcF9zdHJf
KHgpICN4CgojaW5jbHVkZSAib25lIiBta19jcHBfc3RyKHR3bykgInRocmVlLmgiCgpwcmUgbWtf
Y3BwX3N0cihpbikgcG9zdAoiYSIgbWtfY3BwX3N0cihiKSAiYyIK


             reply	other threads:[~2002-12-02 12:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-02  4:16 struppi [this message]
2002-12-02  4:30 neil

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=20021202121501.29615.qmail@sources.redhat.com \
    --to=struppi@acm.org \
    --cc=gcc-gnats@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).