From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6514 invoked by alias); 30 Apr 2003 18:02:19 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 6495 invoked by uid 48); 30 Apr 2003 18:02:19 -0000 Date: Wed, 30 Apr 2003 18:02:00 -0000 Message-ID: <20030430180219.6494.qmail@sources.redhat.com> To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, wxy@kivera.com From: bangerth@dealii.org Reply-To: bangerth@dealii.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, wxy@kivera.com, gcc-gnats@gcc.gnu.org Subject: Re: c++/10569: use typedef type as return from main yields warning X-SW-Source: 2003-04/txt/msg01467.txt.bz2 List-Id: 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. W. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10569