hello BC, We recently encountered a problem where we have a bind statement that specifies binding into a target module (not a named instance), but certain parameterizations of the design can cause there to be no elaborated instance of the target module. Tools complain about this, and that's probably correct per 1800-2012 because the preamble to 23.11 says "a bind construct that is used to specify one or more instantiations" I can't find any other part of the LRM that describes how to handle this situation, nor can I find any Mantis relating to it. In practice this corner case is extremely inconvenient, and it would be much preferable for tools to report only a warning in this case. Does SV-BC have an opinion on this? If there is no obvious reason for prohibiting such "frustrated" binds, I will raise a Mantis item about it. Thanks Jonathan Bromley -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Wed Mar 26 04:23:43 2014
This archive was generated by hypermail 2.1.8 : Wed Mar 26 2014 - 04:23:52 PDT