From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18622 invoked by alias); 10 Jun 2003 19:06:38 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 18568 invoked from network); 10 Jun 2003 19:06:38 -0000 Received: from unknown (HELO localhost.redhat.com) (207.219.125.131) by sources.redhat.com with SMTP; 10 Jun 2003 19:06:38 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 6676F2B63 for ; Tue, 10 Jun 2003 15:06:34 -0400 (EDT) Message-ID: <3EE62C3A.5000302@redhat.com> Date: Tue, 10 Jun 2003 19:06:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030223 X-Accept-Language: en-us, en MIME-Version: 1.0 To: gdb@sources.redhat.com Subject: int foo (); vs int foo (void); Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-06/txt/msg00170.txt.bz2 Ok, so I knew there was a reason for prefering: > static void > foo (void) > { > } over > static void > foo () > { > } other than that `the former is strict ISO C'. -Wmissing-prototypes gets grumpy if it sees the second form. I'd assume that the corresponding ARI check was added as a cheap -Wmissing-prototypes check. enjoy, Andrew