This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/17232] classes and class template specializations treated differently w.r.t. core issue #337
- From: "jason at redhat dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 30 Aug 2004 22:12:02 -0000
- Subject: [Bug c++/17232] classes and class template specializations treated differently w.r.t. core issue #337
- References: <20040829175551.17232.cludwig@cdc.informatik.tu-darmstadt.de>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From jason at redhat dot com 2004-08-30 22:12 -------
Subject: Re: classes and class template specializations
treated differently w.r.t. core issue #337
I think that while the overloading makes the question more interesting,
there is a simpler form:
template<typename T>
class A {
virtual void f() = 0;
};
A<int>(*p)[1];
Is the compiler required to diagnose this? If so, simply creating an array
type requires that the element type be instantiated. I think that this is
the right answer, but I also think it's worth discussing with the
committee.
Jason
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17232