This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: G++/GCC not detetcing stupid errors in code.
- From: Christopher Layne <clayne at anodized dot com>
- To: Axel Freyn <axel-freyn at gmx dot de>
- Cc: gcc-help at gcc dot gnu dot org
- Date: Mon, 9 Jun 2008 00:43:53 +0000
- Subject: Re: G++/GCC not detetcing stupid errors in code.
- References: <48352be5.0c58560a.66c6.16bf@mx.google.com> <4835353E.4000800@cs.uni-frankfurt.de> <-457754682823264016@unknownmsgid> <8bc817ee0805220400y390d8138s91447dbeeaaf847d@mail.gmail.com> <48355ef3.1358560a.6a9d.0fc9@mx.google.com> <20080522122005.GA12930@localhost.localdomain>
On Thu, May 22, 2008 at 02:22:49PM +0200, Axel Freyn wrote:
> I would expect that this warning does not exist, because omitting the return-statement in
> "main" is perfectly valid in C++: (C++-Standard, 3.6.1.3)
> "If control reaches the end of main without encountering a return statement, the
> effect is that of executing return 0;"
>
> For other functions, g++ also emits a warning if you forget the return
> statement.
>
> Axel
This is something, that while valid by the C++ "Standard", I surely hope
doesn't become common practice.
-cl