Sorry for the noise, but reading 1326, I remember that we do not want to allow match item on Boolean abbreviation. Still, the syntax looks over restricted to me. I think we should just put a note saying that match item are not allowed on Boolean abbreviation. This is not for the 2009 version, but I think we need to keep record on that. Doron ________________________________ From: owner-sv-ac@server.eda.org [mailto:owner-sv-ac@server.eda.org] On Behalf Of Bustan, Doron Sent: Monday, October 27, 2008 5:43 AM To: sv-ac@server.eda.org Subject: [sv-ac] match item All, I am looking at 16.7 and there are some syntactic restrictions on the use of match item that I do not understand. If I understand correctly there are only two syntax productions that allow adding match items: | ( sequence_expr {, sequence_match_item } ) [ sequence_abbrev ] | first_match ( sequence_expr {, sequence_match_item} ) So, one cannot write "(a ##1 b, v = 1)" but can write "(a ##1 b, v = 1) [*1]" which is semantically equivalent. As far as I understand, we can always use the [*1] to do add the match item, so there is no semantic meaning to the syntactic restrictions. Does anyone remember a reason for that? Or is it something we overlooked? Thanks Doron --------------------------------------------------------------------- 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 <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 Sun Oct 26 20:54:58 2008
This archive was generated by hypermail 2.1.8 : Sun Oct 26 2008 - 20:55:10 PDT