Hi Ryan,
> I strongly agree. In the current language, directionality has little to do with data type. And I feel it muddies the language to confuse the two. (I admit I'm somewhat of a purist.) I really
> like the user-defined modes (i.e. augmenting IN, OUT, INOUT, ...), but putting the information in the type/subtype feels wrong.
I don't necessarily agree or disagree. One thing Peter is
concerned about is the parsing of:
-- Named Modes
port (
portName : ModeName TypeName ;
vs.
-- Subtypes capturing direction information
port (
portName : SubTypeName ;
So do you have a suggestion for syntax.
> And I'm going to repeat myself, hopefully more clearly and for the last time. :-) I don't think the shared bus example is compelling. WISHBONE in particular has an INTERCON concept that handles
> complex interconnections between master(s) and slave(s) that allows the master and slave interfaces to remain simple and consistent -- and reusable. I guess I have a hard time liking a feature and
> syntax in an example design that I don't care for. (I don't mean to impugn the skills of the proposers. I rather dislike the style of some of our most talented designers here. Most likely the
> feeling is mutual, though we get along and work together quite well. :-)
While I agree that we do not have a use model for needing open/null at
this time, I would be most comfortable syntax that allowed it to be
added in the future. Which is why I proposed it as a question
rather than as a "we need to do this".
Best,
Jim
-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Jim Lewis Director of Training mailto:Jim@SynthWorks.com SynthWorks Design Inc. http://www.SynthWorks.com 1-503-590-4787 Expert VHDL Training for Hardware Design and Verification ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Wed Aug 22 14:03:16 2012
This archive was generated by hypermail 2.1.8 : Wed Aug 22 2012 - 14:03:38 PDT