The original sections on interfaces and interface ports were mostly examples, and did not clearly explain much. It was always my understanding that this was legal even though it may not be clearly stated in the LRM. In 3048 I raised the issue of binding of interface names in interface port declarations as well as virtual interface variables. This is not specified in the LRM either and becomes an issue for customers when they have interfaces of the same name in different libraries. From: owner-sv-bc@eda.org [mailto:owner-sv-bc@eda.org] On Behalf Of Bresticker, Shalom Sent: Wednesday, June 05, 2013 7:41 AM To: sv-bc@eda.org Cc: Guy Nakibly (guy@annapurnalabs.com) Subject: [sv-bc] Connection of parameterized interfaces Can a parameterized interface be connected using a named interface type port ? The LRM describes parameterized interfaces in 25.8. However, the only example of connection of such an interface uses a generic interface port. And 23.3.3.4 says, "If a port declaration has a generic interface type, then it can be connected to an interface instance of any type. If a port declaration has a named interface type, then it shall be connected to an interface instance of the identical type." Usually, parameter values are considered part of the type. On the other hand, there are indications in http://www.eda-stds.org/mantis/view.php?id=905 and http://www.eda-stds.org/mantis/view.php?id=2502 that people think that a named interface port can be used and get the actual parameter values at elaboration time from the connected interface. And some tools do support such connections. So what is correct? Thanks, Shalom Shalom Bresticker Intel LAD DA, Jerusalem, Israel +972 2 589 6582 (office) +972 54 721 1033 (cell) http://www.linkedin.com/in/shalombresticker --------------------------------------------------------------------- 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 Wed Jun 5 16:19:32 2013
This archive was generated by hypermail 2.1.8 : Wed Jun 05 2013 - 16:19:39 PDT