Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!gem.mps.ohio-state.edu!ginosko!uunet!crdgw1!crdos1!davidsen
From: davidsen@crdos1.crd.ge.COM (Wm E Davidsen Jr)
Newsgroups: comp.lang.c
Subject: Re: on the fringe of C syntax/semantics
Message-ID: <789@crdos1.crd.ge.COM>
Date: 4 Oct 89 13:15:19 GMT
References: <80100001@bonzo>
Reply-To: davidsen@crdos1.UUCP (bill davidsen)
Organization: GE Corp R&D Center
Lines: 19

In article <80100001@bonzo>, roy@bonzo.sts.COM writes:
|  
|  Here are a couple questions that come up in conjunction with using the
|  'varargs' series of function calls.  When calling the va_arg()
|  function, the 2nd parameter is supposed to be simply a type, such as
   ^^^^^^^^^ nope, macro. Does that make it clear?

It does something like this:
	#define va_arg(list,mode) list+=sizeof(mode),((mode *)list)[-1]
or somthing along those lines.

|  '(int *())' and '(int ())' were two tries at declaring a general function

  If I understand the question, you want (int(*)())
-- 
bill davidsen	(davidsen@crdos1.crd.GE.COM -or- uunet!crdgw1!crdos1!davidsen)
"The world is filled with fools. They blindly follow their so-called
'reason' in the face of the church and common sense. Any fool can see
that the world is flat!" - anon