Bresticker, Shalom wrote: >Are you guys really disagreeing with each other? > >Shalom > > I was just looking for some clarification. The restriction that the functions should be "analog functions" probably applies to calls in initialization code in an "initial step" block within an analog block since that code is involved in solving the circuit matrix. If the code in question is setting up variables and other initial conditions prior to attempting solving the matrix (and won't be called during the solving process) then there is no requirement (that I can see) for the function calls being constant. I.e. if the code is in an initial block rather than an analog block or just in the variable declaration calls don't have to be constant. Kev. > > >>Dave Miller wrote: >> >> >>>Kevin Cameron wrote: >>> >>> >>>>>With this we could then simply use constant functions and then we >>>>>have a ready to go method to perform complex pre-simulation >>>>>initialisation. >>>>> >>>>> >>>>What's telling the compiler it's a constant function, and does it >>>>have to be? >>>> >>>> >>>Any analog user defined function who's arguments are constant >>>(parameters, numbers) is a constant function, as they can be solved >>>pre-simulation with no dependencies on a matrix etc. >>>I would love to see more use of constant analog functions, if only >>> >>> >as > > >>>an alternative to users writing function macro's to do the same >>> >>> >thing. > > >>>As with all macro's in any language, debugging them can sometimes be >>> >>> >a > > >>>challenge. >>> >>> >>I don't see the need for the function to be a constant or analog if it >>is just being used for initialization and is not inside an analog >> >> >block. > > >Received on Sun Dec 24 15:46:14 2006
This archive was generated by hypermail 2.1.8 : Sun Dec 24 2006 - 15:46:20 PST