public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Falk Hueffner <falk.hueffner@student.uni-tuebingen.de> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/10212: Preprocessor ## problem Date: Tue, 25 Mar 2003 18:26:00 -0000 [thread overview] Message-ID: <20030325181600.495.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/10212; it has been noted by GNATS. From: Falk Hueffner <falk.hueffner@student.uni-tuebingen.de> To: rwgk@cci.lbl.gov Cc: gcc-gnats@gcc.gnu.org Subject: Re: c++/10212: Preprocessor ## problem Date: 25 Mar 2003 19:09:40 +0100 rwgk@cci.lbl.gov writes: > The code below fails to compile with current cvs gcc 3.3: > > % cat z.cpp > # define BOOST_PYTHON_INPLACE_OPERATOR(op) \ > template <class R> \ > inline R \ > operator##op(R const& a, R const& b ) \ > { \ > return a+b; \ > } > > BOOST_PYTHON_INPLACE_OPERATOR(+) > > % gcc --version > gcc (GCC) 3.3 20030325 (prerelease) > % gcc -c z.cpp > z.cpp:9:32: pasting "operator" and "+" does not give a valid preprocessing token > % echo $status > 1 > > The original code compiles with a large number of compilers > incl. several EDG-based, Visual C++ and gcc 2.96 - gcc 3.2.2. Older > gcc's issue a warning which can be suppressed with -w. Well, gcc is right here, it's simply not valid code. Since C++ allows whitespace between "operator" and the operator token, you could just leave it off. -- Falk
next reply other threads:[~2003-03-25 18:16 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-25 18:26 Falk Hueffner [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-03-26 19:26 Martin Sebor 2003-03-25 18:33 zack 2003-03-25 18:16 rwgk
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=20030325181600.495.qmail@sources.redhat.com \ --to=falk.hueffner@student.uni-tuebingen.de \ --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).