Re: [myhdl-list] Example of MyHDL for Python Developers Documentation

[Christopher L. <loz...@fr...>]

>> My mistake.  It is easy to think of MyHDL as a shared project with
>> people having shared direction.  And then we get to discuss the shared
>> direction.  The reality is that each person does whatever they want.
>> Thank you for clearing up my understanding of open source projects.

> Christopher, it sounds like you are being sarcastic here but if so in fact
> you really are mistaken about what happens in open source projects with no
> paid engineers.  The purpose of discussion is only to give a person ideas.
> That person will then go off and do whatever they want.  And whether that
> gets back into the main tree is entirely up to the owners of the project,
> who will do whatever they want with the submission :-).  If they don't take
> it you may get a fork...
Actually I was not being sarcastic.  I did not quite understand the
culture of open source projects.  Thank you for clearing that up.

> don't be a help
> vampire: http://slash7.com/2006/12/22/vampires/
Point well taken. 

On 5/3/12 10:03 AM, G. Andrew Stone wrote:
> Then write it... 
I am doing that.  That is why I wrote the starter Documentation Page. A
great way to contribute to open source is to write documentation.  By
now there is quite a bit of stuff on my wiki.

wiki.myhdlclass.com:8080

Some of it is even correct.

I just have to go and figure out why some people are able to access it
and others not.

On 5/3/12 10:03 AM, G. Andrew Stone wrote:
> In fact, what I thought myHDL was going to let me do is create classes that
> define blocks of logic at the RTL level (synthesizable), perhaps with
> inputs and output "Signals" as variables passed in the constructor and then
> by instantiating those classes I'd be in effect plunking down copies of
> that logic in the FPGA (or within larger logic blocks by instantiating
> these within the constructor of another class).  4 years ago I did not ever
> figure out how to do this... I don't think anything wrapped in a class was
> synthesizable back then.  But maybe that has changed now; I haven't tried
> using classes since.
Brilliant.  Thank you.  Now you have given me a clear idea as to where
MyHDL should be headed.    Here is how to decorate a class method.

http://stackoverflow.com/questions/1367514/how-to-decorate-a-method-inside-a-class

Now if we just agree that the method hardwareModule() is the decorated
method that simulates and converts a class, and the instance variables
are the signals, we can create a more Object-Oriented version of
MyHDL.   Then we can subclass existing hardware modules.  Maybe it will
not convert easily.

t must be more complicated than that.

Chris