Hi all, I would like to get early feedback on a proposal that I am writing to clarify the statistic counters that are associated with assertions. The current chapter 17 LRM specifies that these counters must exist for cover statements only, yet 29.1.2 text is written as though all counters are available for all assertions. I think there is value in having the statistic counters for all assertions. For assert and assume statements, it may be useful to know the number of failures and passes. A failure indicates a bug of some kind while a pass is confirmation that the stimulus tested the behavior. For cover properties, only the number of non-vacuous passes may be of significance. I would like to propose that a minimal set of pass/fail counts be required for all assertions (immediate and concurrent), and that others can be optionally provided if desired. And only the pass counter is required for cover properties (others are optional). Are there any objections to this principal? The other part of the proposal is to clarify how to distinguish a property_spec from a sequence_expr. (this is Mantis 1768) A property_spec that is just a single sequence_expr shall be interpreted as a sequence, whereas a property_spec that is not just a sequence_expr shall be interpreted as a property. For example, an expression that contains an implication operator or a disable iff term, is considered a property. A property instance that is just a single sequence_expr is interpreted as a sequence (assuming there is not any default disable iff clause). Does this sound ok? Lisa -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Mon May 7 11:02:56 2007
This archive was generated by hypermail 2.1.8 : Mon May 07 2007 - 11:03:20 PDT