I think/suspect that this means that is you have module top; child c1(); child c2(); endmodule and then use a configuration to change "c2" to, say, "child2" then the restriction means that you can't have a bind to "child" but rather would have to bind to "top.c1". If that is indeed a correct interpretation of the LRM, I don't think that I like the restriction and don't really see why the restriction would need to be in the LRM. Gord. Bresticker, Shalom wrote: > 22.10 says, > > “It shall be an error to use noninstance-based binding if the design > contains more than one variation of the target module, program, or > interface. This can occur in the presence of configuration library > mapping or nonstandard functionality such as provided by the `uselib > directive. In such cases, users must use instance-based binding syntax > to disambiguate between the multiple variations of the target.” > > What is meant by “variation” here? > > Tools and users need a clear and precise definition in order to know > what is legal and what is not. > > Thanks, > > Shalom > > > > > -- > 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 <http://www.mailscanner.info/>**MailScanner* > <http://www.mailscanner.info/>*, and is > believed to be clean. > -- > This message has been scanned for viruses and > dangerous content by *MailScanner* <http://www.mailscanner.info/>, and is > believed to be clean. * -- -------------------------------------------------------------------- Gordon Vreugdenhil 503-685-0808 Model Technology (Mentor Graphics) gordonv@model.com -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Thu May 31 06:51:19 2007
This archive was generated by hypermail 2.1.8 : Thu May 31 2007 - 06:51:38 PDT