🚀 go-pugleaf

In article <8s2tvu$duk$1@yin.interaccess.com>,
Kenny McCormack <gazelle@interaccess.com> wrote:
>In article <xm2F5.47$xe3.691@burlma1-snr2>,
>Barry Margolin  <barmar@genuity.net> wrote:
>...
>>Basically, K&R C had varargs.  The standardization committee designed
>>stdargs as the replacement for it.  The main difference has to do with the
>>fact that stdargs is designed to coexist with function prototypes, i.e. the
>>funcname(<fixed args>,...) notation.
>
>I can't quite parse your meaning here.  Are you saying that varargs did not
>have the "at least one fixed arg" requirement?  If so, then that's what I
>meant in the original post when I stated that it was my understanding that
>varargs was more powerful (I.e., more powerful b/c it did not have this
>requirement/limitation)

Yes, varargs didn't have that requirement.  However, since it didn't
automatically pass the number of arguments, you still had to have at least
one argument, either an initial argument that was used to determine how
many variable arguments there are (like the format string in printf, or the
count I suggested for your max() function) or a last argument with a
distinguished value.

>>I don't think there's a vscanf(), though (it's not on my Solaris 2.6
>>system).
>
>Present on Linux, but not on Solaris (AFAICT).

So it's probably not required by ISO C or POSIX (unless it's a recent
addition that hasn't made it into Solaris yet).

-- 
Barry Margolin, barmar@genuity.net
Genuity, Burlington, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.