Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site brl-tgr.ARPA
Path: utzoo!linus!decvax!ittvax!dcdwest!sdcsvax!sdcrdcf!hplabs!hao!seismo!brl-tgr!gwyn
From: gwyn@brl-tgr.UUCP
Newsgroups: net.lang.c,net.unix-wizards
Subject: Re: summary of C-standards workshop at Usenix
Message-ID: <3104@brl-tgr.ARPA>
Date: Fri, 6-Jul-84 15:35:41 EDT
Article-I.D.: brl-tgr.3104
Posted: Fri Jul  6 15:35:41 1984
Date-Received: Sun, 8-Jul-84 09:00:13 EDT
References: <4013@utzoo.UUCP>, <138@wnuxb.UUCP>, <4024@utzoo.UUCP>
Organization: Ballistics Research Lab
Lines: 16
Xref: 773 1976

The difference is that
	extern int foo();
has unknown (unspecified) arguments and anything will be permitted,
whereas
	extern int foo(void,);		/* suggested */
has unknown (unspecified) arguments and anything will be permitted.
There is no difference in the meaning of the DECLARATIONS, so the
question comes down to how to properly DEFINE a "varargs" function.
I do not see how
	int foo(void,)
		{
		/* get actual parameters somehow */
		}
is going to be made to work.  Seems like some form of varargs needs
to be defined; does anyone know of a way to do this that will work
on all architectures and C runtime implementations?