Hi, So far I have gone through issues 1-19. I have comments on a few: > 13. 2659 Yes _x_ No ___ Abstain ___ > SV-AC Backward compatibility issue with sequence property Editorial note: "IEEE Std 1800-2005 semantics for a sequence_expr is changed" will sound better if "is changed" is changed to "were changed". > 14. 2541 Yes _x_ No ___ Abstain ___ > SV-AC syntax errors - missing parenthesis Parentheses are also missing near the end of 16.15.2: "a1:assume property @(posedge clk) req dist {0:=40, 1:=60} ;" The editor has agreed to fix it. > 19. 2621 Yes ___ No ___ Abstain ___ > SV-CC Ballot comment #155 vpiSize should return an > error when applied > on a vpiFunction returning string The proposal says, "If the vpiSize of the vpiReturn variable is defined (see 37.17, detail 9) and can be determined without evaluating the function (see 37.3.5), vpiSize for the function shall return the same value as vpiSize for the vpiReturn variable... For all other cases the behavior of vpiSize is undefined." 37.3.5 talks specifically about evaluating functions with side effects, not about function evaluation without side effects. Is this consistent? Thanks, Shalom --------------------------------------------------------------------- Intel Israel (74) Limited This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Wed May 13 20:20:07 2009
This archive was generated by hypermail 2.1.8 : Wed May 13 2009 - 20:20:07 PDT