Path: utzoo!mnetor!uunet!lll-winken!lll-tis!ames!pasteur!ucbvax!ucsfcgl!cca.ucsf.edu!rk9005 From: rk9005@cca.ucsf.edu (Roland McGrath) Newsgroups: comp.lang.c Subject: ANSI: va_list in Message-ID: <1228@ucsfcca.ucsf.edu> Date: 13 Apr 88 00:45:18 GMT Reply-To: roland@rtsg.lbl.gov (Roland McGrath) Organization: Hackers Anonymous International, Ltd., Inc. (Applications welcome) Lines: 22 Since the prototypes for v*printf in use the `va_list' type, that type must be defined. I see several ways that this can be handled: 1) Don't define `va_list' at all in - The Standard doesn't say defines `va_list' Sub-methods: a) If the user hasn't included just let him get error messages (OUT OF THE QUESTION) b) Only declare v*printf if is included. (maybe OK) 2) Do define `va_list' in : Sub_methods: a) Have include (probably not) - The Standard doesn't say defines all those things. b) Have define only `va_list' (maybe) I think 2b is generally good, 1b is definitely strictly-conformant, since the descriptions of v*printf say `#include '. Any words from the horse's mouth? -- Roland McGrath ARPA: roland@rtsg.lbl.gov roland@lbl-rtsg.arpa UUCP: ...!ucbvax!lbl-rtsg.arpa!roland