Re: [myhdl-list] MEP : Signal Containers

[Tom D. <td...@di...>]

On 05/18/2012 10:08 AM, Christopher Felton wrote:
> On 5/17/12 8:35 AM, Tom Dillon wrote:
>>
>> On 05/17/2012 04:03 AM, Oscar Diaz wrote:
>>> 2012/5/14 Christopher Felton<chr...@gm...>:
>>>
>>>> <snip>
>>>>
>>>> I have made some minor changes to the proposed MEP, the modifications
>>>> can be found here, http://www.myhdl.org/doku.php/meps:mep-107
>>>>
>>>> I have been *waffling* if the class attributes should be part of this
>>>> MEP or a separate MEP.  I am leaning more towards inclusion, if a class
>>>> attribute is a convertible type then it can be viewed as a "Signal
>>>> Container".  But it might warrant it separate MEP/thread simply because
>>>> the conversation around class support might be lengthy, e.g. subset of
>>>> class support (the current MEP107 and MEP108) or something different.
>>> I agree: class attributes should be covered in this MEP (as we
>>> discussed in this thread). However, I think this MEP should address
>>> first the easy containers: lists and dictionaries, and after that
>>> experience we can move to support -the more general- class attributes.
>>>
>> I am more interested in using classes. I am not sure what class
>> attributes would do. Can someone provide an example?
> I have already implemented this feature and created a MEP write-up,
> MEP-108, http://www.myhdl.org/doku.php/meps:mep-108.  There hasn't been
> much discussion so I haven't posted the patch yet.  I will post the
> patch soon.

Read that over quickly. What is the advantage to that over a function?

Also, how do class attributes fit into this? I think I may not undertand 
what they are and how they would be used in MyHDL.