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: "giovannibajo at libero dot it" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 6 Sep 2004 13:43:30 -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 giovannibajo at libero dot it 2004-09-06 13:43 -------
(In reply to comment #12)
Jason:
> 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.
I agree too. GCC does not diagnose this case yet, we prolly need to complete
the type in create_array_type_for_decl. If you want, I can prepare such a
patch, and this issue can be tracked in another PR.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17232