[sv-ac] RE: solution with case

Hi John,

I think Bassam meant that the problem is with the VPI only - my
intention was to keep the BNF as it is currently in the proposal but
just make changes in the VPI . the VPI wouldn't have  property statement
at all - but that is apparently OK, if..else would remain as operator
inside property expr (VPI) and "property case" would be added as another
option for property expr VPI object.


regarding changing the BNF, I think by your definition property
statement is redundant, case can go inside property expr, if property
declaration would be changed such that semicolon is made optional and
adding semicolon would be allowed in property expression.

property property_identifier [ ( [ property_port_list ] ) ] ;
{ assertion_variable_declaration }
property_spec semicolon_or_null
endproperty [ : property_identifier ]

and also add:
property_expr::=
  |
  property_expr ;
  |

semicolon_or_null::=
  ; | 


I think by those rules you can write without semicolon after
endcase,if..else stays syntactically backwards compatible (but also
semicolons are allowed), no problem with nested cases, also no need for
semicolon if one property_expr inside property .. endproperty.



Yaniv



-----Original Message-----
From: John Havlicek [mailto:john.havlicek@freescale.com] 
Sent: Monday, February 18, 2008 19:32
To: Fais Yaniv
Cc: sv-ac@eda.org
Subject: solution with case

Hi Yaniv:

We should also look for a solution that gives most of the syntax that we
want and leaves the VPI backward compatible.

To do this, we may need to sacrifice changing the property_spec, in
which case semicolon would still be required after top-level endcase in
a property declaration.

We could leave if-else in property_expr and also put it in
property_statement.  For the if-else in property_statement, we could ask
the "then" and "else" parts both to be property statements.  This would
force uniformity between them.

We would leave

   property_expr ::=
      ...
      | property_statment
      ...

J.H.




   

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.