Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!crdgw1!camelback!volpe From: volpe@camelback.crd.ge.com (Christopher R Volpe) Newsgroups: comp.lang.c Subject: Re: 'void' arguments (Yet Another Feature Proposal) Message-ID: <15955@crdgw1.crd.ge.com> Date: 22 Jan 91 17:42:37 GMT References: <943@tuura.UUCP> Sender: news@crdgw1.crd.ge.com Reply-To: volpe@camelback.crd.ge.com (Christopher R Volpe) Distribution: comp Lines: 36 In article <943@tuura.UUCP>, risto@tuura.UUCP (Risto Lankinen) writes: |> |> SetThisMode( int iMode,int iValue1,int iValue2,int iValue3 ); |> |>also suppose the documentation says that 'when iMode==, then none of |>the iValue:s have any effect'. In code you'd then write: |> |> SetThisMode( ,0,0,0 ); or SetThisMode( ,, |> , ); |> |>when you could be doing... |> |> SetThisMode( ,(int)any,(int)any,(int)any ); |> How about making it a variable argument list function and calling it with SetThisMode(); or SetThisMode(,i,j,k); ??? |> |>Terveisin: Risto Lankinen |>-- |>Risto Lankinen / product specialist *************************************** |>Nokia Data Systems, Technology Dept * 2 2 * |>THIS SPACE INTENTIONALLY LEFT BLANK * 2 -1 is PRIME! Now working on 2 +1 * |>replies: risto@yj.data.nokia.fi *************************************** ================== Chris Volpe G.E. Corporate R&D volpecr@crd.ge.com