Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!elroy.jpl.nasa.gov!ncar!gatech!udel!rochester!kodak!uupsi!cmcl2!adm!smoke!gwyn
From: gwyn@smoke.brl.mil (Doug Gwyn)
Newsgroups: comp.lang.c
Subject: Re: varargs -> varargs mystery
Message-ID: <16175@smoke.brl.mil>
Date: 17 May 91 03:43:52 GMT
References: <3110@cirrusl.UUCP> <16068@smoke.brl.mil> <1991May16.173145.2440@philmtl.philips.ca>
Organization: U.S. Army Ballistic Research Laboratory, APG, MD.
Lines: 8

In article <1991May16.173145.2440@philmtl.philips.ca> ray@philmtl.philips.ca (Ray Dunn) writes:
-What I've found this means in practice is that when you write a varargs
-function it's usually best to write it as *two* functions, fn and vfn,
-where fn creates the va_list and passes it vfn where the work is actually
-done.
-Both fn and vfn can then be called as required.

Exactly right.