[sv-cc] RE: 1503 Assertion VPI update

Hi Lisa,
 
Sorry about this, can we change note on the **inst** diagrams to " .....
are redundant". In case of insts they are not same (they are those of
decl), optionally we can just change all to "....redundant".
 
Thx.
-Bassam.
 

________________________________

From: Lisa Piper [mailto:piper@cadence.com] 
Sent: Tuesday, December 18, 2007 3:00 PM
To: Jim Vellenga; Bassam Tabbara
Cc: sv-cc@eda.org; sv-ac@eda-stds.org
Subject: 1503 Assertion VPI update



	I have uploaded another version to Mantis.  #3 below was just
updated. Changes in the last couple of days include:
<<1503_vpi_071218.pdf>> 

1.      Per Jim's discussion, the notes for each callback were replaced
with a paragraph at the end that states what is possible.

2.      variables was moved from property spec to property declaration,
which is consistent with the BNF and examples in the text.

3.      vpiDefFile and vpiDefLineNo were deleted from property
declaration, property instance, sequence instance, assertion, property
spec, and sequence declaration and the note added:  vpiDefFile and
vpiDefLineNo are deprecated because they are the same as vpiLineNo and
vpiFile

4.      The issues of a) not being able to access properties and
sequences that are not instantiated and b) not being able to determine
the scope in which they are defined was fixed,   Specifically, property
declaration and sequence declaration was added to the 36.11 scope
diagram and to the clocking block diagram.  In the process, it was also
noticed that the clocking block diagram should not have had concurrent
assertion so that was removed (you can declare properties and sequences
in clocking blocks but not assert them).


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