public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: gawrilow@math.tu-berlin.de To: gcc-gnats@gcc.gnu.org Subject: c++/10750: 3.4 parser error with template template parameters Date: Mon, 12 May 2003 14:06:00 -0000 [thread overview] Message-ID: <20030512135821.9307.qmail@sources.redhat.com> (raw) >Number: 10750 >Category: c++ >Synopsis: 3.4 parser error with template template parameters >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: rejects-legal >Submitter-Id: net >Arrival-Date: Mon May 12 14:06:00 UTC 2003 >Closed-Date: >Last-Modified: >Originator: Ewgenij Gawrilow >Release: 3.4 20030509 (experimental) >Organization: >Environment: RedHat 7.3 on an Athlon PC Configured with: ../gcc-3.4/gcc/configure --enable-languages=c++ --enable-shared --with-cpu=athlon --enable-version-specific-runtime-libs --with-gxx-include-dir=/usr/local/include/c++/3.4 >Description: The attached (syntactically correct) code causes an erroneous error message: test.cc:6: error: `list_search<First, Second, Predicate>::answer' cannot appear in a constant-expression. Old parser (3.0 .. 3.3) has not any problems with this. >How-To-Repeat: just compile it >Fix: >Release-Note: >Audit-Trail: >Unformatted: ----gnatsweb-attachment---- Content-Type: application/octet-stream; name="test.cc" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="test.cc" dGVtcGxhdGUgPHR5cGVuYW1lIEZpcnN0LCB0eXBlbmFtZSBTZWNvbmQsIHRlbXBsYXRlIDx0eXBl bmFtZSx0eXBlbmFtZT4gY2xhc3MgUHJlZGljYXRlPgpzdHJ1Y3QgbGlzdF9zZWFyY2ggewogICAv Ly8gd2hldGhlciBhdCBsZWFzdCBvbmUgcGFpciBmb3VuZAogICBzdGF0aWMgY29uc3QgYm9vbCBh bnN3ZXI9UHJlZGljYXRlPEZpcnN0LFNlY29uZD46OmFuc3dlcjsKICAgLy8vIHdoZXJlIGl0IHdh cyBmb3VuZAogICBzdGF0aWMgY29uc3QgaW50IHBvcz0gYW5zd2VyID8gMCA6IC0xOwp9Owo=
reply other threads:[~2003-05-12 14:06 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030512135821.9307.qmail@sources.redhat.com \ --to=gawrilow@math.tu-berlin.de \ --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).