This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: c++/9621: const int typedef is rejected
- From: bangerth at dealii dot org
- To: gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, nobody at gcc dot gnu dot org, patrick dot rabau at gs dot com
- Date: 8 Feb 2003 00:22:54 -0000
- Subject: Re: c++/9621: const int typedef is rejected
- Reply-to: bangerth at dealii dot org, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, nobody at gcc dot gnu dot org, patrick dot rabau at gs dot com, gcc-gnats at gcc dot gnu dot org
Synopsis: const int typedef is rejected
State-Changed-From-To: open->feedback
State-Changed-By: bangerth
State-Changed-When: Sat Feb 8 00:22:54 2003
State-Changed-Why:
Fixed in 3.4: it accepts both typedefs.
I'm surprised that this is legal at all. The standard says
that typedef expressions need to "contain" the typedef
keyword, but the examples only show it as in the form
typedef type1 type2;
Can some language lawyer comment on whether and why
type1 typedef type2;
is legal syntax?
It's also accepted by the C frontend, by the way.
W.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9621