Re: [sv-ec] Struct access via virtual interfaces

From: Jeff Freedman <jeffsf_at_.....>
Date: Fri Jan 05 2007 - 10:11:44 PST
Brad Pierce wrote:

>>The main problem would be educating the user as to why this is not
>>    
>>
>allowed.
>
>Is the argument that simulation performance must necessarily be degraded
>by allowing it, or only that allowing it makes life harder for
>implementors?
>
>  
>
Simulation performance would be the main reason.  By allowing the 
assignment (as we do now), we have to type-check it every time it is 
encountered at run-time.  The problem with making this illegal is 
producing an intelligible error message.  The user is bound to wonder 
why it's okay to have "ifv1.vec = ifv2.vec" but not "ifv1.struc = 
ifv2.struc", where the 2nd case is only illegal if the type for "struc" 
is local to the interface.


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Received on Fri Jan 5 10:12:06 2007

This archive was generated by hypermail 2.1.8 : Fri Jan 05 2007 - 10:12:17 PST