I think the LRM is equally unclear about what input directions means for net ports of modules. I believe this is why no tool enforces port directions on nets. If someone declares a virtual interface with a modport, the only operation allowed with an output is a procedural assignment. If you stretch the longest static prefix rules to include virtual interfaces, then you have to assume that a procedural assignment to a virtual interface member is a procedural assignment to that member in *all* instances of the interface. There is no such thing as a static reference to a virtual interface. Dave -----Original Message----- From: owner-sv-bc@server.eda.org [mailto:owner-sv-bc@server.eda.org] On Behalf Of Mark Hartoog Sent: Wednesday, October 17, 2007 11:12 AM To: Vreugdenhil, Gordon; Mark Hartoog Cc: Jonathan Bromley; sv-bc@server.eda.org; sv-ec@server.eda.org Subject: RE: [sv-bc] RE: [sv-ec] That modport direction issue again I agree the LRM is unclear about what input modport directions means for net ports. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Wed Oct 17 12:42:25 2007
This archive was generated by hypermail 2.1.8 : Wed Oct 17 2007 - 12:42:47 PDT