Re: [myhdl-list] MEP : Signal Containers

[Christopher F. <chr...@gm...>]

On 5/18/12 3:17 PM, Tom Dillon wrote:
> <lots of snips>

>
> I saw the term class attribute and thought it might be something more
> that converting signals in a class. I thought I was missing a feature
> that was being talked about.
>

Yes, it took me a while to understand what a Python /class attribute/ 
was referring to as well.

 From the Python tutorial (documentation)

"""
By the way, I use the word attribute for any name following a dot — for 
example, in the expression z.real, real is an attribute of the object z. 
Strictly speaking, references to names in modules are attribute 
references: in the expression modname.funcname, modname is a module 
object and funcname is an attribute of it. In this case there happens to 
be a straightforward mapping between the module’s attributes and the 
global names defined in the module: they share the same namespace! [1]
"""

I also used the above link as a reference/link in the MEP-107.

And in these discussions the proposal is to convert class attributes of 
the type(SignalType) and constants (the later not mentioned in the 
current version of the MEP, because what is a constant?).

Thanks for the questions, it is worthwhile working through explaining 
exactly what is supported.  My guess is there could be a lot of 
confusion.  It adds some good features but might cause additional 
confusion what is convertible if one is most familiar with OO software 
development.

Regards,
Chris