1. Mantis 2693 Ballot comment #138: Virtual interface in coverpoint? Yes _X__ No ___ Abstain ___ 2. Mantis 2598 2.1 Ballot comment #52 How can class type parameters be accessed? Now handled by Mantis 2575 Close as a duplicate of 2575 Yes _x__ No ___ Abstain ___ 2.2 Ballot comment #64 Access to class type parameters Now handled by Mantis 2575 Close as a duplicate of 2575 Yes _x__ No ___ Abstain ___ 3. Mantis 2575 3.1 Ballot comment #50 Is this.<param_name> or handle.<param_name> allowed for class parameters or local parameters of a class? Yes _x__ No ___ Abstain ___ 3.2 Ballot comment #52 How can class type parameters be accessed? Yes _x__ No ___ Abstain ___ 3.3 Ballot comment #55 Related to specification of hierarchical class methods for triggerring. Is this limited to only static class methods or user can specify object specific method as well. What happens if the object is not existing? Yes ___ No _x__ Abstain ___ I don't think Mantis 2575 address ballot comment #55. 3.4 Ballot comment #59 can :: or . be applied to access a class parameter or a param declared inside the class? Yes _x__ No ___ Abstain ___ 3.5 Ballot comment #64 Access to class type parameters Yes _x__ No ___ Abstain ___ 4. Mantis 2608 Ballot Comment #59 :: access and dot access to class value parameters and local parameters should be allowed Now handled by Mantis 2575 Close as a duplicate of 2575 Yes _x__ No ___ Abstain ___ 5. Mantis 2746 Ballot comment #113 "others" coverage bin example Yes _x__ No ___ Abstain ___ 6. Mantis 2749 Ballot comment #53 class properties and methods are public Yes _x__ No ___ Abstain ___ 7. Mantis 2750 Ballot comment #121 "expression" should be "constant_expression" Yes _x__ No ___ Abstain ___ 8. Mantis 2748 Ballot comment #19 Preponed PLI region not included (but should be removed from LRM anyway as it does not really exist) No change required. See the bug note for an explanation as to why the figure does not need to be updated. Yes _x__ No ___ Abstain ___ 9. Mantis 2745 Ballot comment #111 impicit coverpoint for cross An enhancement request Move to "Status=Resolved, Resolution=Open" and add the following bug note. "The committee read and considered this feedback. the committee believes it is too broad for the scope of the draft to implement at this time but may be considered for future revisions." Yes _x__ No ___ Abstain ___ Neil -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Wed May 27 14:52:08 2009
This archive was generated by hypermail 2.1.8 : Wed May 27 2009 - 14:53:02 PDT