ruby-vpi 11.1.0 → 11.1.1

data/doc/src/manual.xsl

@@ -1,23 +0,0 @@
-<?xml version='1.0'?>
-<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:fo="http://www.w3.org/1999/XSL/Format" version="1.0">
-  <!-- chunking -->
-    <xsl:param name="use.id.as.filename" select="'1'"/>
-    <xsl:param name="chunk.first.sections" select="1"></xsl:param>
-    <!--<xsl:param name="chunk.tocs.and.lots" select="'1'"/>-->
-
-  <!-- graphics -->
-    <xsl:param name="admon.graphics" select="'1'"/>
-    <xsl:param name="admon.graphics.extension" select="'.png'"/>
-
-    <xsl:param name="callout.graphics" select="'1'"/>
-
-    <xsl:param name="navig.graphics" select="1"/>
-    <xsl:param name="navig.graphics.extension" select="'.png'"/>
-
-  <!-- line numbering -->
-    <!--<xsl:param name="use.extensions" select="1"/>-->
-    <!--<xsl:param name="linenumbering.extension" select="1"/>-->
-
-  <!-- styles -->
-    <xsl:param name="html.stylesheet" select="'styles/manual.css'"/>
-</xsl:stylesheet>

data/doc/src/shared.dtd

@@ -1,62 +0,0 @@
-<!--
-  Copyright 2006 Suraj N. Kurapati.
-
-  Permission is granted to copy, distribute and/or modify this
-  document under the terms of the GNU Free Documentation License,
-  Version 1.1 or any later version published by the Free Software
-  Foundation; with no Invariant Sections, no Front-Cover Texts and
-  no Back-Cover Texts.  A copy of the license is included in the
-  the file named "LICENSE".
--->
-
-<!-- project -->
-<!ENTITY rv "<application>Ruby-VPI</application>">
-<!ENTITY rv.url "http://ruby-vpi.rubyforge.org">
-<!ENTITY rv.url-project "http://rubyforge.org/projects/ruby-vpi">
-<!ENTITY rv.url-download "http://rubyforge.org/frs/?group_id=1339">
-<!ENTITY rv.url-tracker "http://rubyforge.org/tracker/?group_id=1339">
-<!ENTITY rv.url-forum "http://rubyforge.org/forum/?group_id=1339">
-<!ENTITY rv.url-source "&rv.url;/src/ruby-vpi">
-<!ENTITY rv..ulink "<ulink url='&rv.url;'>&rv;</ulink>">
-
-
-<!-- authors -->
-<!ENTITY snk "Suraj N. Kurapati">
-<!ENTITY snk..initials "snk">
-<!ENTITY snk..author "<author> <firstname>Suraj</firstname> <othername>N.</othername> <surname>Kurapati</surname> </author>">
-<!ENTITY snk..year "<year>2006</year>">
-<!ENTITY snk..holder "<holder>&snk;</holder>">
-<!ENTITY snk..copyright "<copyright>&snk..year; &snk..holder;</copyright>">
-
-
-<!-- acronyms & abbreviations -->
-<!ENTITY r "Ruby">
-<!ENTITY r.url "http://www.ruby-lang.org/en/20020101.html">
-<!ENTITY r..ulink "<ulink url='&r.url;'>&r;</ulink>">
-<!ENTITY v "Verilog">
-<!ENTITY vpi "<acronym>VPI</acronym>">
-
-<!ENTITY unix "<acronym>UNIX</acronym>">
-<!ENTITY url "<acronym>URL</acronym>">
-<!ENTITY l10n "<acronym>L10N</acronym>">
-<!ENTITY ansi "<acronym>ANSI</acronym>">
-<!ENTITY xml "<acronym>XML</acronym>">
-<!ENTITY xhtml "<acronym>XHTML</acronym>">
-<!ENTITY html "<acronym>HTML</acronym>">
-
-<!ENTITY gnu "<acronym>GNU</acronym>">
-<!ENTITY gpl "&gnu; <acronym>GPL</acronym>">
-<!ENTITY bash "<application>&gnu; <acronym>BASH</acronym></application>">
-<!ENTITY coreutils "&gnu; coreutils">
-<!ENTITY find "<application>&gnu; find</application>">
-<!ENTITY gna "<acronym>Gna!</acronym>">
-<!ENTITY gpg "<acronym>&gnu; Privacy Guard</acronym>">
-
-<!ENTITY iso639 "<acronym>ISO</acronym> 639">
-<!ENTITY iso639..ulink "<ulink url='http://www.oasis-open.org/cover/iso639a.html'>&iso639;</ulink>">
-
-
-<!-- fixed content -->
-<!ENTITY period "period or full stop &quot;<literal>.</literal>&quot;">
-<!ENTITY hyphen "hyphen or dash &quot;<literal>-</literal>&quot;">
-<!ENTITY pipe "pipe or vertical bar &quot;<literal>|</literal>&quot;">

data/doc/styles/manual.css

