public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: david@there.com To: gcc-gnats@gcc.gnu.org Subject: preprocessor/7452: Preprocessor doesn't allow pasting " foo-> ## BAR " Date: Tue, 30 Jul 2002 20:06:00 -0000 [thread overview] Message-ID: <200207310300.g6V30AZ29939@dewdev3.there.com> (raw) >Number: 7452 >Category: preprocessor >Synopsis: Preprocessor doesn't allow pasting " foo-> ## BAR " >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: rejects-legal >Submitter-Id: net >Arrival-Date: Tue Jul 30 20:06:01 PDT 2002 >Closed-Date: >Last-Modified: >Originator: root >Release: 3.1.1 >Organization: There, Inc. >Environment: System: Linux dewdev3.there.com 2.4.2-2 #1 Sun Apr 8 20:41:30 EDT 2001 i686 unknown Architecture: i686 host: i686-pc-linux-gnu build: i686-pc-linux-gnu target: i686-pc-linux-gnu configured with: ../gcc-3.1.1/configure --prefix=/usr/local/gcc-3.1.1 --program-suffix=-311 --enable-languages=c,c++ --enable-version-specific-runtime-libs --with-dwarf2 --disable-nls >Description: The GNU preprocessor has in the past been able to append method names after a "->". It should continue to be able to do so. >How-To-Repeat: When in a macro, try to concatenate some "foo->" with a macro parameter like BAR; i.e., "foo->##BAR". Note that the preprocessor will complain, tossing a warning and the (incorrect) text "foo-> baz" will be tossed out. (Assuming macro parameter BAR was set to baz.) Instead, no warning should be issued, and the text "foo->baz" should be output. >Fix: There doesn't seem to be a way to force the preprocessor to accept concatenating anything with a left-hand token that ends in "->". =( >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-07-31 3:06 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-07-30 20:06 david [this message] 2002-07-30 20:26 Andrew Pinski 2002-07-30 20:36 David E. Weekly 2002-07-30 20:46 Andrew Pinski 2002-07-30 20:56 David E. Weekly 2002-07-30 21:06 Andrew Pinski 2002-07-30 21:26 David E. Weekly 2002-07-30 23:36 Neil Booth 2002-07-30 23:37 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=200207310300.g6V30AZ29939@dewdev3.there.com \ --to=david@there.com \ --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: 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).