I would use the same record type definition, with one or more named composite modes defined for that record type (e.g. "master" & "slave").
But I'm certainly open to other ideas.
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 Martin.J Thompson
Sent: Monday, March 07, 2011 8:59 AM
To: 'vhdl-200x@eda.org'
Subject: RE: EXTERNAL: Re: [vhdl-200x] VHDL enhancements wish list
>>> On 07 March 2011 at 14:43, in message
<75E1FE1C6E1C924A8F27E609CBE62C3D48434D243F@HVXMSP1.us.lmco.com>, "Jones, Andy
D" <andy.d.jones@lmco.com> wrote:
> 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.
Would that require two definitions of the record, one for the initiator and one for the target, with different directions on each?
Or something which allows that to be managed independently of the record defintion?
Cheers,
Martin
-- Martin Thompson CEng MIET TRW Conekt, Stratford Road, Solihull, B90 4GW. UK +44 (0)121-627-3569 : martin.j.thompson@trw.com http://www.conekt.co.uk/ Conekt is a trading division of TRW Limited Registered in England, No. 872948 Registered Office Address: Stratford Road, Solihull B90 4AX -- 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 14:27:45 2011
This archive was generated by hypermail 2.1.8 : Mon Mar 07 2011 - 14:28:09 PST