You can use records on inout ports, but every element of the record must be inout, which then effectively restricts the usage to resolved types on all elements of the record, and the explicit specification of benign drivers on elements which are only used as inputs.
I am in favor of a mechanism to allow different modes on different elements of a record port, while mapping the entire record to the (composite) port in one association. Whether that should be a named composite mode for the record type or some other means is open to suggestions.
Andy D Jones
Electrical Engineering
Lockheed Martin Missiles and Fire Control
Dallas TX
-----Original Message-----
From: owner-vhdl-200x@eda.org [mailto:owner-vhdl-200x@eda.org] On Behalf Of David Koontz
Sent: Friday, March 04, 2011 1:43 AM
To: vhdl-200x@eda.org
Subject: EXTERNAL: Re: [vhdl-200x] VHDL enhancements wish list
On 1/03/11 10:41 PM, Martin.J Thompson wrote:
> * Using records on inout pins in some fashion (or is that doable in
> 2008 and I haven't found out how yet?)
We could consider that a port is a structure (record) and is accessed
(connected) through a portmap.
Are you after other ways to make connectivity such as inferred signals
(wires)?
> * Easy efficient external language interface (to Python - ideally I'd
> like to write my whole testbench in Python).
I don't seem to recall that Python is either an ANSI or IEEE standard. This
sounds like a case of 'who bells the cat' and does VHPI for Python, as well
as issues on operating an elaborated model which are outside of the current
scope of the standard. You could get the idea this is a tool domain issue.
-- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Mon Mar 7 06:43:45 2011
This archive was generated by hypermail 2.1.8 : Mon Mar 07 2011 - 06:44:17 PST