RE: [sv-cc] assertion API

Subject: RE: [sv-cc] assertion API
From: Bassam Tabbara (bassam@novas.com)
Date: Wed Apr 16 2003 - 14:11:18 PDT

• Next message: Joao Geada: "FW: [sv-cc] assertion API"
• Previous message: Joao Geada: "[sv-cc] Resolution of open vs dynamic arrays"
• In reply to: Francoise Martinolle: "[sv-cc] assertion API"
• Next in thread: Joao Geada: "FW: [sv-cc] assertion API"
• Reply: Bassam Tabbara: "RE: [sv-cc] assertion API"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Hi Francoise,

Yes you are right, assume/restrict did not make it in AC so only
assert/cover need stay. We already have a placeholder for "other
extensions" ....

Thx.
-Bassam.

--
Dr. Bassam Tabbara
Technical Manager, R&D
Novas Software, Inc.
http://www.novas.com
(408) 467-7893
> -----Original Message-----
> From: owner-sv-cc@server.eda.org 
> [mailto:owner-sv-cc@server.eda.org] On Behalf Of Francoise Martinolle
> Sent: Wednesday, April 16, 2003 2:01 PM
> To: sv-cc@server.eda.org
> Subject: [sv-cc] assertion API
> 
> 
> After reviewing the assertion chapter, I thought it would be 
> good to review 
> again
> the assertion API chapter.
> While doing do, I found no correlation between some of the directive 
> properties:
> vpiAssumeAssertion, vpiRestrictAssertion etc, with the 
> assertion chapter.
> 
> Should this really be in our API or should we remove some of 
> these properties directive because they are not in the 
> language anymore.
> 
> Francoise
>         '
> 

• Next message: Joao Geada: "FW: [sv-cc] assertion API"
• Previous message: Joao Geada: "[sv-cc] Resolution of open vs dynamic arrays"
• In reply to: Francoise Martinolle: "[sv-cc] assertion API"
• Next in thread: Joao Geada: "FW: [sv-cc] assertion API"
• Reply: Bassam Tabbara: "RE: [sv-cc] assertion API"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b28 : Wed Apr 16 2003 - 14:12:11 PDT