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


bangerth@dealii.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|                            |1
           Keywords|                            |accepts-invalid
   Last reconfirmed|0000-00-00 00:00:00         |2003-06-06 18:23:02
               date|                            |
            Summary|explicit specialization of a|explicit instantiation of a
                   |typedef not diagnosed       |typedef not diagnosed


------- Additional Comments From bangerth@dealii.org  2003-06-06 18:23 -------
Confirmed, but the syntax you are using is that of an explicit
_instantiation_, not _specialization_. So I change the synopsis.

By 14.7.2/1, only classes, functions or static data members
can be explicitly instantiated. A member typedef is none of
these.

W.


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