@@ -1,91 +0,0 @@
-body {
-  font-family: sans-serif;
-  line-height: 2em;
-}
-
-/* admonitions */
-  .tip, .note, .important, .caution, .warning {
-    border: thin solid steelblue;
-    background-color: aliceblue;
-    padding: 1em;
-  }
-
-/* headings */
-  .title, th {
-    font-family: serif;
-  }
-
-  h3, h4, h5, h6 {
-    margin-top: 10em;
-    text-align: center;
-
-    background-color: mistyrose;
-    padding: 1em;
-  }
-
-/* source code */
-  .screen, .filename {
-    background-color: whitesmoke;
-  }
-
-  .code, .programlisting, .function, .constant, .literal, .varname, .token, .type, .remark {
-    font-family: monospace;
-    background-color: ivory;
-  }
-
-  .screen, .programlisting {
-    border: thin solid silver;
-    padding: 1em;
-    line-height: normal;
-    display: block;
-    overflow: auto;
-  }
-
-  .function {
-  }
-
-  .constant {
-    color: green;
-    font-weight: bold;
-  }
-
-  .literal {
-    color: blue;
-  }
-
-  .varname {
-    color: magenta;
-  }
-
-  .token {
-    font-weight: bold;
-    color: indigo;
-  }
-
-  .type {
-    color: red;
-  }
-
-  .remark {
-    color: orangered;
-  }
-
-  .command {
-    background-color: bisque;
-  }
-
-/* tables */
-  table[border="1"] {
-    border: none;
-  }
-
-  table[border="1"] th {
-    border: none;
-    background-color: whitesmoke;
-  }
-
-  table[border="1"] th,
-  table[border="1"] td {
-    border: thin solid silver;
-    padding: 1em;
-  }

data/doc/usage.examples.html

@@ -1,3 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Examples</title><link rel="stylesheet" href="styles/manual.css" type="text/css" /><meta name="generator" content="DocBook XSL Stylesheets V1.68.1" /><link rel="start" href="index.html" title="Ruby-VPI user manual" /><link rel="up" href="usage.html" title="Chapter 4. Usage" /><link rel="prev" href="usage.tutorial.html" title="Tutorial" /><link rel="next" href="hacking.html" title="Chapter 5. Hacking" /></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Examples</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="usage.tutorial.html"><img src="images/prev.png" alt="Prev" /></a> </td><th width="60%" align="center">Chapter 4. Usage</th><td width="20%" align="right"> <a accesskey="n" href="hacking.html"><img src="images/next.png" alt="Next" /></a></td></tr></table><hr /></div><div class="section" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="usage.examples"></a>Examples</h2></div></div></div><p>The <code class="filename">samp</code> directory contains several example tests which illustrate how <span class="application">Ruby-VPI</span> can be used. Each example has an associated <code class="filename">Rakefile</code> which simplifies the process of running it. Therefore, simply navigate into an example directory and run the command <span><strong class="command">rake</strong></span> to get started.</p><p>Also, some example specifications make use of BDD through the <span class="application">rSpec</span> library. See the <a href="background.methodology.html" title="Methodology">the section called “Methodology”</a> for a discussion of <span class="application">rSpec</span>.</p></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="usage.tutorial.html"><img src="images/prev.png" alt="Prev" /></a> </td><td width="20%" align="center"><a accesskey="u" href="usage.html"><img src="images/up.png" alt="Up" /></a></td><td width="40%" align="right"> <a accesskey="n" href="hacking.html"><img src="images/next.png" alt="Next" /></a></td></tr><tr><td width="40%" align="left" valign="top">Tutorial </td><td width="20%" align="center"><a accesskey="h" href="index.html"><img src="images/home.png" alt="Home" /></a></td><td width="40%" align="right" valign="top"> Chapter 5. Hacking</td></tr></table></div></body></html>

data/doc/usage.html

@@ -1,3 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 4. Usage</title><link rel="stylesheet" href="styles/manual.css" type="text/css" /><meta name="generator" content="DocBook XSL Stylesheets V1.68.1" /><link rel="start" href="index.html" title="Ruby-VPI user manual" /><link rel="up" href="index.html" title="Ruby-VPI user manual" /><link rel="prev" href="setup.maintenance.html" title="Maintenance" /><link rel="next" href="usage.tools.html" title="Tools" /></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 4. Usage</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="setup.maintenance.html"><img src="images/prev.png" alt="Prev" /></a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="usage.tools.html"><img src="images/next.png" alt="Next" /></a></td></tr></table><hr /></div><div class="chapter" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="usage"></a>Chapter 4. Usage</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="usage.tools.html">Tools</a></span></dt><dd><dl><dt><span class="section"><a href="usage.tools.html#usage.tools.generate-test">Automated test generation</a></span></dt><dt><span class="section"><a href="usage.tools.html#usage.tools.verilog-ruby-conv">Verilog to Ruby conversion</a></span></dt></dl></dd><dt><span class="section"><a href="usage.tutorial.html">Tutorial</a></span></dt><dd><dl><dt><span class="section"><a href="usage.tutorial.html#usage.tutorial.declare-design">Start with a design</a></span></dt><dt><span class="section"><a href="usage.tutorial.html#usage.tutorial.generate-test">Generate a test</a></span></dt><dt><span class="section"><a href="usage.tutorial.html#usage.tutorial.specification">Specify your expectations</a></span></dt><dt><span class="section"><a href="usage.tutorial.html#usage.tutorial.implement-proto">Implement the prototype</a></span></dt><dt><span class="section"><a href="usage.tutorial.html#usage.tutorial.test-proto">Verify the prototype</a></span></dt><dt><span class="section"><a href="usage.tutorial.html#usage.tutorial.implement-design">Implement the design</a></span></dt><dt><span class="section"><a href="usage.tutorial.html#usage.tutorial.test-design">Verify the design</a></span></dt></dl></dd><dt><span class="section"><a href="usage.examples.html">Examples</a></span></dt></dl></div></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="setup.maintenance.html"><img src="images/prev.png" alt="Prev" /></a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="usage.tools.html"><img src="images/next.png" alt="Next" /></a></td></tr><tr><td width="40%" align="left" valign="top">Maintenance </td><td width="20%" align="center"><a accesskey="h" href="index.html"><img src="images/home.png" alt="Home" /></a></td><td width="40%" align="right" valign="top"> Tools</td></tr></table></div></body></html>

data/doc/usage.tools.html

