All,
I'm also concerned that signal assignment is not one of the operators included. Except for access and protected types, there should be no problem with signal assignment. But, maybe it isn't needed.
Bhasker, since this proposal is intended to address the immediate needs in the testbench and verification area (container objects proposals), can you comment on whether signal assignment would be needed?
-Steve Bailey
> ... sounds like very good stuff, but I don't understand the
> need for this restriction (section 6 Formal Generic Types,
> first paragraph):
>
> An interface type declaration defines a formal generic
> type that can denote any type. The generic unit can only
> assume that operations available for all types are
> applicable, namely, variable assignment, equality and
> inequality operations.
>
> Presumably an object of the generic type can be passed as
> an actual parameter to a subprogram? In which case, why
> not allow it to appear as an operand in an infix
> expression?
> --
> 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
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.
Received on Tue Apr 20 23:30:23 2004
This archive was generated by hypermail 2.1.8 : Tue Apr 20 2004 - 23:30:33 PDT