# \[ANN\] Ruby-VPI 19.0.0 **URL:** \ **Category:** Ruby\ **Created:** [August 28, 2007, 4:33am UTC](https://www.ruby-forum.com/t/ann-ruby-vpi-19-0-0/113149 "2007-08-28T04:33:26Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![snk](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/d9b06d/32.png) [@snk](https://www.ruby-forum.com/u/snk)\ **Post date:** [August 28, 2007, 4:33am UTC](https://www.ruby-forum.com/t/ann-ruby-vpi-19-0-0/113149/1 "2007-08-28T04:33:26Z")
Ruby-VPI is a Ruby interface to IEEE 1364-2005 Verilog VPI and a platform for unit testing, rapid prototyping, and systems integration of Verilog modules through Ruby. It lets you create complex Verilog test benches easily and wholly in Ruby. • See [http://ruby-vpi.rubyforge.org](http://ruby-vpi.rubyforge.org) for details. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Version 19.0.0 (2007-08-27) This release restores support for Cadence NC-Sim, breaks support for Mentor Modelsim, adds support for concurrent processes which simplify implementing Ruby prototypess, and offers numerous other improvements. Mentor Modelsim users, take note: this release does not work very well with Mentor Modelsim, so do not upgrade until compatibility is restored in a future release. In the mean time, consider using this release with another simulator, such as GPL Cver. Thanks • Calvin Wong requested the concurrent processes feature, helped test it, and provided useful feedback. Caution • Prototypes no longer have a feign! method. Instead, they emulate the behavior of the real Verilog DUT using the new concurrency model. • All “initial” blocks in Verilog code are now evaluated before the specification begins executing. This allows you to set the initial value of registers in Verilog before the specification interacts with them. • The Vpi module has been renamed to VPI for consistency with the project name. • The VPI::simulation\_time method has been renamed to VPI::current\_time. • The VPI::Handle.value\_forced? method has been renamed to VPI::Handle.force? • The samp/ directory has been renamed to examples/. • Code coverage analysis results are now produced only in plain-text format. Repairs • You can now access VPI constants using their original uncapitalized names. For example, you can now write “vpiIntVal” instead of having to write “VpiIntVal”. However, note that the capitalized names are still supported, so you are not required to change your code. • Value change / edge detection for VPI handles was previously incorrect: if you called the VPI::Handle.posedge? function twice in the same time step, it would give you two different answers. • The problem of not being able to write values to nets in Cadence NC-Sim has been fixed. Additions • Added support for concurrent processes, which make Ruby prototypes appear more like Verilog code and also give the ability to write parallel tests. • Added support for performance profiling using the ruby-prof project. The profiler can be enabled by setting the PROFILER environment variable to “1” before running a Ruby-VPI test. • Added new method aliases to VPI::Handle for value detection. The complete list of aliases is now: □ Tests if the logic value of this handle is unknown (x). ☆ x? ☆ unknown? ☆ dont\_care? □ Sets the logic value of this handle to unknown (x). ☆ x! ☆ unknown! ☆ dont\_care! □ Tests if the logic value of this handle is high impedance (z). ☆ z? ☆ hi\_z? ☆ high\_z? ☆ high\_impedance? ☆ tri\_state? ☆ floating? □ Sets the logic value of this handle to high impedance (z). ☆ z! ☆ hi\_z! ☆ high\_z! ☆ high\_impedance! ☆ tri\_state! ☆ floating! □ Tests if the logic value of this handle is at “logic high” level. ☆ high? ☆ one? □ Sets the logic value of this handle to “logic high” level. ☆ high! ☆ one! □ Tests if the logic value of this handle is at “logic low” level. ☆ low? ☆ zero? □ Sets the logic value of this handle to “logic low” level. ☆ low! ☆ zero! • Added new methods to VPI::Handle for value change / edge detection: □ edge? – detects positive and negative edges □ change? – detects any kind of value change □ change\_00? – detects a value change from 0 to 0 □ change\_01? – detects a value change from 0 to 1 □ change\_0x? – detects a value change from 0 to unknown □ change\_0z? – detects a value change from 0 to high-Z □ change\_10? – detects a value change from 1 to 0 □ change\_11? – detects a value change from 1 to 1 □ change\_1x? – detects a value change from 1 to unknown □ change\_1z? – detects a value change from 1 to high-Z □ change\_x0? – detects a value change from unknown to 0 □ change\_x1? – detects a value change from unknown to 1 □ change\_xx? – detects a value change from unknown to unknown □ change\_xz? – detects a value change from unknown to high-Z □ change\_z0? – detects a value change from high-Z to 0 □ change\_z1? – detects a value change from high-Z to 1 □ change\_zx? – detects a value change from high-Z to unknown □ change\_zz? – detects a value change from high-Z to high-Z ---
**Author:** ![snk](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/d9b06d/32.png) [@snk](https://www.ruby-forum.com/u/snk)\ **Post date:** [August 28, 2007, 3:41pm UTC](https://www.ruby-forum.com/t/ann-ruby-vpi-19-0-0/113149/2 "2007-08-28T15:41:22Z")
unsubscribe ---
**Author:** ![snk](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/d9b06d/32.png) [@snk](https://www.ruby-forum.com/u/snk)\ **Post date:** [August 28, 2007, 6:01pm UTC](https://www.ruby-forum.com/t/ann-ruby-vpi-19-0-0/113149/3 "2007-08-28T18:01:30Z")
Shawn Sullivan wrote: > unsubscribe I don’t understand. Are you saying that (1) I should stop posting release announcements to ruby-talk, (2) I should stop posting anything to ruby-talk and unsubscribe myself, or (3) you want to unsubscribe from ruby-talk? ---
**Author:** ![snk](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/d9b06d/32.png) [@snk](https://www.ruby-forum.com/u/snk)\ **Post date:** [August 30, 2007, 11:25pm UTC](https://www.ruby-forum.com/t/ann-ruby-vpi-19-0-0/113149/4 "2007-08-30T23:25:56Z")
Suraj K. wrote: > Shawn Sullivan wrote: > > > unsubscribe > > I don’t understand. Are you saying that (1) I should stop posting > release announcements to ruby-talk, (2) I should stop posting anything > to ruby-talk and unsubscribe myself, or (3) you want to unsubscribe from > ruby-talk? He must have unsubscribed. Please keep posting!