[Bug c++/38780] upgrade warning to error for bad C++ code ?

[dcb314 at hotmail dot com]

------- Comment #2 from dcb314 at hotmail dot com  2009-01-10 08:47 -------
(In reply to comment #1)
> You can get an error via -pedantic-errors.  

Agreed - but switching on that flag opens a whole can of worms.

All I'm interested in is getting this *one* warning changed into
an error, for default use of the C++ compiler, without any kitchen
sink flags that render other C++ code uncompilable.

>This has always been a warning for the C front-end so this change makes 
> the C++ front-end consistent with the C front-end.

AFAIK, both front ends should be erroring this kind of code,
because it's neither ISO C nor ISO C++.

gcc 4.3.2, at least in the Suse version, does it right.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38780