Re: [sv-bc] Unofficial Meeting Monday Jan 10 - 9am PST

What would we be the use of it? You can't generate a module declaration.

-- Brad

2011/1/12 Bresticker, Shalom <shalom.bresticker@intel.com>:
> The BNF is
>
> interface_port_header ::=
>          interface_identifier [ . modport_identifier ]
>        | interface [ . modport_identifier ]
>
> Shouldn't you be able to use a generated modport in a non-generic interface port declaration?
>
> Shalom
>
>
>> -----Original Message-----
>> From: owner-sv-bc@eda.org [mailto:owner-sv-bc@eda.org] On Behalf Of
>> Brad Pierce
>> Sent: Wednesday, January 12, 2011 2:51 AM
>> To: Jonathan Bromley
>> Cc: sv-bc@eda.org
>> Subject: Re: [sv-bc] Unofficial Meeting Monday Jan 10 - 9am PST
>>
>> No, it's a semantic issue, because the current BNF can already accept
>> your example, if we agree that the 'interface' keyword in a generic
>> interface_port_header can stand in for, not only an interface
>> instance, but also for a *scope* of an interface instance.
>>
>> -- Brad
>>
>> On Tue, Jan 11, 2011 at 3:53 PM, Brad Pierce <brad_pierce@acm.org>
>> wrote:
>> > Jonathan,
>> >
>> > On p. 29 of that presentation ( http://bit.ly/eipdSE ) , you show a
>> > very clever trick of using generic interface port declarations to
>> > receive a generated modport.
>> >
>> > I think the current BNF in A.1.3 (interface_port_header) never
>> > contemplated the possibility of generate scopes, and to make your
>> > trick work within the official standard, we'd need to correct that
>> > oversight.
>> >
>> > -- Brad
>
> ---------------------------------------------------------------------
> 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.