public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: bangerth@dealii.org To: eivuokko@bonumit.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org Subject: Re: c++/8858: Gcc "rebinds" template member names. Date: Mon, 09 Dec 2002 11:29:00 -0000 [thread overview] Message-ID: <20021209192953.17563.qmail@sources.redhat.com> (raw) Synopsis: Gcc "rebinds" template member names. State-Changed-From-To: open->analyzed State-Changed-By: bangerth State-Changed-When: Mon Dec 9 11:29:52 2002 State-Changed-Why: Confirmed. Very wicked template magic, though. Here's a slightly smaller testcase, failing in the wrong place: ----------------------------------#include <cassert> template<class T_, class U_> struct cons {}; template<class L_> struct list { typedef L_ type; template<class T_> class add : public ::list< ::cons<T_, L_> > {}; }; template<class T1_,class T2_> struct IsSame { enum { Value = false }; }; template<class T_> struct IsSame<T_,T_> { enum { Value = true } ; }; int main() { typedef list<cons<double,float> >::add<char>::add<int>::type test_type; // this should absolutely fail assert((IsSame<cons<int, cons<double,float> >, test_type>::Value )); // and this shouldn't assert(( IsSame< cons<int, cons<char, cons<double,float> > >, test_type>::Value )); } ------------------------------ This never went right, at least not back to 2.95. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8858
next reply other threads:[~2002-12-09 19:29 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-12-09 11:29 bangerth [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-12-07 6:36 eivuokko
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=20021209192953.17563.qmail@sources.redhat.com \ --to=bangerth@dealii.org \ --cc=eivuokko@bonumit.com \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --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).