Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!yale.edu!cmcl2!adm!smoke!gwyn
From: gwyn@smoke.brl.mil (Doug Gwyn)
Newsgroups: comp.std.c
Subject: Re: <varargs.h> vs. function prototypes
Keywords: <varargs.h> usage
Message-ID: <16474@smoke.brl.mil>
Date: 21 Jun 91 05:05:21 GMT
References: <14423@dog.ee.lbl.gov> <16456@smoke.brl.mil> <14532@dog.ee.lbl.gov>
Organization: U.S. Army Ballistic Research Laboratory, APG, MD.
Lines: 7

In article <14532@dog.ee.lbl.gov> torek@elf.ee.lbl.gov (Chris Torek) writes:
>... and tell those who have trouble with it to find an ANSI C
>compiler (and/or port GCC).

You could also suggest that the necessary change to the code to attain
"portable" usage of <varargs.h> is straightforward, and let them do the
extra work if and when the occasion arises.