>Then why not just remove the distinctions between tasks and functions >and be done with it? If you did that, you would have to add the concept of a "no delay" function back in some other way. There are places where functions with delays could not be allowed without causing serious problems for simulation. Relaxing the restrictions on side-effects is less of a problem. I don't know how valuable their protection is to designers. If they are seen as too valuable to give up, I suppose one compromise would be to remove the restrictions only on class method functions. Steven Sharp sharp@cadence.comReceived on Wed Apr 26 16:57:11 2006
This archive was generated by hypermail 2.1.8 : Wed Apr 26 2006 - 16:57:16 PDT