Dave, That is not completely correct. 12.1.2 says, "When a list of port connections is given using the ordered port connection method, the first element in the list shall connect to the first port declared in the module, the second to the second port, and so on. See 12.3 for a more detailed discussion of ports and port connection rules. A connection can be a simple reference to a variable or a net identifier, an expression, or a blank. An expression can be used for supplying a value to a module input port. A blank port connection shall represent the situation where the port is not to be connected. When connecting ports by name, an unconnected port can be indicated either by omitting it in the port list or by providing no expression in the parentheses [i.e., .port_name ()]." The end of the 2nd paragraph talks about a blank port connected when connecting my order. I understand that to mean that the port connection list contains two consecutive commas, with a blank connection in the middle. The 3rd paragraph explicitly mentions omitting a name port connection. That leaves only leaving off a port at the end of an ordered port list. But the subject is more or less covered in 1364. Shalom > -----Original Message----- > From: Rich, Dave [mailto:Dave_Rich@mentor.com] > Sent: Tuesday, October 31, 2006 12:11 PM > To: Bresticker, Shalom; stuart@sutherland-hdl.com; sv-bc@server.eda.org > Subject: RE: [sv-bc] .name and .* > > This is actually a problem with the 1364 LRM. It never defines the > semantics for omitting an ordered or named port expression from a list > of ports. Only where says it that .name() port with no expression leaves > the port unconnected.Received on Tue Oct 31 05:28:07 2006
This archive was generated by hypermail 2.1.8 : Tue Oct 31 2006 - 05:28:23 PST