From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29958 invoked by alias); 8 Jun 2002 05:56:54 -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 29939 invoked by uid 61); 8 Jun 2002 05:56:54 -0000 Date: Fri, 07 Jun 2002 22:56:00 -0000 Message-ID: <20020608055654.29938.qmail@sources.redhat.com> To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, tmorelan@uoguelph.ca From: zack@gcc.gnu.org Reply-To: zack@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, tmorelan@uoguelph.ca, gcc-gnats@gcc.gnu.org Subject: Re: c/6968: functions that shouldn't accept arguments accept infinite arguments (eg; test() ) X-SW-Source: 2002-06/txt/msg00180.txt.bz2 List-Id: Synopsis: functions that shouldn't accept arguments accept infinite arguments (eg; test() ) State-Changed-From-To: open->closed State-Changed-By: zack State-Changed-When: Fri Jun 7 22:56:53 2002 State-Changed-Why: This is not a bug. The C standard specifies that a function declared with an empty parameter list (such as your void test ( ) ) accepts an indefinite number of arguments, not zero arguments. You must write void test ( void ) if you want to declare a function accepting zero arguments. (You may have C confused with C++. In C++ the rule is as you expected.) http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6968