Hi John, That is, $error being the task itself. You last version in which the task represents a truth value looks nice, but it almost circumvents the need for action block. Also, if it is a property, does first match / fail rule apply or all threads that reach that point at the same time? What if they contradict each other? ed > -----Original Message----- > From: owner-sv-ac@eda.org [mailto:owner-sv-ac@eda.org] On > Behalf Of John Havlicek > Sent: Tuesday, October 24, 2006 8:17 AM > To: sv-ac@eda-stds.org > Subject: Re: [sv-ac] new mantis item and proposal #1641 > > Hi Ed: > > Actually, I was referring to calling $error in the property. See > my last post. > > I have also wondered about severity tasks that are not called > directly in a match item or in an action block. > > I think the intention of the current 1641 proposal is that the > action block rules apply only if the severity task is called > directly from the action block. > > I can imagine people wanting to call a user-defined error > handling task that itself might sort out which severity > task to call, and for that it seems it would be more useful > to have the action block rules apply than the sequential code > rules. > > J.H. > > > Hi Manisha, > > > > I think that John meant calling $error etc. from a task > that is called > > from within a sequence. > > > > ed=20 >Received on Tue Oct 24 06:57:37 2006
This archive was generated by hypermail 2.1.8 : Tue Oct 24 2006 - 06:57:41 PDT