This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug c++/11113] explicit instantiation of a typedef not diagnosed


PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11113



------- Additional Comments From giovannibajo@libero.it  2003-06-09 11:35 -------
The code is invalid, but I think it's another part of the standard that should 
be enforced. In fact, a typedef is an alias of a type, so $14.7.2/1 does not 
apply, since the name does effectively names a class.

The problem is earlier: the explicit instantion syntax requires the use of an 
elaborated-type-specifier, which does not allow the use of typedefs 
($7.1.5.3/2). We already have an open bug to track this (PR11036). Anyway, I'll 
keep this open to be 100% sure that this problem will get fixed.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]