Re: [myhdl-list] Advocacy page

[Christopher L. F. <cf...@uc...>]

> On the occasion of the new release, I decided to write a
> page with common situations and opinions that MyHDL addresses,
> and that people hopefully can relate to.
>
> I have tried to write it down as succinctly as possible -
> hard work, takes time!
>
>     http://www.myhdl.org/doku.php/why
>
> Feedback, suggestions, improvements welcome!

Very good work!  Thanks for all the hard work, with the releases,  
documentation, and the "Why".


In addition to everything you mentioned in your write-up, the  
following puts all those together and captures why Python and MyHDL  
has been attractive for me.  The following isn't really new/different  
but a combination of the points you made.  Also, as you mentioned,  
putting together a coherent thought can take some time and work.  I  
apologize in advance if the following is a little sloppy:

HDL and Beyond
For any kind of algorithm work Python provides a single language where  
everything can be accomplished.  A problem can first be tackled at a  
very high level being an algorithm and / or model.  Because of  
Python's extensive libraries this work is no different than using any  
other tool.  Commonly this work and HDL implementation have be done by  
different engineers because the tools for both required a certain  
level of knowledge that wasn't transferrable between the domains.   
With Python / MyHDL an algorithm / model designer can explore HDL  
implementation and an HDL designer can explore algorithm / model  
design.  There are not multiple tools to learn.  MyHDL is an HDL  
language so the conversion from algorithm to model is still the same  
design procedure (this is a good thing) but it can all be accomplished  
in the same environment.  And the testing can be easily leveraged for  
both design domains.
--

As a side note, I have updated to the latest release and rerun a bunch  
of my MyHDL code and everything looks good so far.