PyHVL = verilog PLI is going died....

• open source tool supported 
• iverilog VPI 2.0 
• http://iverilog.wikia.com/wiki/Using_VPI
• what's VPI/PLI(Verilog Procedural Interface)
• http://en.wikipedia.org/wiki/Verilog_Procedural_Interface
• what's DPI(SystemVerilog Direct Programming Interface)
• http://en.wikipedia.org/wiki/SystemVerilog_DPI
• third party language support 
• perl
• http://www.veripool.org/wiki/verilog-pli/Manual-verilog-pli
• ruby
• http://snk.tuxfamily.org/lib/ruby-vpi/
• python
• http://sourceforge.net/projects/pyhvl/?source=dlp
• disadvantage
• hard to read
• more rules need to follow
• init pli
• register pli 
• free pli
• using third part language to mix simulation run that's very difficult for designer view. they need to know how to driver system call and catch the simulation error when the segment fault happened 
• c 
• only for behavior model verification / profile
• why not using SystemVerilog + DPI to replace it?
• more closer with Verilog language
• more easily to understand 
• OO suport
• more flexible to designer(customer DPI)
• UVM