Path: utzoo!mnetor!uunet!husc6!hao!ames!umd5!mimsy!chris
From: chris@mimsy.UUCP (Chris Torek)
Newsgroups: comp.lang.c
Subject: Re: (So-Called) ANSI C
Message-ID: <9930@mimsy.UUCP>
Date: 22 Dec 87 22:16:12 GMT
References: <4668@pyr.gatech.EDU> <495@xyzzy.UUCP>
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 18

In article <495@xyzzy.UUCP> throopw@xyzzy.UUCP (Wayne A. Throop) writes:
>In other words, give me some example of "existing C programs broken" by
>the draft standard.  I'm not aware of any interesting cases.

<varargs.h> vs. <stdarg.h>: Both define `va_start', but the one in
<varargs.h> takes one parameter, while the one in <stdarg.h> takes two.
I think the macros in <stdarg.h> should have different names.  <varargs.h>
could then be implemented in terms of <stdarg.h> (in an implementation-
dependent way) by using, e.g.,

	#define	va_alist int fakearg, ...
	#define va_dcl
		/* the following line is implementation dependent */
	#define va_start(l) (varg_start(l, &fakearg), (l) -= sizeof(int))
	#define va_end(l) varg_end(l)
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7690)
Domain:	chris@mimsy.umd.edu	Path:	uunet!mimsy!chris