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

I like this explanation, although it might be a little long for an error 
message:-)

Jonathan Bromley wrote:

>I'm happy to sign up as educator/evangelist for this version:
>~~~~~~
>If you define a data type inside an interface, it's because
>you intend to use objects of that type only within the code
>for that interface (or module, or whatever).  The offending 
>example (reaching into the interface instance through a
>virtual interface) really doesn't fit with that idea.
>If I want more than one thing to share a definition, I
>should put the definition in a package and import it into 
>both things.  The issue is neither simulation performance
>nor implementation convenience; it's about users 
>Doing the Decent Thing (tm).  Having an external agent
>reach into a scope and grab some of its hidden secrets,
>even if only in order to copy them to the hidden secrets
>of an apparently similar scope, is not my idea of Decent.
>~~~~~~
>
>  
>


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