Maybe it is enough to forbid: "tri reg" And allow all other context - this way all users will know why it is forbidden. DANiel -----Original Message----- From: owner-sv-ec@server.eda.org [mailto:owner-sv-ec@server.eda.org] On Behalf Of Steven Sharp Sent: Tuesday, December 18, 2007 8:52 PM To: Dave_Rich@mentor.com; spsaha@cal.interrasystems.com Cc: sv-ec@server.eda.org; sv-bc@server.eda.org Subject: Re: [sv-ec] 'reg' after net type It would be difficult to write the restriction that you suggest. We cannot say that the reg data type is not allowed on a net. That type is allowed on a net, as long as you use a different name for it, such as logic or a typedef defined to be the same type as reg. The current restriction is exactly what it says: the keyword reg cannot immediately follow a net type keyword. Since the initial concern was about a lexical confusion of "tri reg" and "trireg", the restriction is a purely lexical one also. Extending it to other net types to avoid the visual confusion was only done because it was so easy to specify. It was not considered important enough to be worth the complex wording that your suggestion would require, with the potential for even more confusion. Note that if we had left the restriction as just disallowing "tri reg", it probably would have been less confusing, as the reason for it would have been more obvious. Broadening the restriction makes it less clear why the restriction exists, and therefore exactly what the restriction is. Steven Sharp sharp@cadence.com -- 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 Thu Dec 20 06:00:39 2007
This archive was generated by hypermail 2.1.8 : Thu Dec 20 2007 - 06:01:12 PST