Re: [myhdl-list] migrating from myHDL-0.5.1 to myHDL_0.6

[Newell J. <pil...@gm...>]

On Mon, Jan 26, 2009 at 3:07 PM, Sami Al Dalahmah
<sam...@gm...>wrote:

> Dear All,
>
> Thank you for your response, it is really helpful especially Gunter's
> approach. But for now I think I will go with the straight forward one
> suggested by Jan. And I assume I should install the new VPI file of the 0.6
> for the cosimulation instead of the old one in the simulator (Icarus in my
> case), right?
>
> I really like the analyze/verify features, because they save me the script
> used to compile ans simulate the Verilog code. By the way does anyone have
> good experience in Icarus (maybe it is somehow unrelated to myHDL but it can
> be useful)? I ran into the issue when you have a python script using the
> function "os.system(*command*)" to run Icarus for compiling and simulating
> then


Just remember that you are simply programming in Python.  Therefore, there
are other ways of calling the command above (whether or not this would be
the right thing to do or not will depend on what you doing).  Look at Popen
in the subprocess module that comes with Python.  You can do try-except
blocks as well etc.

>>> help(os.system)

This will show you that os.system will give you an exit status.

This is the beauty of MyHDL....its in Python!

-- 
Newell

http://www.gempillar.com
Before enlightenment: chop wood, carry water
After enlightenment: code, build circuits