public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: csimon@epeios.org
To: gcc-gnats@gcc.gnu.org
Subject: preprocessor/10513: Annoying warning
Date: Sun, 27 Apr 2003 14:46:00 -0000	[thread overview]
Message-ID: <20030427144052.8463.qmail@sources.redhat.com> (raw)


>Number:         10513
>Category:       preprocessor
>Synopsis:       Annoying warning
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Apr 27 14:46:01 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     SIMON Claude
>Release:        gcc version 3.2 20020927 (prerelease)
>Organization:
>Environment:
Cygwin or GNU/Linux
>Description:
When compiling the below source file ('g++ dummy.cpp'), I obtain this message :

---
dummy.cpp:9:14: warning: pasting "::" and "i" does not give a valid preprocessing token
---

This happend with all gcc 3.x releases. It doesn't happend with the gcc releases prior to 3.x, and other compilers (Borland C++, Visual C++, Metrowerks CodeWarrior) don't issue this warning.
I'm not really sure if this is a bug, but, if not, can you say me what's wrong ?
Thanks !

--- Begin of dummy.cpp source file ---
namespace n {
	int i;
}

#define M(a)	a##i

int main( void )
{
	M(n::) = 42;	// The line which produces the preprocessor warning.

	return 0;
}
--- End of dummy.cpp source file ---
>How-To-Repeat:
g++ dummy.cpp
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2003-04-27 14:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-27 14:46 csimon [this message]
2003-04-27 15:11 nathan

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=20030427144052.8463.qmail@sources.redhat.com \
    --to=csimon@epeios.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).