RE: EXTERNAL: RE: [vhdl-200x] Interfaces with normal, conjugated and monitor flavours

I would want to use interfaces for the transaction side of a bus functional model in my testbenches. To complete a transaction interface I use procedures. It would strongly reduce the usefulness of interfaces if I cannot use the interface in a procedure.

So I think interfaces needs to be a type and must be allowed to be used everywhere a type is used.

John

> -----Original Message-----
> From: owner-vhdl-200x@eda.org [mailto:owner-vhdl-200x@eda.org] On
> Behalf Of tgingold@free.fr
> Sent: 5. mars 2015 09:29
> To: vhdl-200x@eda.org
> Subject: Re: EXTERNAL: RE: [vhdl-200x] Interfaces with normal, conjugated
> and monitor flavours
>
> > I don’t see how we can avoid a means of associating a type with one or
> > more interfaces. Interfaces don’t get associated to just other
> > interfaces, they get associated with signal, constant and variable
> > (for subprograms) objects. And those objects have types.
>
> I strongly agree with this requirement.  The 'interface' could also be used to
> declare objects (but as I said this has important consequences).
>
> > Compatibility with subprograms (sequentially or concurrently called)
> > is also desirable.
>
> 'Desirable' is the right word IMHO; this is not a requirement.
>
> Tristan.
>
> --
> This message has been scanned for viruses and dangerous content by
> MailScanner, and is believed to be clean.
>
>


________________________________

CONFIDENTIALITY
This e-mail and any attachment contain KONGSBERG information which may be proprietary, confidential or subject to export regulations, and is only meant for the intended recipient(s). Any disclosure, copying, distribution or use is prohibited, if not otherwise explicitly agreed with KONGSBERG. If received in error, please delete it immediately from your system and notify the sender properly.

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