------- Comment #2 from manu at gcc dot gnu dot org 2009-08-25 13:53 -------
I think this is a duplicate of PR 16663, just a different testcase. One can
possibly construct a lot of different testcases for mispelled/undefined types,
depending on the context where the declaration takes place (return type, first
argument, second argument, inside a class, file scope, function scope), what is
following the myspelled type (more arguments) and other alternatives.
*** This bug has been marked as a duplicate of 16663 ***
--
manu at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |manu at gcc dot gnu dot org
Status|NEW |RESOLVED
Resolution| |DUPLICATE
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41054
