Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!unmvax!ncar!ames!oliveb!3comvax!bridge2!auspex!guy
From: guy@auspex.UUCP (Guy Harris)
Newsgroups: comp.lang.c
Subject: Re: varargs and scanf
Keywords: vfprintf, ANSI C,...
Message-ID: <939@auspex.UUCP>
Date: 3 Feb 89 18:55:13 GMT
References: <1494@zen.UUCP> <9553@smoke.BRL.MIL> <1927@bingvaxu.cc.binghamton.edu>
Reply-To: guy@auspex.UUCP (Guy Harris)
Organization: Auspex Systems, Santa Clara
Lines: 11


 >>I'm not sure how useful v*scanf() would be; I've never felt the need
 >>for it, though.
 >
 >In Turbo C v2.0, *scanf() appears to fail for a few arguments (>3?), but
 >the v*scanf() functions provided work much better for me. 

The term generally used in descriptions of this situation, assuming you
used "*scanf" properly, is "bug"; bugs in Turbo C v2.0 aren't relevant
to the question of whether either "*scanf" or "v*scanf" are useful
enough to be included in the ANSI C standard.