Path: utzoo!attcan!uunet!tut.cis.ohio-state.edu!ucbvax!agate!bionet!ames!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: <10769@smoke.BRL.MIL> Date: 17 Aug 89 20:44:16 GMT References: <1140@midgard.Midgard.MN.ORG> <2095@dataio.Data-IO.COM> <10739@smoke.BRL.MIL> <18684@princeton.Princeton.EDU> Reply-To: gwyn@brl.arpa (Doug Gwyn) Organization: Ballistic Research Lab (BRL), APG, MD. Lines: 16 In article <18684@princeton.Princeton.EDU> nfs@notecnirp.UUCP (Norbert Schlenker) writes: >What is allowed to define? It has to pick up , because >the prototypes in use size_t. What makes allowable >and forbidden? must not #include either. Each standard header is allowed to declare/define only those identifiers specified in the Standard, plus others specifically reserved for implementation use (e.g. "_Iobuf"). For POSIX purposes, #defining _POSIX_SOURCE before including a standard header enables the declaration/definition of the additional identifiers specified in IEEE Std. 1003.1. Other such "feature macros" could be used to further extend the names supplied by the standard headers, but I'd recommend that separate headers be used instead.