@@ -1,9 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Tools</title><link rel="stylesheet" href="styles/manual.css" type="text/css" /><meta name="generator" content="DocBook XSL Stylesheets V1.68.1" /><link rel="start" href="index.html" title="Ruby-VPI user manual" /><link rel="up" href="usage.html" title="Chapter 4. Usage" /><link rel="prev" href="usage.html" title="Chapter 4. Usage" /><link rel="next" href="usage.tutorial.html" title="Tutorial" /></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Tools</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="usage.html"><img src="images/prev.png" alt="Prev" /></a> </td><th width="60%" align="center">Chapter 4. Usage</th><td width="20%" align="right"> <a accesskey="n" href="usage.tutorial.html"><img src="images/next.png" alt="Next" /></a></td></tr></table><hr /></div><div class="section" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="usage.tools"></a>Tools</h2></div></div></div><p>The <code class="filename">bin</code> directory contains various utilities which ease the process of writing tests. Each tool provides help and usage information invoked with the <code class="option">--help</code> option.</p><div class="section" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="usage.tools.generate-test"></a>Automated test generation</h3></div></div></div><p>The automated test generator (<span><strong class="command">generate_test.rb</strong></span>) generates tests from Verilog 2001 module declarations, as demonstrated in <a href="usage.tutorial.html#usage.tutorial.generate-test" title="Generate a test">the section called “Generate a test”</a>. A generated test is composed of the following parts:
-          </p><div class="variablelist"><dl><dt><span class="term">Runner</span></dt><dd><p>Written in Rake, this file builds and runs the test.</p></dd><dt><span class="term">Bench</span></dt><dd><p>Written in Verilog and Ruby, these files define the testing environment.</p></dd><dt><span class="term">Design</span></dt><dd><p>Written in Ruby, this file provides an interface to the design being verified.</p></dd><dt><span class="term">Prototype</span></dt><dd><p>Written in Ruby, this file defines a prototype of the design being verified.</p></dd><dt><span class="term">Specification</span></dt><dd><p>Written in Ruby, this file verifies the design.</p></dd></dl></div><p>
-        </p><p>The reason for dividing a single test into these parts is mainly to decouple the design from the specification. This allows you to focus on writing the specification while the remainder is automatically generated by the tool. For example, when the interface of a Verilog module changes, you would simply re-run this tool and incorporate those changes (using a <a href="setup.reqs.html#setup.reqs.optional" title="Recommendations">text merging tool</a>) into the test without diverting your focus from the specification.</p><div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Tip: Using kdiff3 with the automated test generator"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Tip]" src="images/tip.png" /></td><th align="left">Using <span class="application">kdiff3</span> with the automated test generator</th></tr><tr><td align="left" valign="top"><p>Create a file named <code class="filename">merge2</code> with the content below, make it executable, and put it somewhere accessible by your <code class="varname">PATH</code> environment variable. Next, update the <code class="varname">MERGER</code> environment variable by executing <span><strong class="command">export <code class="varname">MERGER</code>=<em class="replaceable"><code>merge2</code></em></strong></span>.</p><pre class="programlisting">
-#!/bin/sh
-# args: old file, new file
-kdiff3 --auto --merge --output "$2" "$@" 2&gt;/dev/null
-</pre><p>From now on, <span class="application">kdiff3</span> will be invoked to help you transfer your changes between generated files. When you are finished transferring changes, simply issue the "save the file" command and terminate <span class="application">kdiff3</span>. Or, if you do not want to transfer any changes, simply terminate <span class="application">kdiff3</span>.</p></td></tr></table></div></div><div class="section" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="usage.tools.verilog-ruby-conv"></a>Verilog to Ruby conversion</h3></div></div></div><p>The <span><strong class="command">header_to_ruby.rb</strong></span> tool can be used to convert Verilog header files into Ruby. You can try it by running the command <span><strong class="command">header_to_ruby.rb <code class="option">--help</code></strong></span>.</p></div></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="usage.html"><img src="images/prev.png" alt="Prev" /></a> </td><td width="20%" align="center"><a accesskey="u" href="usage.html"><img src="images/up.png" alt="Up" /></a></td><td width="40%" align="right"> <a accesskey="n" href="usage.tutorial.html"><img src="images/next.png" alt="Next" /></a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 4. Usage </td><td width="20%" align="center"><a accesskey="h" href="index.html"><img src="images/home.png" alt="Home" /></a></td><td width="40%" align="right" valign="top"> Tutorial</td></tr></table></div></body></html>

data/doc/usage.tutorial.html

