RE: [sv-ac] new mantis item and proposal #1641

John,


I like your example, but having severity system tasks
called upon sequence matches to affect the severity of
the overall property might have a few problem.

One issue is that this feature is enabled on the
match of all sequences.  Thus it could occur within
covers as well as assertions.  What should be done
in that case?

Could there be any "surprising" situations that arise
in the end user's point of view?

Are there other oddball cases that need to be considered
and specified?

I'm tempted to suggest that another Mantis item should be
opened on this issue.  But if agreement can be reached quickly,
it should be fine to incorporate this extension into Manisha's
proposal.

Regards,
Doug Warmke 

> -----Original Message-----
> From: owner-sv-ac@server.eda.org 
> [mailto:owner-sv-ac@server.eda.org] On Behalf Of John Havlicek
> Sent: Tuesday, October 24, 2006 5:17 AM
> To: sv-ac@server.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
>