Re: [sv-bc] Query on Virtual (parameterized) interface declaration

  Hi Steven,
Thanks for your clarification. Now it is clear to me. However, do you
have any comment regarding the original questions that Kakoli has. If
the parameters are typed (type parameter) then what rule to be imposed
for actual value matching? Will it be "Matching types (section 6.22.1)"
or "Equivalent types (section 6.22.2)". Please comment.

Regards
Surya

-------- Original Message --------
Subject: Re: [sv-bc] Query on Virtual (parameterized) interface declaration
From: Steven Sharp <sharp@cadence.com>
To: Brad.Pierce@synopsys.com, spsaha@cal.interrasystems.com
Cc: sv-bc@eda.org
Date: Tuesday, August 24, 2010 11:15:10 AM
>> Date: Tue, 24 Aug 2010 10:43:22 +0530
>> From: Surya Pratik Saha<spsaha@cal.interrasystems.com>
>>> Further on this topic, I need to understand the meaning of following sentence
> mentioned in page no 686 of SV 2009 LRM:
>>> The actual values and types of those parameters shall match for an interface
> and virtual interface to be of the same type and to be assignment compatible
> (see 6.22.3).
>>> If the types of actual values are of the same type then it is redundant to
> specify "assignment compatible" as they are anyway assignment compatible. Or LRM
> wants mean something else.
>
>
> The previous revision of the LRM said that a virtual interface could be
> assigned an interface of the same type.
>
> If the current LRM had simply said that the parameters must match for
> the interface and virtual interface to be assignment compatible, someone
> might have tried to claim that the current LRM was changing the rules.
>
> By stating that the parameters must match for the interface and virtual
> interface to be of the same type, it is making clear that the rule about
> "the same type" in the previous LRM meant the same thing as the rule in
> the current LRM. It is making clear that this is a clarification of the
> previous rule, not a change to it.
>
>
> Steven Sharp | Architect | Cadence
>
> P: 508.459.1436 M: 774.535.4149 www.cadence.com
>
>
>

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