RE: [sv-bc] Unconnected ports using .name implicit ports (SVDB 1660??)

I looked at some of the early proposals. I had to go back to
http://www.eda.org/vlog-pp/hm/ to find them. Some of them could
certainly be interpreted as saying that if you used .name on any port,
then all ports had to be listed. Although they allowed to combine .name
and .name(name), they did not allow to combine .name and .*.

Regards,
Shalom 

> -----Original Message-----
> From: owner-sv-bc@server.eda.org 
> [mailto:owner-sv-bc@server.eda.org] On Behalf Of Steven Sharp
> Sent: Tuesday, October 16, 2007 2:31 AM
> To: sv-bc@server.eda.org; cliffc@sunburst-design.com
> Subject: Re: [sv-bc] Unconnected ports using .name implicit 
> ports (SVDB 1660??)
> 
> 
> >From: "Clifford E. Cummings" <cliffc@sunburst-design.com>
> 
> >Shalom pointed out SVDB 1660. I'm not sure if it is clear that 
> >unconnected ports must be explicitly listed as empty ports (i.e.
> >...  .port1(), ... when instantiating a module with an unconnected 
> >port. What do SV-BC members think?
> 
> The only time unconnected ports must be explicitly listed as 
> empty ports is when you are using .* for the port 
> connections.  That is because .* is a request to connect all ports.
> 
> In all other situations, unmentioned ports are unconnected, 
> regardless of whether you specify the connected ports with 
> .name or .name(signal).
> 
> Stu said at today's SV-BC meeting that you and he intended it 
> to work differently, but neither the LRM text nor anyone else 
> at the meeting supported that interpretation.
> 
> Steven Sharp
> sharp@cadence.com
> 
> 
> --
> This message has been scanned for viruses and dangerous 
> content by MailScanner, and is believed to be clean.
> 
---------------------------------------------------------------------
Intel Israel (74) Limited

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.