11. 0001855 Yes _X_ No ___ Abstain ___ SV-AC issues with 22.10 after 1722 duplicate 13. 0001804 Yes _X_ No ___ Abstain ___ SV-AC Add abiltiy to require equiv types for typed formal args Voice vote on 2007-08-07 not to address this since lint tools can check such conditions 17. 0001737 Yes ___ No _X_ Abstain ___ SV-AC Incomplete fix from 1381 Resolved by e-mail ballot on 2007-05-28, 7y/0n/4a JH justification: This proposal has not been properly colored to show which parts of the existing text should be retained and which stricken. JH friendly amendments: 1. I think that "The enabling condition assumed from the context" should be "The enabling condition inferred from the context". 2. I think that "assert property", "assume property", and "cover property" should be in bold Courier as compound keywords. 3. The LRM is moving to a style in which non-terminals of the syntax are referenced in italics, preserving underscores, rather than Courier. This affects "property_expr" and "property_spec". 4. The font of "case" in "Similarly, the enabling condition is also inferred from case statements" should be bold Courier. 5. 1768 has already been approved. I think that this proposal should be updated to explain inferred enabling conditions for "cover sequence". I think that ##0 should be used for this since the negation dual formulation for "cover property" will not be legal syntax. This will also require some reworking of various places that talk about property_expr and property_spec to be inclusive of the body of a "cover sequence", which may have a "disable iff" clause, but for which there is not an analogous non-terminal "sequence_spec". And the examples may want to illustrate the inference for "cover sequence". 6. The proposal has been crafted carefully so that the transformation inserts the inferred enabling condition after any "disable iff" clause, but this may be a bit too subtle for readers. Consider mentioning this point, perhaps with an example. 18. 0001731 Yes _X_ No ___ Abstain ___ SV-AC Sampled value functions with arbitrary clocks Passed by e-mail ballot 2007-07-03, 9y/0n/2a JH friendly amendments: 1. The added text in Clause 16 and Annex F needs to be in blue. 2. The example in 16.8.3 should use Courier font. For example, I see the first word "bit" in a bold Roman font. The other bold words are the same way. And "&&" is not in Courier. I'm not sure about the punctuations (",", ";"). The source of the proposal may be using an obscure or variant font. I recommend switching to a more common font. 3. In the paragraph after the example in 16.8.3, the font is not consistent in referencing identifiers from the example. They should all be in Courier. 4. In the new section F.2.3.6, the deprecated form "sampled(e,c)" should not appear. 5. In the new section F.2.3.6, Courier font should be used for terminals, such as "1", "0", punctuations (",", ";"), parentheses, "&&", and "=". 6. In the new text in F.4.2, Courier font should be used for terminals in the sequence expression, such as parentheses, "&&", "##1", brackets, etc. 7. I think that the more precise language from 1550 with cross references should be used in F.4.2 to discuss the case when $past looks back too far and the initial values are used. 20. 0001681 Yes _X_ No ___ Abstain ___ SV-AC Introduce global clocking New proposal was uploaded - redoing email vote (didn't reach quorum) 29. 0001383 Yes _X_ No ___ Abstain ___ SV-AC Property coverage definition Duplicate of 805 JH comment: SV-AC still need to vote on the state change to "resolved,won't fix". This is another process mistake for which I am to blame. Approval by the Champions should be conditional on the SV-AC vote. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Tue Sep 18 12:20:19 2007
This archive was generated by hypermail 2.1.8 : Tue Sep 18 2007 - 12:20:26 PDT