public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: bangerth@dealii.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, giovannibajo@libero.it, nobody@gcc.gnu.org Subject: Re: c++/10530: [3.4 regression] Cannot access non-dependent type within nested template Date: Tue, 29 Apr 2003 00:19:00 -0000 [thread overview] Message-ID: <20030429001914.30806.qmail@sources.redhat.com> (raw) Synopsis: [3.4 regression] Cannot access non-dependent type within nested template State-Changed-From-To: open->analyzed State-Changed-By: bangerth State-Changed-When: Tue Apr 29 00:19:14 2003 State-Changed-Why: Correct. Even smaller: -------------------------- template <typename T> struct Foo { struct Inner { typedef int type; }; }; template <typename A> struct Bar { typedef typename Foo<int>::Inner::type type; }; ------------------------------ This won't compile with present mainline: g/x> /home/bangerth/bin/gcc-3.4-pre/bin/c++ -c x.cc x.cc:9: error: no type named `type' in `struct Foo<int>::Inner' x.cc:9: error: ISO C++ forbids declaration of `type' with no type If now someone (probably rightfully) argues that the "typename" is not necessary here -- this is what we get in that case: g/x> /home/bangerth/bin/gcc-3.4-pre/bin/c++ -c x.cc x.cc:9: error: type `Foo<int>::Inner' is not derived from type `Bar<A>' x.cc:9: error: ISO C++ forbids declaration of `type' with no type x.cc:9: error: expected `;' Ups, that's even worse... For the record: icc7 compiles it with and without the typename stuff. So does gcc3.3, so this is indeed a regression. W. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10530
next reply other threads:[~2003-04-29 0:19 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-04-29 0:19 bangerth [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-04-28 23:36 giovannibajo
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=20030429001914.30806.qmail@sources.redhat.com \ --to=bangerth@dealii.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=giovannibajo@libero.it \ --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).