Hi Yaniv: I am reviewing 2173 for Champions. There are some semicolon problems that need to be fixed. 1. When property_spec is used in a concurrent assertion statement, no semicolon is required. This needs to be preserved for backward compatibility. Under this proposal, a semicolon is required for the property_statement form "property_expr ;". 2. In a property declaration, there is an explicit ";" after the property_spec. This proposal will result in two semicolons when the property_statement has the form "property_expr ;". A possible solution is to have both property_spec and property_statement_spec, where the former is unchanged, i.e. property_spec ::= [clocking_event] [disable iff (expression_or_dist)] property_expr and the latter requires a property_statement in place of the property_expr. Then use property_spec in the assertion statements (unchanged) and use property_statement_spec in the property declaration, getting rid of the explicit semicolon there. J.H. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Wed Mar 12 05:09:35 2008
This archive was generated by hypermail 2.1.8 : Wed Mar 12 2008 - 05:10:14 PDT