# \[ANN\] Ruby-VPI 13.0.0

**URL:** <https://rubytalk.org/t/ann-ruby-vpi-13-0-0/34048>\
**Category:** ruby-talk\
**Created:** [28 December 2006 06:59 UTC](https://rubytalk.org/t/ann-ruby-vpi-13-0-0/34048 "2006-12-28T06:59:44Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Suraj\_Kurapati1](https://avatars.discourse-cdn.com/v4/letter/s/f19dbf/32.png) [@Suraj\_Kurapati1](https://rubytalk.org/u/Suraj_Kurapati1)\
**Post date:** [28 December 2006 06:59 UTC](https://rubytalk.org/t/ann-ruby-vpi-13-0-0/34048/1 "2006-12-28T06:59:44Z")

</div>

Ruby-VPI is a Ruby interface to Verilog VPI. It lets you create  
complex Verilog test benches easily and wholly in Ruby.

&nbsp;&nbsp;Web site: [http://ruby-vpi.rubyforge.org](http://ruby-vpi.rubyforge.org)

&nbsp;&nbsp;Install: gem install ruby-vpi

Version 13.0.0 (2006-12-27)

Summary

This release fixes a major instability bug, simplifies  
generated Verilog benches, and purifies the API reference  
documentation.

Notice

&nbsp;&nbsp;• The $ruby\_init and $ruby\_relay system task/functions  
&nbsp;&nbsp;&nbsp;&nbsp;have been removed. Generated Verilog benches no longer  
&nbsp;&nbsp;&nbsp;&nbsp;use them.  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;□ To pass your own command-line options to Ruby, set  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;the RUBYOPT environment variable before running a  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;test.

New features

&nbsp;&nbsp;• You can now choose when Vpi::relay\_verilog is  
&nbsp;&nbsp;&nbsp;&nbsp;triggered: upon positive/negative edge of the clock  
&nbsp;&nbsp;&nbsp;&nbsp;signal, or any other criteria. This is done by passing  
&nbsp;&nbsp;&nbsp;&nbsp;a block to the RubyVpi::init\_bench method (see the API  
&nbsp;&nbsp;&nbsp;&nbsp;reference documentation for details).

Details

&nbsp;&nbsp;• Fixed a major instability bug that was randomly causing  
&nbsp;&nbsp;&nbsp;&nbsp;segmentation faults and pthread assertion failures.

&nbsp;&nbsp;&nbsp;&nbsp;The problem was that the $ruby\_init system task/  
&nbsp;&nbsp;&nbsp;&nbsp;function was mischeviously unlocking a pthread mutex.  
&nbsp;&nbsp;&nbsp;&nbsp;From then onward, all code assumed that the mutex was  
&nbsp;&nbsp;&nbsp;&nbsp;still locked—but in reality, the mutex was already  
&nbsp;&nbsp;&nbsp;&nbsp;unlocked.

&nbsp;&nbsp;• Replaced the $ruby\_init and $ruby\_relay system task/  
&nbsp;&nbsp;&nbsp;&nbsp;functions with callbacks.

&nbsp;&nbsp;• Excluded internal stuff from the API reference  
&nbsp;&nbsp;&nbsp;&nbsp;documentation for Ruby.

&nbsp;&nbsp;• Removed system-dependent path /usr/bin/ruby from the  
&nbsp;&nbsp;&nbsp;&nbsp;tools.

> **···**
>
> --  
> Posted via [http://www.ruby-forum.com/](http://www.ruby-forum.com/).
