Path: utzoo!attcan!uunet!tut.cis.ohio-state.edu!mailrus!uflorida!haven!adm!smoke!gwyn From: gwyn@smoke.BRL.MIL (Doug Gwyn) Newsgroups: comp.lang.c Subject: Re: va_list used inKeywords: va_list, X3J11, vfprintf Message-ID: <10720@smoke.BRL.MIL> Date: 12 Aug 89 23:49:11 GMT References: <1140@midgard.Midgard.MN.ORG> Reply-To: gwyn@brl.arpa (Doug Gwyn) Organization: Ballistic Research Lab (BRL), APG, MD. Lines: 15 In article <1140@midgard.Midgard.MN.ORG> dal@midgard.Midgard.MN.ORG (Dale Schumacher) writes: >In the header file, the v[fs]printf() function prototypes >use the va_list type, but va_list is not defined anywhere in . This is a frequent question. The answer is that the implementor of must not attempt to use "va_list" but instead should just use the actual type expressed without use of typedefs. >The standard also seems to imply that header files do not include each >other. Is this the case? Yes, in effect each standard header contains exactly what the Standard says it does and nothing else. (Identifers specifically stated as reserved for implementation use may also be defined/declared in standard headers. Warning! Use __iob or _Iob, not _iob, in your .)