Any way to get g++ to warn about missing return in main

Any way to get g++ to warn about missing return in main

[Bill Priest]

All,
	Using gcc & g++ stock 3.0.3 on Linux ix86 I have the following code

t.c & t.cc
--------------
int main(void)
{
}
--------------

Using gcc -Wall -c t.c
t.c: In function `main':
t.c:3: warning: control reaches end of non-void function

Using gcc -Wall -c t.cc
No warnings

Looking at the man pages for 3.0
-Wreturn-type
           Warn whenever a function is defined with a return-type that defaults to "int".  
           Also warn about any "return" statement with no return-value
           in a function whose return-type is not "void".

           For C++, a function without return type always produces a diagnostic message, 
           even when -Wno-return-type is specified.  The only exceptions
           are main and functions defined in system headers.

The second sentence in the second paragraph is a little ambiguous:

It could be read to mean that main and system headers are not checked w/ -Wno-return-type
It could be read to mean that main and system headers are not checked no matter what

Assuming that main and system headers are not checked no matter what I tried the following:
gcc -Wall -pedantic -ansi -Wmain -Wsystem-headers -Wmissing-noreturn -c t.cc

Is there any way to get missing return warnings on main from g++?

It seems inconsistent (to me) to for c++ to require a return type of int; but not get a
warning about not having a return.

My 2 cents,

Bill

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

Re: Any way to get g++ to warn about missing return in main

[Bill Priest]

On Fri, 11 Jan 2002 12:03:35 -0600
"John Love-Jensen" <eljay@adobe.com> wrote:

> Hi Bill,
> 
> I assume your second example was supposed to be "g++ ..." instead of "gcc
> ...".

Actually since the extension is .cc it uses g++ by default.

> 
> As per the C++ specification, it is legal and valid C++ code to have main()
> drop off the end without a return.  The compiler is burdened with putting an
> implicit "return 0;" in the code on the (lazy) programmer's behalf.

I understand that it is legal C++ code; I'd just like for g++ to warn about it
just like gcc does IFF I set a compiler switch warning to catch it (ie. it seems
like -Wmain-return-type).

Of course for this simple example I gave it is obvious that the compiler adding
a return of is is correct; this might not always be the case and without an
explicit statement in the code the compiler can't be sure that is what I intended.

I'm not looking to change the semantics of inserting the default; I'm just looking
for a way for me to be reminded that it is missing in case I don't want the default.

Thanks for the response,

Bill

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com