ruby-vpi 12.0.0 → 12.0.1

data/doc/history.rb

@@ -1,8 +1,11 @@
 require 'yaml'
 @history = YAML.load_file(File.join(File.dirname(__FILE__), 'history.yml'))
 
+# note: @history is an array of hashes
+
+
 def format_history_entry aEntry
-  output = "h1. Version #{aEntry['Version']} (#{aEntry['Date']})\n\n"
+  output = "h1(##{aEntry['Version']}). Version #{aEntry['Version']} (#{aEntry['Date']})\n\n"
 
   %w[Summary Acknowledgment Notice Detail].each do |key|
     if content = aEntry[key]

data/doc/history.yml

@@ -1,3 +1,20 @@
+-
+  Version: 12.0.1
+
+  Date: 2006-12-18
+
+  Summary: |
+    This release fixes a problem in code coverage analysis.
+
+  Acknowledgment: |
+    Thanks to Mauricio Fernandez for helping me solve the problem.
+
+  Detail: |
+    Previously, code coverage reports were not providing any useful information because they were being generated _before_ the test had a chance to run. This problem has been fixed -- code coverage reports are now generated _after_ the test has finished running.
+
+    This problem was wholly due to programmer error (i.e. my mistake @;-)@) because I had forgotten that @Kernel.at_exit@ invokes the blocks passed to it in _reverse_ order. So, the coverage report was being generated before Test::Unit had a chance to run (it also uses @Kernel.at_exit@).
+
+
 -
   Version: 12.0.0
 
@@ -298,7 +315,7 @@
   Date: 2006-09-15
 
   Summary: |
-    This release adds initial[1] support for code coverage analysis via the "rcov library":http://eigenclass.org/hiki.rb?rcov.
+    This release adds initial support for code coverage analysis via the "rcov library":http://eigenclass.org/hiki.rb?rcov.
 
   Acknowledgment: |
     Thanks to Mauricio Fernandez for helping me use rcov without its runner.

data/doc/images/feed-icon.LICENSE

@@ -0,0 +1,2 @@
+The file named "feed-icon.svg" is released under a MPL/GPL/LGPL tri-licence.
+See http://www.mozilla.org/foundation/feed-icon-guidelines/faq.html for details.

data/doc/images/feed-icon.svg

@@ -0,0 +1,18 @@
+<?xml version="1.0"?>
+<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd"> 
+<svg xmlns="http://www.w3.org/2000/svg" version="1.1" width="128px" height="128px" id="RSSicon" viewBox="0 0 256 256">
+<defs>
+<linearGradient x1="0.085" y1="0.085" x2="0.915" y2="0.915" id="RSSg">
+<stop  offset="0.0" stop-color="#E3702D"/><stop  offset="0.1071" stop-color="#EA7D31"/>
+<stop  offset="0.3503" stop-color="#F69537"/><stop  offset="0.5" stop-color="#FB9E3A"/>
+<stop  offset="0.7016" stop-color="#EA7C31"/><stop  offset="0.8866" stop-color="#DE642B"/>
+<stop  offset="1.0" stop-color="#D95B29"/>
+</linearGradient>
+</defs>
+<rect width="256" height="256" rx="55" ry="55" x="0"  y="0"  fill="#CC5D15"/>
+<rect width="246" height="246" rx="50" ry="50" x="5"  y="5"  fill="#F49C52"/>
+<rect width="236" height="236" rx="47" ry="47" x="10" y="10" fill="url(#RSSg)"/>
+<circle cx="68" cy="189" r="24" fill="#FFF"/>
+<path d="M160 213h-34a82 82 0 0 0 -82 -82v-34a116 116 0 0 1 116 116z" fill="#FFF"/>
+<path d="M184 213A140 140 0 0 0 44 73 V 38a175 175 0 0 1 175 175z" fill="#FFF"/>
+</svg>

data/doc/intro.inc

