But direction and kind can be implicit. If I remove interface from the code I've post then type integer wire will be used as port type - I do not need to write :input T i DANiel -----Original Message----- From: Greg Jaxon [mailto:Greg.Jaxon@synopsys.com] Sent: 23 lipca 2008 17:42 To: Daniel Mlynek Cc: sv-bc@eda-stds.org Subject: Re: [sv-bc] search rules for type vs interface Daniel, I'm sorry to report that only the context can determine which definition of T applies in each circumstance. In the case you've asked about, T can only refer to the interface, whereas in "module top( input T i );", it can only refer to the typedef. The fact that this is beyond the capabilities of context-free scanners and parsers is worth noting. Greg Daniel Mlynek wrote: > interface T; > endinterface > > typedef integer T; > > module top (T i); //T is a type or T is an interface?????? > initial $display("%b", i); > endmodule > > DANiel > > -- > 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 Jul 23 08:48:08 2008
This archive was generated by hypermail 2.1.8 : Wed Jul 23 2008 - 08:48:19 PDT