I believe that port coercion can only happen if both sides of the connection are nets, not just if the port declarations are nets. As soon as one side has a variable, then the rules for connections to variables indicate that an implicit continuous assignment is created, thus the direction can no longer be coerced. This section really belongs in 22.3.3.3 Port connection rules for nets, just before mentioning additional rules in 22.3.3.7 or you could put this in the latter section. Port coercion is really due in part to the fact that the port is collapsed. Dave ________________________________ From: owner-sv-bc@server.eda.org [mailto:owner-sv-bc@server.eda.org] On Behalf Of Bresticker, Shalom Sent: Friday, October 19, 2007 12:13 AM To: sv-bc@server.eda.org Subject: [sv-bc] Mantis 1573 I revised the proposal to Mantis 1573 to apply only to net ports, not to variable ports. See Mantis 1744. Shalom <<1573_D4_port coercion.V2.htm>> Shalom Bresticker Intel Jerusalem LAD DA +972 2 589-6852 +972 54 721-1033 --------------------------------------------------------------------- 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. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Fri Oct 19 09:42:44 2007
This archive was generated by hypermail 2.1.8 : Fri Oct 19 2007 - 09:42:59 PDT