@@ -3,7 +3,7 @@ bq. Ruby-VPI is a "Ruby":http://www.ruby-lang.org interface to "Verilog VPI":htt
 
 h2(#intro.features). Features
 
-* Supports the _entire_ IEEE Std 1364-2005 VPI standard.
+* Supports the _entire_ "IEEE Std 1364-2005"::http://ieeexplore.ieee.org/xpl/standardstoc.jsp?isnumber=33945 VPI standard.
 
 * Works with all "major Verilog simulators":manual.html#setup.reqs available today.
 ** Compile _once_ (during "installation":manual.html#setup.installation) and use forever!

data/doc/lib/doc_format.rb

@@ -24,16 +24,56 @@ require 'coderay'
 require 'redcloth'
 
 class String
+  # The content of these HTML tags will be preserved verbatim when they are processed by Textile.
+  PRESERVED_TAGS = [:code, :tt]
+
+  # Transforms this string into HTML.
+  def to_html
+    text = dup
+
+    # prevent the content of these tags from being transformed by Textile
+    # for example, Textile transforms quotation marks in code into curly ones ( ) -- this ruins any source code in the content of the tags!
+      PRESERVED_TAGS.each do |tag|
+        text.gsub! %r{<#{tag}(.*?)>(.*?)</#{tag}>}m, %{<pre tag=#{tag.inspect}\\1>\\2</pre>}
+      end
+
+    html = text.redcloth
+
+    # restore the original tags for the preserved tags
+      # unescape content of <pre> tags because they may contain nested preserved tags (redcloth escapes the content of <pre> tags)
+        html.gsub! %r{(<pre>)(.*?)(</pre>)}m do
+          $1 + CGI.unescapeHTML($2) + $3
+        end
+
+      PRESERVED_TAGS.each do |tag|
+        html.gsub! %r{<pre tag=#{tag.inspect}(.*?)>(.*?)</pre>}m, %{<#{tag}\\1>\\2</#{tag}>}
+      end
+
+      # assume that indented text in Textile is NOT source code
+        html.gsub! %r{(<pre>)\s*<code>(.*?)\s*</code>\s*(</pre>)}m, '\1\2\3'
+
+      # escape content of <pre> tags, because we un-escaped it above
+        html.gsub! %r{(<pre>)(.*?)(</pre>)}m do
+          $1 + CGI.escapeHTML($2) + $3
+        end
+
+    html.coderay
+  end
+
   # Returns the result of running this string through RedCloth.
   def redcloth
     RedCloth.new(self).to_html
   end
 
-  # Adds syntax coloring to <code>...</code> elements in the given text. If the <code> tag has an attribute lang="...", then that is considered the programming language for which appropriate syntax coloring should be applied. Otherwise, the programming language is assumed to be ruby.
+  # Adds syntax coloring to <code> elements in the given text. If
+  # the <code> tag has an attribute lang="...", then that is considered the
+  # programming language for which appropriate syntax coloring should be
+  # applied. Otherwise, the programming language is assumed to be ruby.
   def coderay
     gsub %r{<(code)(.*?)>(.*?)</\1>}m do
-      code = CGI.unescapeHTML($3)
+      code = CGI.unescapeHTML $3
       atts = $2
+
       lang =
         if $2 =~ /lang=('|")(.*?)\1/i
           $2
@@ -41,8 +81,7 @@ class String
           :ruby
         end
 
-
-      type =
+      tag =
         if code =~ /\n/
           :pre
         else
@@ -51,12 +90,7 @@ class String
 
       html = CodeRay.scan(code, lang).html(:css => :style)
 
-      %{<#{type} class="code"#{atts}>#{html}</#{type}>}
+      %{<#{tag} class="code"#{atts}>#{html}</#{tag}>}
     end
   end
-
-  def to_html
-    redcloth.coderay
-  end
 end
-

data/doc/lib/doc_proxy.rb

@@ -24,6 +24,7 @@ require 'erb_proxy'
 class DocProxy < ErbProxy
   Block = Struct.new :anchor, :title, :type
   Heading = Struct.new :anchor, :title, :depth
+  @@anchorNum = 0
 
   CATEGORIES = {
     :admonition => [:tip, :note, :important, :caution, :warning],
@@ -65,25 +66,25 @@ class DocProxy < ErbProxy
     buffer = aResult
 
     # parse document structure and insert anchors (so that the table of contents can link directly to these headings) where necessary
-      buffer.gsub! %r{^(\s*h(\d))(\.|\(.*?\)\.)(.*)$} do
-        target = $~.dup
-
-        title = target[4].strip
-        depth = target[2].to_i
-
-        hasAnchor = target[3] =~ /#([^#]+)\)/
-        anchor = $1 || "anchor#{headings.length}"
-
-
-        @headings << Heading.new(anchor, title, depth)
+      buffer.gsub! %r{^(\s*h(\d))(.*)$} do
+        head, depth, rest = $1, $2, $3
+
+        # parse title and class attributes
+          rest =~ /^([\{\(\[].*?[\]\)\}])?\.(.*)$/
+          atts, title = $1, $2.strip
+
+        # parse and insert anchor if necessary
+          if atts =~ /#(.*?)\)/
+            anchor = $1
+          else
+            anchor = "anchor#{@@anchorNum += 1}"
+            rest.insert 0, "(##{anchor})"
+          end
+
+        @headings << Heading.new(anchor, title, depth.to_i)
         @blocks[:section] << Block.new(anchor, title, :section)
 
-
-        if hasAnchor
-          target.to_s
-        else
-          "#{target[1]}(##{anchor})#{target[3]}#{target[4]}"
-        end
+        head + rest
       end
 
     # expand cross-references into links to their targets

data/doc/{manual.erb → manual.doc}

@@ -118,7 +118,7 @@ In the event that a child handle has the same name as a VPI property, the child
 |_. Operation |_. _ |_. Property |_. _ |_. Accessor |_. Addendum |
 |\2. optional       | required   |\3. optional                   |
 
-* *Operation* suggests a method that should be invoked in the context of the Property parameter.
+* *Operation* suggests a method that should be invoked in the context of the Property parameter. All "methods in the Enumerable module":http://www.ruby-doc.org/core/classes/Enumerable.html are available as operations.
 
 * *Property* suggests a VPI property that should be accessed. The "vpi" prefix, which is common to all VPI properties, can be omitted if you wish. For example, the VPI property "vpiFullName" is considered equivalent to "fullName" and "FullName", but not equivalent "full_name".
 
@@ -321,7 +321,7 @@ h1(#usage). Usage
 
 h2(#usage.tools). Tools
 
-The <tt>bin</tt> directory contains various utilities which ease the process of writing tests. Each tool provides help and usage information invoked with the <tt>-h</tt> option.
+The <tt>bin</tt> directory contains various utilities which ease the process of writing tests. Each tool provides help and usage information invoked with the <tt>--help</tt> option.
 
 
 h3(#usage.tools.generate-test). Automated test generation
@@ -530,7 +530,7 @@ Finished in 0.040668 seconds.
 In these examples, the @PROTOTYPE@ 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 @PROTOTYPE@ before running the test, by using your shell's *export* or *setenv* command. Finally, the "GPL Cver simulator":#setup.reqs, denoted by _cver_, is used to run the simulation.
 
 <% tip "What can the test runner do?" do %>
-If you invoke the test runner (1) without any arguments or (2) with the <tt>-T</tt> option, it will show you a list of tasks that it can perform for you.
+If you invoke the test runner (1) without any arguments or (2) with the <tt>--tasks</tt> option, it will show you a list of tasks that it can perform for you.
 <% end %>
 
 

data/doc/manual.html

@@ -1,19 +1,18 @@
-
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
 <html>
   <head>
     <meta http-equiv="content-type" content="text/html; charset=utf-8"/>
     <link rel="stylesheet" type="text/css" href="common.css" />
+    <link rel="alternate" type="application/rss+xml" href="http://ruby-vpi.rubyforge.org/doc/rss.xml" title="RSS feed for this project." />
     <title>Ruby-VPI user manual</title>
   </head>
   <body>
-  
-    <div id="navigation">
+      <div id="navigation">
       <p><a href="readme.html"><img src="images/home.png" title="project home" alt="project home" /></a></p>
 
       <h1>Contents</h1>
       <ul>
-	<li><a href="#anchor0">Ruby-VPI user manual</a>
+	<li><a href="#anchor5">Ruby-VPI user manual</a>
 	<ul>
 	<li><a href="#terms">Terms</a></li>
 	</ul>
@@ -141,22 +140,16 @@
 	</ul></li>
 	</ul>
 
-      
-        <h1>Admonitions</h1>
+              <h1>Admonitions</h1>
 
-        
-          
-            <h2>Tips</h2>
+                              <h2>Tips</h2>
             <ol>
 	<li><a href="#tip1">Add support for your Verilog simulator</a></li>
 		<li><a href="#tip2">Using <strong>kdiff3</strong> with the automated test generator.</a></li>
 		<li><a href="#tip3">What can the test runner do?</a></li>
 		<li><a href="#tip4">Running multiple tests at once.</a></li>
 	</ol>
-          
-        
-          
-            <h2>Notes</h2>
+                                        <h2>Notes</h2>
             <ol>
 	<li><a href="#note1">note1</a></li>
 		<li><a href="#note2">Undefined symbols in Windows</a></li>
@@ -166,28 +159,16 @@
 		<li><a href="#note6">Fixed in 2.0.0.</a></li>
 		<li><a href="#note7">Fixed in 2.0.0.</a></li>
 	</ol>
-          
-        
-          
-            <h2>Importants</h2>
+                                        <h2>Importants</h2>
             <ol>
 	<li><a href="#important1">Before we continue&#8230;</a></li>
 		<li><a href="#important2">Before we continue&#8230;</a></li>
 		<li><a href="#important3">Before we continue&#8230;</a></li>
 		<li><a href="#important4">Before we continue&#8230;</a></li>
 	</ol>
-          
-        
-          
-        
-          
-        
-      
-        <h1>Formals</h1>
-
-        
-          
-            <h2>Figures</h2>
+                                                                    <h1>Formals</h1>
+
+                              <h2>Figures</h2>
             <ol>
 	<li><a href="#fig..organization">Overall organization of a test</a></li>
 		<li><a href="#fig..organization.detail">Detailed organization of a test</a></li>
@@ -195,17 +176,11 @@
 		<li><a href="#fig..ruby_init">Initialization of a test</a></li>
 		<li><a href="#fig..ruby_relay">Execution of a test</a></li>
 	</ol>
-          
-        
-          
-            <h2>Tables</h2>
+                                        <h2>Tables</h2>
             <ol>
 	<li><a href="#table1">Possible accessors and their implications</a></li>
 	</ol>
-          
-        
-          
-            <h2>Examples</h2>
+                                        <h2>Examples</h2>
             <ol>
 	<li><a href="#example1">Examples of accessing a handle&#8217;s <span class="caps">VPI</span> properties</a></li>
 		<li><a href="#fig..counter.v_decl">Declaration of a simple up-counter with synchronous reset</a></li>
@@ -223,24 +198,16 @@
 		<li><a href="#ex..TestFoo_bad">Bad design with unconnected registers</a></li>
 		<li><a href="#ex..TestFoo_fix">Fixed design with wired registers</a></li>
 	</ol>
-          
-        
-          
-        
-          
-        
-      
-    </div>
-  
-    <div class="cover-page">
+                                                                </div>
+      <div class="cover-page">
 
-	<h1 id="anchor0">Ruby-VPI user manual</h1>
+	<h1 id="anchor5">Ruby-VPI user manual</h1>
 
 
 	<p>Suraj N. Kurapati</p>
 
 
-	<p>Thu Dec 07 15:09:49 <span class="caps">PST 2006</span></p>
+	<p>Mon Dec 18 12:07:24 <span class="caps">PST 2006</span></p>
 
 
 </div>
@@ -266,7 +233,7 @@
 
 
 	<ul>
-	<li>Supports the <em>entire</em> IEEE Std 1364-2005 <span class="caps">VPI</span> standard.</li>
+	<li>Supports the <em>entire</em> <a href=":http://ieeexplore.ieee.org/xpl/standardstoc.jsp?isnumber=33945"><span class="caps">IEEE</span> Std 1364-2005</a> VPI standard.</li>
 	</ul>
 
 
@@ -439,9 +406,7 @@
 </div>
 
 </div>
-
-	<p>As a newcomer into the world of Verilog, I often heard the term <strong>test bench</strong>: &#8220;I ran the test bench, but it didn&#8217;t work!&#8221; or &#8220;Are you crazy?!! You <em>still</em> haven&#8217;t written the test bench?&#8221;, for example. I poured through my textbook for a definition of the term, but it was to no avail. Instead, it nonchalantly employed the term <em>throughout</em> its being, as if mocking my ignorance of what seems to be universal knowledge.</p>
-
+As a newcomer into the world of Verilog, I often heard the term <strong>test bench</strong>: &#8220;I ran the test bench, but it didn&#8217;t work!&#8221; or &#8220;Are you crazy?!! You <em>still</em> haven&#8217;t written the test bench?&#8221;, for example. I poured through my textbook for a definition of the term, but it was to no avail. Instead, it nonchalantly employed the term <em>throughout</em> its being, as if mocking my ignorance of what seems to be universal knowledge.
 
 	<p>Defeated, I turned to my inner faculties to determine the answer. Let&#8217;s see, the term <em>test bench</em> has the word <em>test</em>&mdash;so it has something to do with testing&mdash;and it has the word <em>bench</em>&mdash;so maybe it&#8217;s referring to a table where the testing should occur. This reasoning grew increasingly familiar as my mind rummaged through towering stores of obsolescence and ultimately revealed dreaded memories of sleepless anguish: debugging electronics in the robotics laboratory.</p>
 
@@ -468,9 +433,7 @@
 </div>
 
 </div>
-
-	<p>As <a href="#fig..organization">the figure named &ldquo;Overall organization of a test&rdquo;</a> shows, a <a href="#glossary.test">test</a> is composed of a <a href="#glossary.bench">bench</a>, a <a href="#glossary.design">design</a>, and a <a href="#glossary.specification">specification</a>.</p>
-
+As <a href="#fig..organization">the figure named &ldquo;Overall organization of a test&rdquo;</a> shows, a <a href="#glossary.test">test</a> is composed of a <a href="#glossary.bench">bench</a>, a <a href="#glossary.design">design</a>, and a <a href="#glossary.specification">specification</a>.
 
 	<p>To extend the <a href="#background.vocab">analogy of an electronics laboratory</a>, the <em>bench</em> acts as the laboratory bench which provides measurement and manipulation tools. The <em>design</em> acts as the electronic component being verified by the engineer. And the <em>specification</em> acts as the engineer who measures, manipulates, and verifies the electronic component.</p>
 
@@ -491,9 +454,7 @@
 </div>
 
 </div>
-
-	<p>In <a href="#fig..organization.detail">the figure named &ldquo;Detailed organization of a test&rdquo;</a>, Ruby-VPI acts as the <em>bench</em>, a Verilog simulator encapsulates the <em>design</em>, and a Ruby interpreter encapsulates the <em>specification</em>.</p>
-
+In <a href="#fig..organization.detail">the figure named &ldquo;Detailed organization of a test&rdquo;</a>, Ruby-VPI acts as the <em>bench</em>, a Verilog simulator encapsulates the <em>design</em>, and a Ruby interpreter encapsulates the <em>specification</em>.
 
 	<p>Notice that Ruby-VPI encapsulates all communication between the Ruby interpreter and <span class="caps">VPI</span>. This allows the specification, or any Ruby program in general, to access <span class="caps">VPI</span> using nothing more than the Ruby language! Thus, Ruby-VPI removes the burden of having to write C programs in order to access <span class="caps">VPI</span>.</p>
 
@@ -561,7 +522,7 @@
 
 
 	<ul>
-	<li><strong>Operation</strong> suggests a method that should be invoked in the context of the Property parameter.</li>
+	<li><strong>Operation</strong> suggests a method that should be invoked in the context of the Property parameter. All <a href="http://www.ruby-doc.org/core/classes/Enumerable.html">methods in the Enumerable module</a> are available as operations.</li>
 	</ul>
 
 
@@ -583,7 +544,6 @@
 </div>
 
 </div>
-
 <div class="formal">
 
 <div class="table" id="table1">
@@ -635,7 +595,6 @@
 </div>
 
 </div>
-
 <div class="formal">
 
 <div class="example" id="example1">
@@ -1083,12 +1042,8 @@
 </div>
 
 </div>
-
-	<ul>
-	<li><strong>make</strong>
-  &#8211; any distribution should be acceptable.</li>
-	</ul>
-
+* <strong>make</strong>
+  &#8211; any distribution should be acceptable.
 
 	<ul>
 	<li>C compiler
@@ -1174,14 +1129,10 @@ $ ls -d /usr/lib/ruby/gems/1.8/gems/ruby-vpi*
 </div>
 
 </div>
+* Search for object files whose names end with <tt>.so</tt>, <tt>.o</tt>, or <tt>.dll</tt> in your Verilog simulator&#8217;s installation directory.
 
 	<ul>
-	<li>Search for object files whose names end with <tt>.so</tt>, <tt>.o</tt>, or <tt>.dll</tt> in your Verilog simulator&#8217;s installation directory.</li>
-	</ul>
-
-
-	<ul>
-	<li>Determine which object files, among those found in the previous step, contain symbols whose names begin with &#8220;_vpi&#8221; by running the <pre>for x in *.{o,so,dll}; do nm $x | grep -q '[Tt] _vpi' &#38;&#38; echo $x; done</pre> command in Cygwin.
+	<li>Determine which object files, among those found in the previous step, contain symbols whose names begin with &#8220;_vpi&#8221; by running the <pre>for x in *.{o,so,dll}; do nm $x | grep -q '[Tt] _vpi' &amp;&amp; echo $x; done</pre> command in Cygwin.
 	<ul>
 	<li>If you are using Mentor Modelsim, the desired object file can be found at a path similar to <tt>C:\Modeltech\win32\libvsim.dll</tt>.</li>
 		<li>If you are using <span class="caps">GPL</span> Cver, the desired object file can be found at a path similar to <tt>C:\gplcver\objs\v_vpi.o</tt>.</li>
@@ -1231,7 +1182,7 @@ $ ls -d /usr/lib/ruby/gems/1.8/gems/ruby-vpi*
 	<h2 id="usage.tools">Tools</h2>
 
 
-	<p>The <tt>bin</tt> directory contains various utilities which ease the process of writing tests. Each tool provides help and usage information invoked with the <tt>-h</tt> option.</p>
+	<p>The <tt>bin</tt> directory contains various utilities which ease the process of writing tests. Each tool provides help and usage information invoked with the <tt>--help</tt> option.</p>
 
 
 	<h3 id="usage.tools.generate-test">Automated test generation</h3>
@@ -1342,7 +1293,6 @@ endmodule
 </div>
 
 </div>
-
 <div class="admonition">
 
 <div class="important" id="important1">
@@ -1390,9 +1340,7 @@ Each format represents a different software development methodology:
 </div>
 
 </div>
-
-	<p>Once we have decided how we want to implement our specification, we can proceed to generate a test for our design. This process is illustrated by <a href="#fig..generate-test.rspec">the example named &ldquo;Generating a test with specification in rSpec format&rdquo;</a> and <a href="#fig..generate-test.unit-test">the example named &ldquo;Generating a test with specification in xUnit format&rdquo;</a>.</p>
-
+Once we have decided how we want to implement our specification, we can proceed to generate a test for our design. This process is illustrated by <a href="#fig..generate-test.rspec">the example named &ldquo;Generating a test with specification in rSpec format&rdquo;</a> and <a href="#fig..generate-test.unit-test">the example named &ldquo;Generating a test with specification in xUnit format&rdquo;</a>.
 
 <div class="formal">
 
@@ -1416,7 +1364,6 @@ $ generate_test.rb counter.v --rspec --name rspec
 </div>
 
 </div>
-
 <div class="formal">
 
 <div class="example" id="fig..generate-test.unit-test">
@@ -1508,7 +1455,6 @@ context <span style="background-color:#fff0f0"><span style="color:#710">&quot;</
 </div>
 
 </div>
-
 <div class="formal">
 
 <div class="example" id="fig..counter_xunit_spec.rb">
@@ -1560,7 +1506,6 @@ context <span style="background-color:#fff0f0"><span style="color:#710">&quot;</
 </div>
 
 </div>
-
 <div class="admonition">
 
 <div class="important" id="important2">
@@ -1617,7 +1562,6 @@ context <span style="background-color:#fff0f0"><span style="color:#710">&quot;</
 </div>
 
 </div>
-
 <div class="admonition">
 
 <div class="important" id="important3">
@@ -1651,7 +1595,7 @@ context <span style="background-color:#fff0f0"><span style="color:#710">&quot;</
 <pre>
 $ rake -f counter_rspec_runner.rake cver PROTOTYPE=1
 
-Ruby-VPI: prototype has been enabled for test "counter_rspec" 
+Ruby-VPI: prototype has been enabled for test &quot;counter_rspec&quot; 
 
 A resetted counter's value
 - should be zero
@@ -1668,7 +1612,6 @@ Finished in 0.018199 seconds
 </div>
 
 </div>
-
 <div class="formal">
 
 <div class="example" id="fig..test-proto.unit-test">
@@ -1679,7 +1622,7 @@ Finished in 0.018199 seconds
 <pre>
 $ rake -f counter_xunit_runner.rake cver PROTOTYPE=1
 
-Ruby-VPI: prototype has been enabled for test "counter_xunit" 
+Ruby-VPI: prototype has been enabled for test &quot;counter_xunit&quot; 
 
 Loaded suite counter_xunit_bench
 Started
@@ -1692,9 +1635,7 @@ Finished in 0.040668 seconds.
 </div>
 
 </div>
-
-	<p>In these examples, the <code class="code"><span style="color:#036; font-weight:bold">PROTOTYPE</span></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="code"><span style="color:#036; font-weight:bold">PROTOTYPE</span></code> before running the test, by using your shell&#8217;s <strong>export</strong> or <strong>setenv</strong> command. Finally, the <a href="#setup.reqs"><span class="caps">GPL</span> Cver simulator</a>, denoted by <em>cver</em>, is used to run the simulation.</p>
-
+In these examples, the <code class="code"><span style="color:#036; font-weight:bold">PROTOTYPE</span></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="code"><span style="color:#036; font-weight:bold">PROTOTYPE</span></code> before running the test, by using your shell&#8217;s <strong>export</strong> or <strong>setenv</strong> command. Finally, the <a href="#setup.reqs"><span class="caps">GPL</span> Cver simulator</a>, denoted by <em>cver</em>, is used to run the simulation.
 
 <div class="admonition">
 
@@ -1706,7 +1647,7 @@ Finished in 0.040668 seconds.
 	<p class="title">Tip: What can the test runner do?</p>
 
 
-	<p>If you invoke the test runner (1) without any arguments or (2) with the <tt>-T</tt> option, it will show you a list of tasks that it can perform for you.</p>
+	<p>If you invoke the test runner (1) without any arguments or (2) with the <tt>--tasks</tt> option, it will show you a list of tasks that it can perform for you.</p>
 
 
 </div>
@@ -1751,7 +1692,6 @@ endmodule
 </div>
 
 </div>
-
 <div class="admonition">
 
 <div class="important" id="important4">
@@ -1800,7 +1740,6 @@ Finished in 0.005628 seconds
 </div>
 
 </div>
-
 <div class="formal">
 
 <div class="example" id="fig..test-design.unit-test">
@@ -1822,9 +1761,7 @@ Finished in 0.006766 seconds.
 </div>
 
 </div>
-
-	<p>In these examples, the <code class="code"><span style="color:#036; font-weight:bold">PROTOTYPE</span></code> environment variable is <em>not</em> 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="code"><span style="color:#036; font-weight:bold">PROTOTYPE</span></code>, or by using your shell&#8217;s <strong>unset</strong> command. Finally, the <a href="#setup.reqs"><span class="caps">GPL</span> Cver simulator</a>, denoted by <em>cver</em>, is used to run the simulation.</p>
-
+In these examples, the <code class="code"><span style="color:#036; font-weight:bold">PROTOTYPE</span></code> environment variable is <em>not</em> 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="code"><span style="color:#036; font-weight:bold">PROTOTYPE</span></code>, or by using your shell&#8217;s <strong>unset</strong> command. Finally, the <a href="#setup.reqs"><span class="caps">GPL</span> Cver simulator</a>, denoted by <em>cver</em>, is used to run the simulation.
 
 <div class="admonition">
 
@@ -1904,9 +1841,7 @@ Finished in 0.006766 seconds.
 </div>
 
 </div>
-
-	<p>If a &#8220;stack level too deep (SystemStackError)&#8221; error occurs during the simulation, then increase the system-resource limit for stack-size by running the <pre>ulimit -s unlimited</pre> command before starting the simulation.</p>
-
+If a &#8220;stack level too deep (SystemStackError)&#8221; error occurs during the simulation, then increase the system-resource limit for stack-size by running the <pre>ulimit -s unlimited</pre> command before starting the simulation.
 
 	<h3 id="problems.ruby.xUnit">test/unit</h3>
 
@@ -1927,9 +1862,7 @@ Finished in 0.006766 seconds.
 </div>
 
 </div>
-
-	<p>If your specification employs Ruby&#8217;s unit testing framework, then you will encounter an error saying &#8220;[BUG] cross-thread violation on rb_gc()&#8221;.</p>
-
+If your specification employs Ruby&#8217;s unit testing framework, then you will encounter an error saying &#8220;[BUG] cross-thread violation on rb_gc()&#8221;.
 
 	<h2 id="problem.ivl">Icarus Verilog</h2>
 
@@ -1995,7 +1928,6 @@ endmodule
 </div>
 
 </div>
-
 <div class="formal">
 
 <div class="example" id="ex..TestFoo_fix">
@@ -2048,9 +1980,7 @@ endmodule
 </div>
 
 </div>
-
-	<p>Version 6.1b of Mentor Modelsim doesn&#8217;t play nicely with either an embedded Ruby interpreter or <span class="caps">POSIX</span> threads in a <span class="caps">PLI</span> application. When Ruby-VPI invokes the ruby_run function (which starts the Ruby interpreter), the simulator terminates immediately with an exit status of 0.</p>
-
+Version 6.1b of Mentor Modelsim doesn&#8217;t play nicely with either an embedded Ruby interpreter or <span class="caps">POSIX</span> threads in a <span class="caps">PLI</span> application. When Ruby-VPI invokes the ruby_run function (which starts the Ruby interpreter), the simulator terminates immediately with an exit status of 0.
 
 	<h1 id="glossary">Glossary</h1>