public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Falk Hueffner <falk.hueffner@student.uni-tuebingen.de> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/10569: use typedef type as return from main yields warning Date: Wed, 30 Apr 2003 18:36:00 -0000 [thread overview] Message-ID: <20030430183601.28251.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/10569; it has been noted by GNATS. From: Falk Hueffner <falk.hueffner@student.uni-tuebingen.de> To: bangerth@dealii.org Cc: gcc-bugs@gcc.gnu.org, wxy@kivera.com, gcc-gnats@gcc.gnu.org Subject: Re: c++/10569: use typedef type as return from main yields warning Date: 30 Apr 2003 20:26:07 +0200 bangerth@dealii.org writes: > Old Synopsis: use typedef type as return from main > New Synopsis: use typedef type as return from main yields warning > > State-Changed-From-To: open->analyzed > State-Changed-By: bangerth > State-Changed-When: Wed Apr 30 18:02:19 2003 > State-Changed-Why: > Confirmed with present 3.4. The standard says in 3.6.1.2: > > An implementation shall not predefine the main function. This func- > tion shall not be overloaded. It shall have a return type of type > int,... > I can't say whether this rules out having a typedef to > int instead. I think the answer is: don't do it, there's > no good reason for such bogosity. There's something weird going on, though. For me, it fails with *error* when turning on -Wall, but not when additionally giving -pedantic: falk@juist:/tmp% g++ --version g++ (GCC) 3.4 20030423 (experimental) falk@juist:/tmp% g++ -O2 test.cc falk@juist:/tmp% g++ -O2 -Wall test.cc test.cc:2: error: return type for `main' changed to `int' falk@juist:/tmp% g++ -O2 -Wall -pedantic test.cc test.cc:2: warning: return type for `main' changed to `int' Adding -Wall shouldn't make any program fail, I think. -- Falk
next reply other threads:[~2003-04-30 18:36 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-04-30 18:36 Falk Hueffner [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-05 7:21 lerdsuwa 2003-04-30 19:26 Geoff Keating 2003-04-30 18:36 Wolfgang Bangerth 2003-04-30 18:36 Gabriel Dos Reis 2003-04-30 18:02 bangerth
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20030430183601.28251.qmail@sources.redhat.com \ --to=falk.hueffner@student.uni-tuebingen.de \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).