Re: Confusion over connect_resolution rule

From: Surya Pratik Saha <spsaha_at_.....>
Date: Tue Aug 25 2009 - 05:01:32 PDT
Hi Marq,
I have filed Mantis 2860 for that.
Regards
Surya


-------- Original Message  --------
Subject: Re:Confusion over connect_resolution rule
From: Marq Kole <marq.kole@nxp.com>
To: Surya Pratik Saha <spsaha@cal.interrasystems.com>, verilog-ams@server.eda.org <verilog-ams@eda.org>
Date: Tuesday, August 25, 2009 4:46:08 PM

Hi Surya,

 

The use of the vertical bar in this grammar rule seems to assume different precedence than in other rules. Although one could add parentheses to the rule to fix the precedence I think your proposal is more transparent. I suggest you make a Mantis item for it.

 

Cheers,

Marq

 

From: owner-verilog-ams@server.eda.org [mailto:owner-verilog-ams@server.eda.org] On Behalf Of Surya Pratik Saha
Sent: Tuesday 25 August 2009 12:30
To: verilog-ams@server.eda.org
Subject: Confusion over connect_resolution rule

 

Hi,
I have a confusion on connect_resolution rule. It is defined as:

connect_resolution ::= connect discipline_identifier { , discipline_identifier } resolveto // from A.1.8
discipline_identifier
| exclude
;


As per the position of '|', it seems to me connect_resolution can be resolved to either:
connect discipline_identifier { , discipline_identifier } resolveto discipline_identifier

or

exclude ;


But by the example it seems to me, after resolveto keyword, either discipline_identifier or exclude can be present. So the rule should be rewritten as:
connect_resolution ::= connect discipline_identifier { , discipline_identifier } resolveto discipline_or_exclude ;

discipline_or_exclude ::= discipline_identifier
| exclude

Please correct me if I am wrong.

-- 
Regards
Surya


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



--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean. Received on Tue Aug 25 05:03:47 2009

This archive was generated by hypermail 2.1.8 : Tue Aug 25 2009 - 05:04:11 PDT