Steven Sharp wrote: >>A problem with a nonblocking assignment is that if you do an NBA to the >>function return value, it won't be returned to the expression which >>called the function. This is because the assignment is non-blocking and >>the function executes in zero time, so the function returns immediately >>with the value of the function variable before the nonblocking >>assignment finishes execution. The value is updated only afterwards. > > > Yes, this was the case that I thought of also. The behavior is strange, > since each call gets back the result assigned by the previous call. I don't agree that those are the obvious semantics. Every call should get back the result assigned by the last call in the previous iteration of the process (always block). > > One way to prevent this problem would be to allow nonblocking assignments > in functions, except to the function return value. > > Steven Sharp > sharp@cadence.com >Received on Wed May 3 15:00:43 2006
This archive was generated by hypermail 2.1.8 : Wed May 03 2006 - 15:00:48 PDT