RE: [sv-bc] New Mantis item SV-BC 315 added

Doug,

[...]
> One can imagine simply doing
> "cut-n-paste" of the text from the bind statement into
> the target scope.

Thanks for the explanation - it confirms my understanding in
every respect save the following...

> It shall be an error if the bound module/program/interface's name
> conflicts with a pre-existing instance name in the target scope.

I can understand that this makes things much simpler both to
specify and to implement, but I believe it severely limits
the usefulness of "bind". It has the consequence that the
binding ("parasite") code must have full knowledge of the
bound-to ("host") code. Much worse, it means that future
modifications to the host code (which, of course, is innocent
of any knowledge of the binding) may subvert the binding
by clashing with the parasite's instance name.

I guess it may be too late to change this now, and in
practice it could be worked-around by suitable coding
conventions such as choosing a special name suffix for
all parasite instance names.

Thanks,

--
Jonathan Bromley, Consultant
DOULOS - Developing Design Know-how
VHDL * Verilog * SystemC * Perl * Tcl/Tk * Verification * Project Services
Doulos Ltd. Church Hatch, 22 Market Place, Ringwood, Hampshire, BH24 1AW, UK
Tel: +44 (0)1425 471223                    mail: jonathan.bromley@doulos.com
Fax: +44 (0)1425 471573                           Web: http://www.doulos.com
This e-mail and any  attachments are  confidential and Doulos Ltd. reserves 
all rights of privilege in  respect thereof. It is intended for the use of 
the addressee only. If you are not the intended recipient please delete it 
from  your  system, any  use, disclosure, or copying  of this  document is 
unauthorised. The contents of this message may contain personal views which 
are not the views of Doulos Ltd., unless specifically stated.