RE: [sv-ac] Feedback for Mantis 3295 proposal

Hi Tom,

I'll make the changes. About the tasks defined in 20.12, they can also be mapped to $assertcontrol with new values for contro_type. So, far we have not discussed mapping them. We can discuss it in today's meeting and then I can make appropriate change if there are any.

Thanks.
Manisha

-----Original Message-----
From: owner-sv-ac@eda.org [mailto:owner-sv-ac@eda.org] On Behalf Of Thomas J Thatcher
Sent: Tuesday, March 22, 2011 6:29 AM
To: sv-ac@eda.org
Subject: [sv-ac] Feedback for Mantis 3295 proposal

Hi Manisha,

I have the following suggestions:

1. Change
        Off: shall stop the checking of all . . .
      To
        Off: A value of 2 for this argument shall stop the checking of all . . .

   Similarly,
      Change
        Kill: Shall abort the execution . . .
      To
        Kill: A value of 3 for this argument shall abort the execution . . .

      Change
        On: shall reenable the ..
      To
        On: A value of 1 for this argument shall reenable the . . .

2. An editorial change:
     Change
        If fourth argument is not specified ,it defaults to 0.
     To
        If the fourth argumet is not specified, it defaults to 0.

Now for one other question:
Clause 20.12 defines assertion action control system tasks:
        $assertpasson
        $assertpassoff
        $assertfailon
        $assertfailoff
        $assertnonvacuouson
        $assertnonvacuousoff

Are these assertion control tasks just other forms of the new
$assertcontrol system task? i.e. Do you need to add six more control
types to your new Table 20.5?

Tom

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.