Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utcs!mnetor!seismo!brl-adm!brl-smoke!smoke!gwyn@BRL.ARPA
From: gwyn@BRL.ARPA
Newsgroups: net.lang.c
Subject: Re:  Another printf-type question
Message-ID: <2236@brl-smoke.ARPA>
Date: Tue, 15-Jul-86 02:06:24 EDT
Article-I.D.: brl-smok.2236
Posted: Tue Jul 15 02:06:24 1986
Date-Received: Tue, 15-Jul-86 23:17:44 EDT
Sender: news@brl-smoke.ARPA
Lines: 16

invprintf(fmt,_0,_1,_2,_3,_4,_5,_6,_7,_8,_9)

is not a portable solution.  In some cases an attempt to invoke
it with a small actual parameter count can even lead to abnormal
process termination.

The reason <varargs.h> or <stdarg.h> exist is to provide the
hooks necessary for implementation of a portable solution;
the other half of the solution requires something like the
v*printf() functions.

The fellow asked the great gurus what he *should* have done.
Why do you feed him that garbage in return?  If it's to show
us that you don't believe in writing portable code, we knew
that already from your ravings about how the VAX is the only
sane architecture.