Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!mp.cs.niu.edu!ux1.cso.uiuc.edu!news.iastate.edu!john
From: john@iastate.edu (Hascall John Paul)
Newsgroups: comp.lang.c
Subject: Re: :? unique? (was Re: cond. op. on ='s LHS)
Message-ID: <1991Feb25.034628.28422@news.iastate.edu>
Date: 25 Feb 91 03:46:28 GMT
References: <1991Feb23.215538.10212@Think.COM> <1991Feb24.022225.10838@news.iastate.edu> <1991Feb24.085322.7800@Think.COM>
Sender: news@news.iastate.edu (USENET News System)
Organization: Iowa State University, Ames, IA
Lines: 22

In article <1991Feb24.085322.7800@Think.COM> barmar@think.com (Barry Margolin) writes:
}In article <1991Feb24.022225.10838@news.iastate.edu> john@iastate.edu (Hascall John Paul) writes:
}>In article <1991Feb23.215538.10212@Think.COM> barmar@think.com (Barry Margolin) writes:
}>}What about the function call operator?  It takes an arbitrary positive
}>}number of parameters.

}>   Non-negative.         ;-)

}I stand by my original statement.  The function call operator always has at
}least one parameter: a function or function pointer.

 I stand by my original statement.  ... but it has ...
 ... at least one operand: a function pointer.

  Followups to alt.nomenclature.nit-pick    ;-)

John
--
John Hascall                        An ill-chosen word is the fool's messenger.
Project Vincent
Iowa State University Computation Center                       john@iastate.edu
Ames, IA  50011                                                  (515) 294-9551