@@ -1,189 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Tutorial</title><link rel="stylesheet" href="styles/manual.css" type="text/css" /><meta name="generator" content="DocBook XSL Stylesheets V1.68.1" /><link rel="start" href="index.html" title="Ruby-VPI user manual" /><link rel="up" href="usage.html" title="Chapter 4. Usage" /><link rel="prev" href="usage.tools.html" title="Tools" /><link rel="next" href="usage.examples.html" title="Examples" /></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Tutorial</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="usage.tools.html"><img src="images/prev.png" alt="Prev" /></a> </td><th width="60%" align="center">Chapter 4. Usage</th><td width="20%" align="right"> <a accesskey="n" href="usage.examples.html"><img src="images/next.png" alt="Next" /></a></td></tr></table><hr /></div><div class="section" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="usage.tutorial"></a>Tutorial</h2></div></div></div><div class="procedure"><a id="id2529000"></a><p class="title"><b>Procedure 4.1. Typical way of using <span class="application">Ruby-VPI</span></b></p><ol type="1"><li><p><a href="usage.tutorial.html#usage.tutorial.declare-design" title="Start with a design">Declare the design</a>, which is a Verilog module, using Verilog 2001 syntax.</p></li><li><p><a href="usage.tutorial.html#usage.tutorial.generate-test" title="Generate a test">Generate a test</a> for the design using the <a href="usage.tools.html#usage.tools.generate-test" title="Automated test generation">automated test generator</a> tool.</p></li><li><p><a href="usage.tutorial.html#usage.tutorial.specification" title="Specify your expectations">Identify your expectations</a> for the design and implement them in the specification.</p></li><li><p>(Optional) <a href="usage.tutorial.html#usage.tutorial.implement-proto" title="Implement the prototype">Implement the prototype</a> of the design in Ruby.</p></li><li><p>(Optional) <a href="usage.tutorial.html#usage.tutorial.test-proto" title="Verify the prototype">Verify the prototype</a> against the specification.</p></li><li><p><a href="usage.tutorial.html#usage.tutorial.implement-design" title="Implement the design">Implement the design</a> in Verilog once the prototype has been verified.</p></li><li><p><a href="usage.tutorial.html#usage.tutorial.test-design" title="Verify the design">Verify the design</a> against the specification.</p></li></ol></div><div class="section" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="usage.tutorial.declare-design"></a>Start with a design</h3></div></div></div><p>First, we need a <a href="glossary.html#term..design">Design</a> to verify. In this tutorial, <a href="usage.tutorial.html#fig..counter.v_decl" title="Figure 4.1. Declaration of a simple up-counter with synchronous reset">Figure 4.1, “Declaration of a simple up-counter with synchronous reset”</a> will serve as our design. Its interface is composed of the following parts:
-          </p><div class="variablelist"><dl><dt><span class="term"><code class="constant">Size</code></span></dt><dd><p>This parameter defines the number of bits used to represent the counter's value.</p></dd><dt><span class="term"><code class="varname">clock</code></span></dt><dd><p>Each positive edge of this signal causes the <code class="varname">count</code> register to increment.</p></dd><dt><span class="term"><code class="varname">reset</code></span></dt><dd><p>Assertion of this signal causes the <code class="varname">count</code> register to become zero.</p></dd><dt><span class="term"><code class="varname">count</code></span></dt><dd><p>This register contains the counter's value.</p></dd></dl></div><p>
-        </p><div class="figure"><a id="fig..counter.v_decl"></a><p class="title"><b>Figure 4.1. Declaration of a simple up-counter with synchronous reset</b></p><pre class="programlisting">
-<span class="token">module</span> counter #(<span class="token">parameter</span> <code class="constant">Size</code> = <code class="literal">5</code>) (
-  <span class="token">input</span> <code class="varname">clock</code>,
-  <span class="token">input</span> <code class="varname">reset</code>,
-  <span class="token">output</span> <span class="type">reg</span> [<code class="constant">Size</code> - <code class="literal">1</code> : <code class="literal">0</code>] <code class="varname">count</code>
-);
-<span class="token">endmodule</span>
-</pre></div><div class="important" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Important: Before we continue…"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Important]" src="images/important.png" /></td><th align="left">Before we continue…</th></tr><tr><td align="left" valign="top"><p>Save the source code shown in <a href="usage.tutorial.html#fig..counter.v_decl" title="Figure 4.1. Declaration of a simple up-counter with synchronous reset">Figure 4.1, “Declaration of a simple up-counter with synchronous reset”</a> into a file named <code class="filename">counter.v</code>.</p></td></tr></table></div></div><div class="section" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="usage.tutorial.generate-test"></a>Generate a test</h3></div></div></div><p>Now that we have a <a href="glossary.html#term..design">Design</a> to verify, let us generate a <a href="glossary.html#term..test">Test</a> for it using the <a href="usage.tools.html#usage.tools.generate-test" title="Automated test generation">automated test generator</a>. This tool allows us to implement our <a href="glossary.html#term..specification">Specification</a> in either rSpec, xUnit, or our very own format. Each format represents a different software development methodology: rSpec represents <a href="glossary.html#term..BDD"><span class="acronym">BDD</span></a>, xUnit represents <a href="glossary.html#term..TDD">TDD</a>, and our own format can represent another methodology. Both rSpec and xUnit are presented in this tutorial.</p><p>Once we have decided how we want to implement our specification, we can proceed to generate a test for our design. <a href="usage.tutorial.html#fig..generate-test.rspec" title="Figure 4.2. Generating a test with specification in rSpec format">Figure 4.2, “Generating a test with specification in rSpec format”</a> and <a href="usage.tutorial.html#fig..generate-test.unit-test" title="Figure 4.3. Generating a test with specification in xUnit format">Figure 4.3, “Generating a test with specification in xUnit format”</a> illustrate this process.</p><div class="figure"><a id="fig..generate-test.rspec"></a><p class="title"><b>Figure 4.2. Generating a test with specification in rSpec format</b></p><pre class="screen">
-<code class="prompt">$</code> <strong class="userinput"><code><span><strong class="command">generate_test.rb <em class="replaceable"><code>counter.v</code></em> <code class="option">--rspec</code> <code class="option">--name</code> <em class="replaceable"><code>rspec</code></em></strong></span></code></strong>
-<code class="computeroutput">
-    name  rspec
-  format  rSpec
-
-  module  counter
-  create  counter_rspec_runner.rake
-  create  counter_rspec_bench.v
-  create  counter_rspec_bench.rb
-  create  counter_rspec_design.rb
-  create  counter_rspec_proto.rb
-  create  counter_rspec_spec.rb
-</code>
-</pre></div><div class="figure"><a id="fig..generate-test.unit-test"></a><p class="title"><b>Figure 4.3. Generating a test with specification in xUnit format</b></p><pre class="screen">
-<code class="prompt">$</code> <strong class="userinput"><code><span><strong class="command">generate_test.rb <em class="replaceable"><code>counter.v</code></em> <code class="option">--xunit</code> <code class="option">--name</code> <em class="replaceable"><code>xunit</code></em></strong></span></code></strong>
-<code class="computeroutput">
-    name  xunit
-  format  xUnit
-
-  module  counter
-  create  counter_xunit_runner.rake
-  create  counter_xunit_bench.v
-  create  counter_xunit_bench.rb
-  create  counter_xunit_design.rb
-  create  counter_xunit_proto.rb
-  create  counter_xunit_spec.rb
-</code>
-</pre></div></div><div class="section" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="usage.tutorial.specification"></a>Specify your expectations</h3></div></div></div><p>So far, the test generation tool has created a basic foundation for our <a href="glossary.html#term..test">Test</a>. Now we must build upon this foundation by identifying our <a href="glossary.html#term..expectation">Expectation</a>s of the <a href="glossary.html#term..design">Design</a>. That is, how do we expect the design to <span class="emphasis"><em>behave</em></span> under certain conditions?</p><p>The following is a reasonable set of expectations for our simple counter:
-          </p><div class="itemizedlist"><ul type="disc"><li><p>A resetted counter's value should be zero.</p></li><li><p>A resetted counter's value should increment by one count upon each rising clock edge.</p></li><li><p>A counter with the maximum value should overflow upon increment.</p></li></ul></div><p>
-        </p><p>Now that we have identified a set of expectations for our design, we are ready to implement them in our specification. <a href="usage.tutorial.html#fig..counter_rspec_spec.rb" title="Figure 4.4. Specification implemented in rSpec format">Figure 4.4, “Specification implemented in rSpec format”</a> and <a href="usage.tutorial.html#fig..counter_xunit_spec.rb" title="Figure 4.5. Specification implemented in xUnit format">Figure 4.5, “Specification implemented in xUnit format”</a> illustrate this process. Note the striking similarities between our expectations and their implementation.</p><div class="figure"><a id="fig..counter_rspec_spec.rb"></a><p class="title"><b>Figure 4.4. Specification implemented in rSpec format</b></p><pre class="programlisting">
-<em><span class="remark"># lowest upper bound of counter's value</span></em>
-<code class="constant">LIMIT</code> = <code class="literal">2</code> ** <code class="constant">Counter</code>.<code class="function">Size</code>.<code class="function">intVal</code>
-
-<em><span class="remark"># maximum allowed value for a counter</span></em>
-<code class="constant">MAX</code> = <code class="constant">LIMIT</code> - <code class="literal">1</code>
-
-<code class="function">context</code> <code class="literal">"A resetted counter's value"</code> <span class="token">do</span>
-  <code class="function">setup</code> <span class="token">do</span>
-    <code class="constant">Counter</code>.<code class="function">reset!</code>
-  <span class="token">end</span>
-
-  <code class="function">specify</code> <code class="literal">"should be zero"</code> <span class="token">do</span>
-    <code class="constant">Counter</code>.<code class="function">count</code>.<code class="function">intVal</code>.<code class="function">should_equal</code> <code class="literal">0</code>
-  <span class="token">end</span>
-
-  <code class="function">specify</code> <code class="literal">"should increment by one count upon each rising clock edge"</code> <span class="token">do</span>
-    <code class="constant">LIMIT</code>.<code class="function">times</code> <span class="token">do</span> |<code class="varname">i</code>|
-      <code class="constant">Counter</code>.<code class="function">count</code>.<code class="function">intVal</code>.<code class="function">should_equal</code> <code class="varname">i</code>
-      <code class="function">relay_verilog</code> <em><span class="remark"># advance the clock</span></em>
-    <span class="token">end</span>
-  <span class="token">end</span>
-<span class="token">end</span>
-
-<code class="function">context</code> <code class="literal">"A counter with the maximum value"</code> <span class="token">do</span>
-  <code class="function">setup</code> <span class="token">do</span>
-    <code class="constant">Counter</code>.<code class="function">reset!</code>
-
-    <em><span class="remark"># increment the counter to maximum value</span></em>
-    <code class="constant">MAX</code>.<code class="function">times</code> <span class="token">do</span> <code class="function">relay_verilog</code> <span class="token">end</span>
-    <code class="constant">Counter</code>.<code class="function">count</code>.<code class="function">intVal</code>.<code class="function">should_equal</code> <code class="constant">MAX</code>
-  <span class="token">end</span>
-
-  <code class="function">specify</code> <code class="literal">"should overflow upon increment"</code> <span class="token">do</span>
-    <code class="function">relay_verilog</code> <em><span class="remark"># increment the counter</span></em>
-    <code class="constant">Counter</code>.<code class="function">count</code>.<code class="function">intVal</code>.<code class="function">should_equal</code> <code class="literal">0</code>
-  <span class="token">end</span>
-<span class="token">end</span>
-</pre></div><div class="figure"><a id="fig..counter_xunit_spec.rb"></a><p class="title"><b>Figure 4.5. Specification implemented in xUnit format</b></p><pre class="programlisting">
-<em><span class="remark"># lowest upper bound of counter's value</span></em>
-<code class="constant">LIMIT</code> = <code class="literal">2</code> ** <code class="constant">Counter</code>.<code class="function">Size</code>.<code class="function">intVal</code>
-
-<em><span class="remark"># maximum allowed value for a counter</span></em>
-<code class="constant">MAX</code> = <code class="constant">LIMIT</code> - <code class="literal">1</code>
-
-<span class="token">class</span> <code class="constant">ResettedCounterValue</code> &lt; <code class="constant">Test</code>::<code class="constant">Unit</code>::<code class="constant">TestCase</code>
-  <span class="token">def</span> <code class="function">setup</code>
-    <code class="constant">Counter</code>.<code class="function">reset!</code>
-  <span class="token">end</span>
-
-  <span class="token">def</span> <code class="function">test_zero</code>
-    <code class="function">assert_equal</code> <code class="literal">0</code>, <code class="constant">Counter</code>.<code class="function">count</code>.<code class="function">intVal</code>
-  <span class="token">end</span>
-
-  <span class="token">def</span> <code class="function">test_increment</code>
-    <code class="constant">LIMIT</code>.<code class="function">times</code> <span class="token">do</span> |<code class="varname">i</code>|
-      <code class="function">assert_equal</code> <code class="varname">i</code>, <code class="constant">Counter</code>.<code class="function">count</code>.<code class="function">intVal</code>
-      <code class="function">relay_verilog</code> <em><span class="remark"># advance the clock</span></em>
-    <span class="token">end</span>
-  <span class="token">end</span>
-<span class="token">end</span>
-
-<span class="token">class</span> <code class="constant">MaximumCounterValue</code> &lt; <code class="constant">Test</code>::<code class="constant">Unit</code>::<code class="constant">TestCase</code>
-  <span class="token">def</span> <code class="function">setup</code>
-    <code class="constant">Counter</code>.<code class="function">reset!</code>
-
-    <em><span class="remark"># increment the counter to maximum value</span></em>
-    <code class="constant">MAX</code>.<code class="function">times</code> <span class="token">do</span> <code class="function">relay_verilog</code> <span class="token">end</span>
-    <code class="function">assert_equal</code> <code class="constant">MAX</code>, <code class="constant">Counter</code>.<code class="function">count</code>.<code class="function">intVal</code>
-  <span class="token">end</span>
-
-  <span class="token">def</span> <code class="function">test_overflow</code>
-    <code class="function">relay_verilog</code> <em><span class="remark"># increment the counter</span></em>
-    <code class="function">assert_equal</code> <code class="literal">0</code>, <code class="constant">Counter</code>.<code class="function">count</code>.<code class="function">intVal</code>
-  <span class="token">end</span>
-<span class="token">end</span>
-</pre></div><div class="important" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Important: Before we continue…"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Important]" src="images/important.png" /></td><th align="left">Before we continue…</th></tr><tr><td align="left" valign="top"><div class="itemizedlist"><ul type="disc"><li><p>Replace the contents of the file named <code class="filename">counter_rspec_spec.rb</code> with the source code shown in <a href="usage.tutorial.html#fig..counter_rspec_spec.rb" title="Figure 4.4. Specification implemented in rSpec format">Figure 4.4, “Specification implemented in rSpec format”</a>.</p></li><li><p>Replace the contents of the file named <code class="filename">counter_xunit_spec.rb</code> with the source code shown in <a href="usage.tutorial.html#fig..counter_xunit_spec.rb" title="Figure 4.5. Specification implemented in xUnit format">Figure 4.5, “Specification implemented in xUnit format”</a>.</p></li><li><p>Replace the contents of the files named <code class="filename">counter_rspec_design.rb</code> and <code class="filename">counter_xunit_design.rb</code> with the following code. This code defines the <code class="function">reset!</code> method which resets our Verilog design.</p><pre class="programlisting">
-<span class="token">def</span> <code class="constant">Counter</code>.<code class="function">reset!</code>
-  <code class="function">reset</code>.<code class="function">intVal</code> = <code class="literal">1</code>
-  <code class="function">relay_verilog</code> <em><span class="remark"># advance the clock</span></em>
-  <code class="function">reset</code>.<code class="function">intVal</code> = <code class="literal">0</code>
-<span class="token">end</span>
-</pre></li></ul></div></td></tr></table></div></div><div class="section" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="usage.tutorial.implement-proto"></a>Implement the prototype</h3></div></div></div><p>Now that we have a <a href="glossary.html#term..specification">Specification</a> against which to verify our <a href="glossary.html#term..design">Design</a>, let us build a prototype of our design. By doing so, we exercise our specification, experience potential problems that may arise when we later implement our design in Verilog, and gain confidence in our work. <a href="usage.tutorial.html#fig..counter_proto.rb" title="Figure 4.6. Ruby prototype of our Verilog design">Figure 4.6, “Ruby prototype of our Verilog design”</a> shows the completed prototype for our design.</p><div class="figure"><a id="fig..counter_proto.rb"></a><p class="title"><b>Figure 4.6. Ruby prototype of our Verilog design</b></p><pre class="programlisting">
-<span class="token">def</span> <code class="constant">Counter</code>.<code class="function">simulate!</code>
-  <span class="token">if</span> <code class="function">reset</code>.<code class="function">intVal</code> == <code class="literal">1</code>
-    <code class="function">count</code>.<code class="function">intVal</code> = <code class="literal">0</code>
-  <span class="token">else</span>
-    <code class="function">count</code>.<code class="function">intVal</code> += <code class="literal">1</code>
-  <span class="token">end</span>
-<span class="token">end</span>
-</pre></div><div class="important" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Important: Before we continue…"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Important]" src="images/important.png" /></td><th align="left">Before we continue…</th></tr><tr><td align="left" valign="top"><p>Replace the contents of the files named <code class="filename">counter_rspec_proto.rb</code> and <code class="filename">counter_xunit_proto.rb</code> with the source code shown in <a href="usage.tutorial.html#fig..counter_proto.rb" title="Figure 4.6. Ruby prototype of our Verilog design">Figure 4.6, “Ruby prototype of our Verilog design”</a>.</p></td></tr></table></div></div><div class="section" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="usage.tutorial.test-proto"></a>Verify the prototype</h3></div></div></div><p>Now that we have implemented our prototype, we are ready to verify it against our <a href="glossary.html#term..specification">Specification</a> by running the <a href="glossary.html#term..test">Test</a>. <a href="usage.tutorial.html#fig..test-proto.rspec" title="Figure 4.7. Running a test with specification in rSpec format">Figure 4.7, “Running a test with specification in rSpec format”</a> and <a href="usage.tutorial.html#fig..test-proto.unit-test" title="Figure 4.8. Running a test with specification in xUnit format">Figure 4.8, “Running a test with specification in xUnit format”</a> illustrate this process.</p><div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Tip: Reuse your past efforts!"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Tip]" src="images/tip.png" /></td><th align="left">Reuse your past efforts!</th></tr><tr><td align="left" valign="top"><p>The <span class="emphasis"><em>same</em></span> specification can be used to verify both prototype and design.</p></td></tr></table></div><p>Here, the <code class="varname">PROTOTYPE</code> environment variable is assigned a non-empty value while running the test, so that, instead of our design, our prototype is verified against our specification. You can also assign a value to <code class="varname">PROTOTYPE</code> before running the test, by using your shell's <span><strong class="command">export</strong></span> or <span><strong class="command">setenv</strong></span> command. Finally, the Icarus Verilog simulator, denoted by <em class="replaceable"><code>cver</code></em>, is used to run the simulation.</p><div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Tip: What can the test runner do?"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Tip]" src="images/tip.png" /></td><th align="left">What can the test runner do?</th></tr><tr><td align="left" valign="top"><p>If you invoke the test runner (1) without any arguments or (2) with the <code class="option">-T</code> option, it will show you a list of tasks that it can perform for you.</p></td></tr></table></div><div class="figure"><a id="fig..test-proto.rspec"></a><p class="title"><b>Figure 4.7. Running a test with specification in rSpec format</b></p><pre class="screen">
-<code class="prompt">$</code> <strong class="userinput"><code><span><strong class="command">rake <code class="option">-f</code> <em class="replaceable"><code>counter_rspec_runner.rake</code></em> <em class="replaceable"><code>cver</code></em> <code class="varname">PROTOTYPE</code>=<em class="replaceable"><code>1</code></em></strong></span></code></strong>
-<code class="computeroutput">counter_rspec: verifying prototype instead of design
-
-A resetted counter's value
-- should be zero
-- should increment by one count upon each rising clock edge
-
-A counter with the maximum value
-- should overflow upon increment
-
-Finished in 0.018199 seconds
-
-3 specifications, 0 failures</code>
-</pre></div><div class="figure"><a id="fig..test-proto.unit-test"></a><p class="title"><b>Figure 4.8. Running a test with specification in xUnit format</b></p><pre class="screen">
-<code class="prompt">$</code> <strong class="userinput"><code><span><strong class="command">rake <code class="option">-f</code> <em class="replaceable"><code>counter_xunit_runner.rake</code></em> <em class="replaceable"><code>cver</code></em> <code class="varname">PROTOTYPE</code>=<em class="replaceable"><code>1</code></em></strong></span></code></strong>
-<code class="computeroutput">counter_xunit: verifying prototype instead of design
-
-Loaded suite counter_xunit_bench
-Started
-...
-Finished in 0.040668 seconds.
-
-3 tests, 35 assertions, 0 failures, 0 errors</code>
-</pre></div></div><div class="section" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="usage.tutorial.implement-design"></a>Implement the design</h3></div></div></div><p>Now that we have implemented and verified our prototype, we are ready to implement our <a href="glossary.html#term..design">Design</a>. This is often quite simple because we translate <span class="emphasis"><em>existing</em></span> code from Ruby (our prototype) into Verilog (our design). <a href="usage.tutorial.html#fig..counter.v_impl" title="Figure 4.9. Implementation of a simple up-counter with synchronous reset">Figure 4.9, “Implementation of a simple up-counter with synchronous reset”</a> illustrates the result of this process. Once again, note the striking similarities between the implementation of our prototype and design.</p><div class="figure"><a id="fig..counter.v_impl"></a><p class="title"><b>Figure 4.9. Implementation of a simple up-counter with synchronous reset</b></p><pre class="programlisting">
-<span class="token">module</span> counter #(<span class="token">parameter</span> <code class="constant">Size</code> = <code class="literal">5</code>) (
-  <span class="token">input</span> <code class="varname">clock</code>,
-  <span class="token">input</span> <code class="varname">reset</code>,
-  <span class="token">output</span> <span class="type">reg</span> [<code class="constant">Size</code> - <code class="literal">1</code> : <code class="literal">0</code>] <code class="varname">count</code>
-);
-  <span class="token">always</span> @(<span class="token">posedge</span> <code class="varname">clock</code>) <span class="token">begin</span>
-    <span class="token">if</span> (<code class="varname">reset</code>)
-      <code class="varname">count</code> &lt;= <code class="literal">0</code>;
-    <span class="token">else</span>
-      <code class="varname">count</code> &lt;= <code class="varname">count</code> + <code class="literal">1</code>;
-  <span class="token">end</span>
-<span class="token">endmodule</span>
-</pre></div><div class="important" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Important: Before we continue…"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Important]" src="images/important.png" /></td><th align="left">Before we continue…</th></tr><tr><td align="left" valign="top"><p>Replace the contents of the file named <code class="filename">counter.v</code> with the source code shown in <a href="usage.tutorial.html#fig..counter.v_impl" title="Figure 4.9. Implementation of a simple up-counter with synchronous reset">Figure 4.9, “Implementation of a simple up-counter with synchronous reset”</a>.</p></td></tr></table></div></div><div class="section" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="usage.tutorial.test-design"></a>Verify the design</h3></div></div></div><p>Now that we have implemented our <a href="glossary.html#term..design">Design</a>, we are ready to verify it against our <a href="glossary.html#term..specification">Specification</a> by running the <a href="glossary.html#term..test">Test</a>. <a href="usage.tutorial.html#fig..test-design.rspec" title="Figure 4.10. Running a test with specification in rSpec format">Figure 4.10, “Running a test with specification in rSpec format”</a> and <a href="usage.tutorial.html#fig..test-design.unit-test" title="Figure 4.11. Running a test with specification in xUnit format">Figure 4.11, “Running a test with specification in xUnit format”</a> illustrate this process.</p><p>Here, the <code class="varname">PROTOTYPE</code> environment variable is <span class="emphasis"><em>not</em></span> specified while running the test, so that our design, instead of our prototype, is verified against our specification. You can also achieve this effect by assigning an empty value to <code class="varname">PROTOTYPE</code>, or by using your shell's <span><strong class="command">unset</strong></span> command. Finally, the GPL Cver Verilog simulator, denoted by <em class="replaceable"><code>cver</code></em>, is used to run the simulation.</p><div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Tip: Running multiple tests"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Tip]" src="images/tip.png" /></td><th align="left">Running multiple tests</th></tr><tr><td align="left" valign="top"><p>Create a file named <code class="filename">Rakefile</code> containing the following line.</p><pre class="programlisting">require 'ruby-vpi/runner_proxy'</pre><p>Now you can invoke all test runners in the current directory simply by executing <span><strong class="command">rake <em class="replaceable"><code>cver</code></em></strong></span> (where <em class="replaceable"><code>cver</code></em> denotes the GPL Cver simulator).</p></td></tr></table></div><div class="figure"><a id="fig..test-design.rspec"></a><p class="title"><b>Figure 4.10. Running a test with specification in rSpec format</b></p><pre class="screen">
-<code class="prompt">$</code> <strong class="userinput"><code><span><strong class="command">rake <code class="option">-f</code> <em class="replaceable"><code>counter_rspec_runner.rake</code></em> <em class="replaceable"><code>cver</code></em></strong></span></code></strong>
-<code class="computeroutput">A resetted counter's value
-- should be zero
-- should increment by one count upon each rising clock edge
-
-A counter with the maximum value
-- should overflow upon increment
-
-Finished in 0.005628 seconds
-
-3 specifications, 0 failures</code>
-</pre></div><div class="figure"><a id="fig..test-design.unit-test"></a><p class="title"><b>Figure 4.11. Running a test with specification in xUnit format</b></p><pre class="screen">
-<code class="prompt">$</code> <strong class="userinput"><code><span><strong class="command">rake <code class="option">-f</code> <em class="replaceable"><code>counter_xunit_runner.rake</code></em> <em class="replaceable"><code>cver</code></em></strong></span></code></strong>
-<code class="computeroutput">Loaded suite counter_xunit_bench
-Started
-...
-Finished in 0.006766 seconds.
-
-3 tests, 35 assertions, 0 failures, 0 errors</code>
-</pre></div></div></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="usage.tools.html"><img src="images/prev.png" alt="Prev" /></a> </td><td width="20%" align="center"><a accesskey="u" href="usage.html"><img src="images/up.png" alt="Up" /></a></td><td width="40%" align="right"> <a accesskey="n" href="usage.examples.html"><img src="images/next.png" alt="Next" /></a></td></tr><tr><td width="40%" align="left" valign="top">Tools </td><td width="20%" align="center"><a accesskey="h" href="index.html"><img src="images/home.png" alt="Home" /></a></td><td width="40%" align="right" valign="top"> Examples</td></tr></table></div></body></html>

