On 11/14/2013 06:31 AM, Dodji Seketeli wrote:
int foo() {
return;
}
I am wondering why this warning hasn't been activated by default in the
first place, for C++ at least?
Note that using g++ to compile the example above with -std=c++98 yields:
foo.c:2:2: error: return-statement with no value, in function returning
‘int’ [-fpermissive]
So what do we gain from not emitting that warning by default there?
If we already give an error, we don't want to give a redundant warning.
I'm confused about what you're asking here.
Jason
