We have heard similar requests in the past from more than 1 user to
have $coveroff likes. I would personally opt for $coveroff than adding
an arg to the $assertoff for ease of use & self documenting code.
Srini
www.cvcblr.com
On Thu, Nov 25, 2010 at 5:07 PM, Kulshrestha, Manisha
<Manisha_Kulshrestha@mentor.com> wrote:
> Hi Dimitry,
>
> I have filed a new mantis 3295. Please find out from the WG if we can
> work on it.
>
> Thanks.
> Manisha
>
> -----Original Message-----
> From: Bresticker, Shalom [mailto:shalom.bresticker@intel.com]
> Sent: Thursday, November 25, 2010 4:52 PM
> To: Kulshrestha, Manisha; sv-ac@eda.org
> Subject: RE: assertion control system tasks
>
> I agree this would be very useful.
> I recently had such a need.
>
> Regards,
> Shalom
>
>> -----Original Message-----
>> From: owner-sv-ac@eda.org [mailto:owner-sv-ac@eda.org] On Behalf Of
>> Kulshrestha, Manisha
>> Sent: Thursday, November 25, 2010 1:01 PM
>> To: sv-ac@eda.org
>> Subject: [sv-ac] assertion control system tasks
>>
>> Hi,
>>
>> Currently assertion control system tasks control all kinds of
>> assertions (assert, cover and assume) and there is no way to choose
> any
>> specific type. Sometimes it is useful to be able to control only
>> certain types e.g. sometimes user want to only run asserts and no
>> covers as they are not interested in coverage. It is not possible to
>> achieve this with current set of functions. Proabably by adding a new
>> argument to existing functions, we can achieve this enhanced
>> functionality.
>>
>> Dimitry, I am just wondering if it is possible to include this
>> enhancement in the current PAR ? I'll file a mantis but it would be
>> good to consider it in this PAR.
>>
>> Thanks.
>> Manisha
>
> ---------------------------------------------------------------------
> Intel Israel (74) Limited
>
> This e-mail and any attachments may contain confidential material for
> the sole use of the intended recipient(s). Any review or distribution
> by others is strictly prohibited. If you are not the intended
> recipient, please contact the sender and delete all copies.
>
>
> --
> 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.Received on Thu Nov 25 04:34:11 2010
This archive was generated by hypermail 2.1.8 : Thu Nov 25 2010 - 04:34:18 PST