RE: [sv-bc] Re: [sv-ec] No event triggers in functions?

Same problem with output arguments of functions, or anything local to an
automatic function. So pretty much an NBA would have to be a side-effect
to the function. 

I don't really think a method writing to a member of a class is a
side-effect, but we still don't allow NBAs to members of classes.

Dave


> -----Original Message-----
> From: owner-sv-bc@server.eda.org [mailto:owner-sv-bc@server.eda.org]
On
> Behalf Of Steven Sharp
> Sent: Wednesday, May 03, 2006 1:16 PM
> To: michael.burns@freescale.com; shalom.bresticker@intel.com
> Cc: Arturo.Salz@synopsys.com; sv-ec@server.eda.org;
sv-bc@server.eda.org
> Subject: RE: [sv-bc] Re: [sv-ec] No event triggers in functions?
> 
> 
> >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.
> 
> 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