[sv-ac] Updated version of 2328

Hi all:

I have uploaded an updated version of 2328. Below is a summary of the changes. Please let me know if there are additional concerns. Also, if anyone has an answer to my question regarding event.triggered that would be great.

Thanks,
Scott

-Manisha, Dmitry: Clarify the sentence about dynamic variables in the proposal.
REPLACED
If the expression references a dynamic variable and the value of that variable is not defined when the value is captured for evaluation, then the tool shall generate an error message. The value captured for evaluation shall be maintained until assertion evaluation is complete even if the object is destroyed.
WITH (based on language in 13.5.2 as suggested in the meeting)
If an expression references an element of a dynamic data type that does not exist when the value of the element is captured for assertion evaluation, then the tool shall generate an error message. Any dynamic data type elements captured for assertion evaluation shall continue to exist within the scope of the assertion until the assertion evaluation completes.

-Manisha, Ed: Add an example clarifying the incurred penalties for sampling large dynamic variables.

Added.

Scott: Will disallow class members in assertions for the time being.
ADDED: - Expressions shall not reference class properties.

Dmitry: Need to add an explanation of event.triggered sampling.

ADDED at the beginning of the proposal. I did not add a code example. This was requested during the SV-AC meeting. I am happy to add an example or enhance a current example to incorporate event.triggered, but I am not sure what concept should be illustrated. What is unique about event.triggered that should be clarified/highlighted in the example?

Dmitry: Need to mention that this proposal is written on top of 3213.
ADDED: Note to the editor: This proposal should be applied after mantis 3213. It makes changes using the text in 3213.

-Expanded the timing example with additional explanation.

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