[sv-ac] FW: Query on Formal Syntax of property_case_item [SV 2012]

From: Bresticker, Shalom <shalom.bresticker@intel.com>
Date: Mon Oct 06 2014 - 23:34:11 PDT
From: owner-sv-bc@eda.org [mailto:owner-sv-bc@eda.org] On Behalf Of Steven Sharp
Sent: Tuesday, October 07, 2014 09:16
To: Datta, Kausik; sv-bc@eda.org
Subject: [sv-bc] RE: Query on Formal Syntax of property_case_item [SV 2012]

This appears to be an unintentional side-effect of the changes for Mantis 3525.  I have filed a new Mantis 5038.

From: owner-sv-bc@eda.org<mailto:owner-sv-bc@eda.org> [mailto:owner-sv-bc@eda.org] On Behalf Of Datta, Kausik
Sent: Monday, October 06, 2014 9:30 AM
To: sv-bc@eda.org<mailto:sv-bc@eda.org>
Subject: [sv-bc] Query on Formal Syntax of property_case_item [SV 2012]

Hi,

In SV 2012 LRM the semicolon [;] in property_case_item is optional, this means writing two expressions without any symbol in between is valid in SV.

For example  the following syntax is a valid one as per LRM

case (expr1) expr2 : expr3 expr4 : expr5 endcase
where there is no delimiter in between expr3 and expr4.

Is this an intended syntax? But all examples in this area in LRM has [;] after property_expr.

Formal Syntax:
property_expr ::= case ( expression_or_dist ) property_case_item { property_case_item } endcase

property_case_item::=
expression_or_dist { , expression_or_dist } : property_expr [ ; ]
| default [ : ] property_expr [ ; ]

Thanks
Kausik Datta


--
This message has been scanned for viruses and
dangerous content by MailScanner<http://www.mailscanner.info/>, and is
believed to be clean.

--
This message has been scanned for viruses and
dangerous content by MailScanner<http://www.mailscanner.info/>, and is
believed to be clean.
---------------------------------------------------------------------
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 Mon Oct 6 23:34:41 2014

This archive was generated by hypermail 2.1.8 : Mon Oct 06 2014 - 23:35:26 PDT