This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: "no return statement" warning weirdness
- From: Neil Booth <neil at daikokuya dot co dot uk>
- To: Chris Lattner <sabre at nondot dot org>
- Cc: Ulrich Weigand <weigand at i1 dot informatik dot uni-erlangen dot de>, gcc at gcc dot gnu dot org
- Date: Thu, 18 Mar 2004 20:53:54 +0000
- Subject: Re: "no return statement" warning weirdness
- References: <Pine.LNX.4.44.0403181446120.7379-100000@nondot.org>
Chris Lattner wrote:-
> >IMO we should warn whether implicit int or not.
>
> I speculate that this is attempting to avoid warning in cases like this:
>
> foo() {}
>
> ... Where the function defaults to returning int, though the programmer
> may never use the return value. I think that it's reasonable to avoid
> warning on that function, but it is still important to warn on the
> slightly different:
>
> int foo() {}
Why? If it's a void function it only takes another 5 keystrokes to make
it so.
Neil.