Re: [sv-bc] DataTypes: The wone net type

If we head down the route of merging the class stuff with the net/driver
data-types then you could probably add the equivalent of a constructor
(or initial process)in the definition that would go check whichever
attributes you are interested in. I think that would be cleaner than
adding a whole bunch of pre-defined wire types.

Kev.

Andrew MacCormack wrote:

>On Fri, Oct 29, 2004 at 09:09:18AM -0700, Stuart Sutherland wrote:
>
>
>>All of your reasoning is excellent and well stated. I am now satisfied that
>>all that is needed is a single-driver version of wire. I'm still not sold
>>on the keyword "wone". I would like to see some brainstorming on alternate
>>keyword suggestions.
>>
>>
>
>My preference would be to say bye-bye to some backward compatibility and make
>the "wone" keyword "wire" and have "tri" mean a resolved wire. But failing
>that:
>
>uwire // unresolved wire
>swire // Single driver wire
>sdwire // Single Driver wire
>p2pwire // point to point wire
>ptpwire // point to point wire
>wiref1 // wire fanin 1
>f1wire // fanin 1 wire
>uniwire // unique driver wire
>carpool // lots of commuters, but only one driver...
>
>
>
>

-- 
Altera Corp, 101 Innovation Drv, San Jose, CA 95134. T# (408) 544 7126