public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bangerth at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/38681] Internal compiler error. expr.c:6956 [Template instantiation with non-type value of member function ptr]
Date: Fri, 30 Jan 2009 15:52:00 -0000 [thread overview]
Message-ID: <20090130155143.12793.qmail@sourceware.org> (raw)
In-Reply-To: <bug-38681-17131@http.gcc.gnu.org/bugzilla/>
------- Comment #7 from bangerth at gmail dot com 2009-01-30 15:51 -------
(In reply to comment #5)
> Did I understand this wrong ? Does the correct interpretation of the standard
> not allow for member-function-pointers as non-type arguments ?
It does, but it requires them to be in a constant-expression context -- i.e.
informally speaking the compiler needs to know *at compile time* which member
function you refer to. You can use a function argument as a template
argument.
I think this is indeed a duplicate of PR 37093.
W.
W.
*** This bug has been marked as a duplicate of 37093 ***
--
bangerth at gmail dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bangerth at gmail dot com
Status|UNCONFIRMED |RESOLVED
Resolution| |DUPLICATE
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38681
prev parent reply other threads:[~2009-01-30 15:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-31 7:42 [Bug c++/38681] New: " juvvij at gmail dot com
2008-12-31 7:44 ` [Bug c++/38681] " juvvij at gmail dot com
2008-12-31 7:44 ` juvvij at gmail dot com
2008-12-31 7:51 ` pinskia at gcc dot gnu dot org
2008-12-31 16:12 ` pinskia at gcc dot gnu dot org
2008-12-31 17:32 ` juvvij at gmail dot com
2008-12-31 17:42 ` pinskia at gcc dot gnu dot org
2009-01-30 15:52 ` bangerth at gmail dot com [this message]
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=20090130155143.12793.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).