data/header.html

@@ -1,95 +0,0 @@
-<head>
-  <link rel="stylesheet" type="text/css" href="style.css" />
-</head>
-
-<div class="variablelist">
-<dl>
-
-<dt>
-<span class="term">
-<a href="./doc/usage.tutorial.html" target="_top">Tutorial</a>
-</span>
-</dt>
-<dd>
-<p>Learn how to use Ruby-VPI quickly.</p>
-</dd>
-
-<dt>
-<span class="term">
-<a href="./doc/" target="_top">Manual</a>
-</span>
-</dt>
-<dd>
-<p>Complete documentation for users. <em>Start here!</em></p>
-</dd>
-
-<dt>
-<span class="term">
-<a href="./ref/" target="_top">Reference</a>
-</span>
-</dt>
-<dd>
-<p><span class="caps">API</span> reference documentation for Ruby libraries and C extension.</p>
-</dd>
-
-<dt>
-<span class="term">
-<a href="http://rubyforge.org/projects/ruby-vpi" target="_top">
-Facilities</a>
-</span>
-</dt>
-<dd>
-<p>
-Access the issue tracker, file downloads, support requests, discussion forums, and more at <a href="http://rubyforge.org" target="_top">
-RubyForge</a>.
-</p>
-</dd>
-
-<dt>
-<span class="term">
-<a href="http://ruby-vpi.rubyforge.org" target="_top">
-Project</a>
-</span>
-</dt>
-<dd>
-<p>
-Access more information at the project&#8217;s home page.
-</p>
-</dd>
-
-<dt>
-<span class="term">
-<a href="http://ruby-vpi.rubyforge.org/src/ruby-vpi" target="_top">
-Sources</a>
-</span>
-</dt>
-<dd>
-<p>
-Browse or access the source code repository.</p>
-</dd>
-
-<dt>
-<span class="term">
-<a href="http://ruby-vpi.rubyforge.org/talks" target="_top">
-Talks</a>
-</span>
-</dt>
-<dd>
-<p>
-Access public presentations about Ruby-VPI.</p>
-</dd>
-
-<dt>
-<span class="term">
-<a href="http://ruby-vpi.rubyforge.org/blog" target="_top">
-News</a>
-</span>
-</dt>
-<dd>
-<p>
-See what the developers are cooking up.</p>
-</dd>
-
-</dl>
-</div>
-</div>