[Bug c++/16663] Poor parse error recovery with mispelled type in function declaration

2021-10-15 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=16663 --- Comment #9 from Jonathan Wakely --- We no longer print the final "initializer expression list treated as compound expression" error. If we make the example a little more realistic so the thing being mispelled is actually in scope, then GCC

[Bug c++/16663] Poor parse error recovery with mispelled type in function declaration

2011-09-11 Thread rui.maciel at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16663 Rui Maciel rui.maciel at gmail dot com changed: What|Removed |Added CC||rui.maciel at

[Bug c++/16663] Poor parse error recovery with mispelled type in function declaration

2011-09-11 Thread manu at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16663 --- Comment #8 from Manuel López-Ibáñez manu at gcc dot gnu.org 2011-09-11 20:28:50 UTC --- (In reply to comment #7) If 'void' is not allowed and 'misspelled' is not declared, then wouldn't it be better to recognize that case as an undeclared

[Bug c++/16663] Poor parse error recovery with mispelled type in function declaration

2009-08-25 Thread manu at gcc dot gnu dot org
--- Comment #6 from manu at gcc dot gnu dot org 2009-08-25 13:53 --- *** Bug 41054 has been marked as a duplicate of this bug. *** -- manu at gcc dot gnu dot org changed: What|Removed |Added