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

From: Jonathan Bromley <jonathan.bromley_at_.....>
Date: Fri Jan 05 2007 - 10:27:06 PST
> > 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?

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.
~~~~~~

-- 
Jonathan Bromley, Consultant

DOULOS - Developing Design Know-how
VHDL * Verilog * SystemC * e * Perl * Tcl/Tk * Project Services

Doulos Ltd. Church Hatch, 22 Market Place, Ringwood, Hampshire, BH24 1AW, UK
Tel: +44 (0)1425 471223                   Email: jonathan.bromley@doulos.com
Fax: +44 (0)1425 471573                           Web: http://www.doulos.com

The contents of this message may contain personal views which 
are not the views of Doulos Ltd., unless specifically stated.

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

This archive was generated by hypermail 2.1.8 : Fri Jan 05 2007 - 10:28:06 PST