From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 533 invoked by alias); 30 Apr 2003 19:26:01 -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 517 invoked by uid 71); 30 Apr 2003 19:26:01 -0000 Date: Wed, 30 Apr 2003 19:26:00 -0000 Message-ID: <20030430192601.512.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Geoff Keating Subject: Re: c++/10569: use typedef type as return from main yields warning Reply-To: Geoff Keating X-SW-Source: 2003-04/txt/msg01471.txt.bz2 List-Id: The following reply was made to PR c++/10569; it has been noted by GNATS. From: Geoff Keating To: bangerth@dealii.org Cc: 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 Date: 30 Apr 2003 12:16:42 -0700 bangerth@dealii.org writes: > 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. The standard does permit this. Typedefs are just names for existing types, not new types, and so can be used anywhere that the type could be used. -- - Geoffrey Keating