public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gdr at integrable-solutions dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/27560] template function not recognized when invoked with enum defined in function Date: Thu, 11 May 2006 16:24:00 -0000 [thread overview] Message-ID: <20060511162407.3783.qmail@sourceware.org> (raw) In-Reply-To: <bug-27560-1313@http.gcc.gnu.org/bugzilla/> [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain, Size: 873 bytes --] ------- Comment #3 from gdr at integrable-solutions dot net 2006-05-11 16:24 ------- Subject: Re: New: template function not recognized when invoked with enum defined in function "ian at airs dot com" <gcc-bugzilla@gcc.gnu.org> writes: | Compiling this file, with mainline, gcc 4.0, or 4.1 | | template<typename t> void f(t a) { } | void g() { enum e { v }; f(v); } | | gives this error message: | | foo.cc: In function Âvoid g()Â: | foo.cc:2: error: no matching function for call to Âf(g()::e)Â | | If the enum definition is moved out of the function, this works. With gcc 3.2, | this works. I didn't try 3.4. There is a core issue for this. We discussed it again at the last meeting in Berlin. There are proposals to make it "just work", but that is still in the open state. -- Gaby -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27560
next prev parent reply other threads:[~2006-05-11 16:24 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-05-11 15:43 [Bug c++/27560] New: " ian at airs dot com 2006-05-11 15:58 ` [Bug c++/27560] " pinskia at gcc dot gnu dot org 2006-05-11 16:07 ` pinskia at gcc dot gnu dot org 2006-05-11 16:24 ` gdr at integrable-solutions dot net [this message] 2006-05-11 16:33 ` gdr at gcc dot gnu dot org 2006-05-11 16:38 ` pinskia at gcc dot gnu dot org 2006-05-11 16:48 ` gdr at integrable-solutions dot net 2006-05-11 22:56 ` ian at airs dot com 2006-05-11 23:03 ` pinskia at gcc dot gnu dot org 2006-05-11 23:20 ` gdr at integrable-solutions dot net 2009-11-04 20:16 ` jason at gcc dot gnu dot org
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=20060511162407.3783.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: 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).