This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/12581] [3.4 Regression] gcc rejects typeof use for the return type
- From: "gabor dot greif at lucent dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 12 Nov 2003 12:35:37 -0000
- Subject: [Bug c++/12581] [3.4 Regression] gcc rejects typeof use for the return type
- References: <20031011162654.12581.pinskia@gcc.gnu.org>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From gabor dot greif at lucent dot com 2003-11-12 12:35 -------
(In reply to comment #4)
> This is not a bug.
I beg your pardon. If I understand your comment #3 correctly,
a __typeof__() can appear "anywhere a typedef name could be used".
A typedef name can certainly appear a the result type of a PTMF type
declaration. So I cannot understand why a typeof construct must not.
This looks illogical to me.
This bug omits some stuff from its parent PR#12577. There I see:
foobar.cpp:35: error: expected unqualified-id
I ask myself why a typeof construct cannot be an unqualified-id?
Also, I think the analysis in comment #1 is completely bogus.
The example mentioned in it does not deal with pointer-to-member-function types
at all.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12581