------- Comment #5 from gdr at integrable-solutions dot net 2005-11-30 20:19
-------
Subject: Re: typedef in class scope not reported by error message
"brad dot king at kitware dot com" <[EMAIL PROTECTED]> writes:
| Okay, if you don't consider it a bug that is fine with me. I just reported
it
| to make sure you were aware of the inconsistency. I'm changing this bug's
| status to Verified.
I don't want to leave you under the impression that your report was
dismissed as unimportant. Quite the contrary. There is a furious
debate in the user community about what the right thing should be. It
is not clear and there does not seem be a right way of doing it.
We're well aware of this issue; we're trying to do our best. I
understand not everybody is happy, but is not an issue we can make
everybody happy.
| Meanwhile I'm still a bit curious as to where in the source the
| argument's true type as written by the user is lost
| ("dereferenced"). Why is it lost only for class-scope typedefs and
| not for namespace-scope ones?
all those are good questions I don't have the answer for yet. But, if
you dig the archive (gcc-patches) you'll have a hint from a recent
patch of Mark Mitchell and another hint about the on-going debate.
| I'm somewhat familiar
| with the internals of GCC and can read the output of -fdump-translation-unit
| but I could not find the spot that loses this information. Any pointers are
| appreciated. Thanks.
-fdump-translation-unit is broken at the present; and if it did work,
it won't help you much. Search for a recent patch of Mark Mitchell
about canonicalizing types.
-- Gaby
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22573
