Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!decwrl!decvax!ucbvax!agate!aurora!eos!ames!nrl-cmf!cmcl2!brl-adm!brl-smoke!gwyn
From: gwyn@brl-smoke.ARPA (Doug Gwyn )
Newsgroups: comp.lang.c
Subject: Re: variable number of arguments
Message-ID: <7376@brl-smoke.ARPA>
Date: 28 Feb 88 05:17:39 GMT
References: <1608@byzantium.UUCP> <1632@mhres.mh.nl> <51@vsi.UUCP> <7361@brl-smoke.ARPA> <1078@pasteur.Berkeley.Edu>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 16
Keywords: arguments, varargs

In article <1078@pasteur.Berkeley.Edu> dheller@cory.Berkeley.EDU.UUCP (Dan Heller) writes:
>I refute that claiming that it shouldn't be necessary to worry about it.

But since in fact it is necessary to worry about it, that's not a good
refutation.

>A good compiler will pass the arguments correctly and the architecture
>should be completely transparent to the programmer.

Sorry, in order for the architecture to be "transparent" across all
systems, you have to use varargs as I said.

>Declaring the _known_ arguments makes the code more easily linted and
>more easily understood by others readers.

Which doesn't do much good if it won't run.