ruby-vpi 20.0.0 → 21.0.0

data/doc/guide.erb

@@ -5,49 +5,33 @@
   # local variables for this document
   mailing_list_url  = 'http://rubyforge.org/mailman/listinfo/ruby-vpi-discuss'
   mailing_list_link = link(mailing_list_url, "project mailing list")
-  download_url      = 'http://rubyforge.org/frs/?group_id=1339'
-  source_repo_url   = File.join(RubyVPI::Project[:website], 'src')
-  feed_url          = File.join(RubyVPI::Project[:website], 'news.xml')
+
+  pkg_url = File.join(RubyVPI::Project[:website], 'pkg')
+  src_url = File.join(RubyVPI::Project[:website], 'src')
+  ann_url = File.join(RubyVPI::Project[:website], 'ann')
+  dev_url = File.join(RubyVPI::Project[:website], 'dev')
+  log_url = File.join(RubyVPI::Project[:website], 'log')
 
   # parameters for the HTML format
   $title   = "Ruby-VPI #{RubyVPI::Project[:version]} user guide"
-  $authors = { 'Suraj N. Kurapati' => 'http://snk.tuxfamily.org' }
-  $feeds   = { feed_url => :rss }
-
-  # parameters for Gerbil
-  $unindent = '  '
-
-  class String
-    def indent aDepthOrNode
-      amt =
-        if aDepthOrNode.is_a? Node
-          aDepthOrNode.depth + 1
-        else
-          aDepthOrNode
-        end
-
-      gsub(/^/, $unindent * amt).strip
-    end
-  end
+  $authors = { 'Suraj N. Kurapati' => 'http://snk.rubyforge.org' }
+  $feeds   = { ann_url => :rss }
 %>
 
 <% header_inside_below do %>
-  <div style="text-align: left; margin-top: 2em">
-
-  * "News feed":<%= feed_url %>
-    - project news and release announcements.
-  * "Download area":<%= download_url %>
-    - place to obtain release packages.
-  * "Mailing list":<%= mailing_list_url %>
-    - ask questions, get help, and discuss.
-  * "Reference":api/
-    - API documentation for source code.
-  * "Talks":http://ruby-vpi.rubyforge.org/talks/
-    - archive of presentations and seminars.
-  * "Papers":http://ruby-vpi.rubyforge.org/papers/
-    - archive of research and publications.
-
-  </div>
+  "Release notes and project news":<%= log_url %> &mdash; "Subscribe !images/feed-icon-28x28.png!":<%= ann_url %>
+
+  "Downloads":<%= pkg_url %> - obtain the newest release package.
+
+  "Talks":http://ruby-vpi.rubyforge.org/talks/ - archive of presentations and seminars.
+
+  "Papers":http://ruby-vpi.rubyforge.org/papers/ - archive of research and publications.
+
+  "Mailing list":<%= mailing_list_url %> - ask questions, get help, and discuss.
+
+  "Reference":api/index.html - API documentation for source code.
+
+  "Developer feed":<%= dev_url %> - news about repository commits.
 <% end %>
 
 <% chapter "Introduction" do %>
@@ -200,7 +184,7 @@
       |_. Simulator |_. Notes |
       | "Synopsys VCS":http://www.synopsys.com/products/simulation/simulation.html | Any version that supports the <tt>-load</tt> option is acceptable. |
       | "Mentor Modelsim":http://www.model.com | Any version that supports the <tt>-pli</tt> option is acceptable. |
-      | "Cadence NC-Sim":http://www.cadence.com/products/functional_ver/nc-verilog/ | Any version that supports the <tt>+loadvpi</tt> option is acceptable. |
+      | "Cadence NC-Sim":http://www.cadence.com/products/functional_ver/nc-verilog/ | Any version that supports the <tt>+loadvpi</tt> option is acceptable for Ruby-VPI versions 20.0.0 or older.  Version 21.0.0 of Ruby-VPI <%= xref "problem.ncsim", "does not work with Cadence NC-Sim" %>. |
       | "GPL Cver":http://www.pragmatic-c.com/gpl-cver/ | Version 2.11a or newer is acceptable. |
       | "Icarus Verilog":http://www.geda.seul.org/tools/icarus/index.html | Version 0.8 is _mostly_ acceptable because you *will not* be able to <%= xref "vpi.handles.relatives", "access child handles through method calls" %>. The reason for this limitation is explained in <%= xref 'problems.ivl.vpi_handle_by_name.absolute-paths' %>. |
     <% end %>
@@ -215,7 +199,6 @@
 
     <% paragraph "Libraries" do %>
       |_. Library |_. Notes |
-      | "POSIX threads (pthreads)":http://en.wikipedia.org/wiki/Pthreads | Header and linkable object files, and operating system support for this library are necessary. |
       | "RubyGems":http://rubyforge.org/frs/?group_id=126 | Any recent version should be acceptable. You can install RubyGems by following "these instructions":http://www.rubygems.org/read/chapter/3. |
     <% end %>
   <% end %>
@@ -245,8 +228,8 @@
       gem install ruby-vpi
       ruby-vpi -v
 
-    Otherwise, follow these instructions:
-    # Download the newest <tt>tar.gz</tt> release package from "the project download area":<%= download_url %>.
+    Alternatively, if you do not wish to use RubyGems:
+    # Download the newest <tt>tar.gz</tt> release package from "the project download area":<%= pkg_url %>.
     # Extract the release package anywhere you want on your system.
     # Go inside the extracted directory and run the following commands:
 
@@ -864,12 +847,12 @@
 
       Now that we have identified a set of expectations for our design, we are ready to implement them in our specification. This process is illustrated by <%= xref "fig:RSpec/counter_spec.rb" %> and <%= xref "fig:xUnit/counter_spec.rb" %>.
 
-      <% example "Specification implemented in RSpec format", "fig:RSpec/counter_spec.rb" do |n| %>
-        <code><%= File.read('examples/counter/RSpec/counter_spec.rb').indent(n) %></code>
+      <% example "Specification implemented in RSpec format", "fig:RSpec/counter_spec.rb" do %>
+        <code><%= File.read('examples/counter/RSpec/counter_spec.rb') %></code>
       <% end %>
 
-      <% example "Specification implemented in xUnit format", "fig:xUnit/counter_spec.rb" do |n| %>
-        <code><%= File.read('examples/counter/xUnit/counter_spec.rb').indent(n) %></code>
+      <% example "Specification implemented in xUnit format", "fig:xUnit/counter_spec.rb" do %>
+        <code><%= File.read('examples/counter/xUnit/counter_spec.rb') %></code>
       <% end %>
 
       Before we continue,
@@ -880,8 +863,8 @@
     <% section "Implement the prototype", "usage.tutorial.implement-proto" do %>
       Now that we have a specification against which to verify our design 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. The result of this proceess is illustrated by <%= xref "fig:counter_proto.rb" %>.
 
-      <% example "Ruby prototype of our Verilog design", "fig:counter_proto.rb" do |n| %>
-        <code><%= File.read('examples/counter/RSpec/counter_proto.rb').indent(n) %></code>
+      <% example "Ruby prototype of our Verilog design", "fig:counter_proto.rb" do %>
+        <code><%= File.read('examples/counter/RSpec/counter_proto.rb') %></code>
       <% end %>
 
       Before we continue, replace the contents of the files named <tt>RSpec/counter_proto.rb</tt> and <tt>xUnit/counter_proto.rb</tt> with the source code shown in <%= xref "fig:counter_proto.rb" %>.
@@ -930,8 +913,8 @@
     <% section "Implement the design", "usage.tutorial.implement-design" do %>
       Now that we have implemented and verified our prototype, we are ready to implement our design This is often quite simple because we translate _existing_ code from Ruby (our prototype) into Verilog (our design). The result of this process is illustrated by <%= xref "fig:counter.v_impl" %>.
 
-      <% example "Implementation of a simple up-counter with synchronous reset", "fig:counter.v_impl" do |n| %>
-        <code lang="verilog"><%= File.read('examples/counter/counter.v').indent(n) %></code>
+      <% example "Implementation of a simple up-counter with synchronous reset", "fig:counter.v_impl" do %>
+        <code lang="verilog"><%= File.read('examples/counter/counter.v') %></code>
       <% end %>
 
       Before we continue, replace the contents of the files named <tt>RSpec/counter.v</tt> and <tt>xUnit/counter.v</tt> with the source code shown in <%= xref "fig:counter.v_impl" %>
@@ -971,7 +954,7 @@
     <% end %>
 
     <% section "More examples", "usage.examples" do %>
-      The <tt>examples</tt> directory ("browse it online":<%= source_repo_url %>/examples/) contains several example tests which illustrate how Ruby-VPI can be used. Each example has an associated <tt>Rakefile</tt> which simplifies the process of running it. Therefore, simply navigate into an example directory and run the <pre>rake</pre> command to get started.
+      The <tt>examples</tt> directory ("browse it online":<%= src_url %>/examples/) contains several example tests which illustrate how Ruby-VPI can be used. Each example has an associated <tt>Rakefile</tt> which simplifies the process of running it. Therefore, simply navigate into an example directory and run the <pre>rake</pre> command to get started.
     <% end %>
   <% end %>
 <% end %>
@@ -1071,6 +1054,10 @@
       In version 0.8 of Icarus Verilog, the @vpi_control(vpiReset)@ VPI function causes an assertion to fail inside the simulator. As a result, the simulation terminates and a core dump is produced.
     <% end %>
   <% end %>
+
+  <% section "Cadence NC-Sim", "problem.ncsim" do %>
+    *ncsim* crashes with Ruby-VPI 21.0.0.  The problem is most likely an interaction issue with Ruby's threads implementation because *ncsim* worked fine with a "POSIX threads (pthreads)":http://en.wikipedia.org/wiki/Pthreads based implementation of Ruby-VPI (version 20.0.0).
+  <% end %>
 <% end %>
 
 <% chapter "Glossary", "glossary" do %>

data/doc/guide.html

@@ -2,11 +2,11 @@
 <html>
   <head>
     <meta http-equiv="content-type" content="text/html; charset=utf-8"/>
-    <meta name="date" content="27 January 2008"/>
+    <meta name="date" content="08 June 2008"/>
     <meta name="author" content="Suraj N. Kurapati"/>
-    <meta name="generator" content="Gerbil 1.1.0"/>
-    <link rel="alternate" type="application/rss+xml" href="http://ruby-vpi.rubyforge.org/news.xml"/>
-    <title>Ruby-VPI 20.0.0 user guide</title>
+    <meta name="generator" content="Gerbil 3.0.2"/>
+    <link rel="alternate" type="application/rss+xml" href="http://ruby-vpi.rubyforge.org/ann"/>
+    <title>Ruby-VPI 21.0.0 user guide</title>
 
     <style type="text/css" media="screen">
       body
@@ -25,6 +25,18 @@
     font-family      : Cambria, Georgia, serif;
   }
 
+/* lists */
+
+  #content li:first-child
+  {
+    margin-top       : 1em;
+  }
+
+  #content li
+  {
+    margin-bottom    : 1em;
+  }
+
 /* headings */
 
   h1,
@@ -105,7 +117,7 @@
     padding          : 1em;
     border           : 1px solid #C0C0C0;
     vertical-align   : top;
-    background-color : #FFFFFF;
+    background-color : inherit;
   }
 
   th
@@ -117,10 +129,35 @@
 
   #header
   {
-    margin-bottom    : 5em;
     text-align       : center;
   }
 
+  .header_outside_above,
+  #header,
+  .header_outside_below
+  {
+    margin-bottom    : 5em;
+  }
+
+  .footer_outside_above,
+  #footer,
+  .footer_outside_below
+  {
+    margin-top       : 5em;
+  }
+
+  #header .header_inside_above,
+  #footer .footer_inside_above
+  {
+    margin-bottom    : 4em;
+  }
+
+  #header .header_inside_below,
+  #footer .footer_inside_below
+  {
+    margin-top       : 4em;
+  }
+
   #abstract
   {
     margin-bottom    : 5em;
@@ -157,7 +194,6 @@
   {
     border-top       : thick dotted #DCDCDC;
     padding-top      : 1em;
-    margin-top       : 5em;
     text-align       : center;
   }
 
@@ -279,55 +315,21 @@
   max-width          : 36em;
 }
 
-/* hyperlinks */
-
-  a
-  {
-    color            : #0000FF;
-    text-decoration  : none;
-  }
-
-  a:visited
-  {
-    color            : #800080;
-  }
-
-  a:hover
-  {
-    color            : #FF0000;
-    text-decoration  : underline;
-  }
-
-  a:target
-  {
-    color            : #FF0000;
-    text-decoration  : underline;
-  }
-
-  a.toc:link,
-  a.toc:visited
-  {
-    text-decoration  : none;
-    z-index          : 1;
-  }
-
-  a img
-  {
-    border           : none;
-  }
+/* emphasis */
 
-  /*
-    mark external links with a symbol to help the user
-    distinguish between internal and external links
-  */
-  a:after
+  blockquote
   {
-    content: "∗";
+    margin           : 1em;
+    border           : 5px dotted #C0C0C0;
+    padding          : 1em;
+    color            : #444;
   }
 
-  a[href^="#"]:after
+  hr
   {
-    content: "";
+    height           : 0;
+    border           : 0;
+    border-top       : 2px solid #FF0000;
   }
 
 /* source code */
@@ -346,7 +348,7 @@
     background-color : #FFFAF0;
   }
 
-  /* output of syntax colorizer */
+  /* output of the syntax coloring library */
   .code
   {
     background-color : #FFFFF0;
@@ -354,12 +356,12 @@
 
   pre
   {
+    cursor           : text;
     line-height      : normal;
     border           : 1px dashed #C0C0C0;
     background-color : #F5FFDF;
     padding          : 1em;
     overflow         : auto;
-    cursor           : text;
   }
 
   /*
@@ -378,20 +380,42 @@
   }
   */
 
-/* emphasis */
+/* hyperlinks */
 
-  blockquote
+  a > img
   {
-    margin           : 1em;
-    border           : 5px dotted #C0C0C0;
-    padding          : 1em;
-    color            : #444;
+    border           : none;
   }
 
-  hr
+  a:link
+  {
+    color            : #0000FF;
+    text-decoration  : none;
+  }
+
+  a:visited
+  {
+    color            : #9400D3;
+    text-decoration  : none;
+  }
+
+  a:hover
   {
-    color            : #FF0000; /* for IE6 */
-    background-color : #FF0000; /* for Firefox */
+    color            : #FF0000;
+    text-decoration  : underline;
+  }
+
+  a:target
+  {
+    color            : #FF0000;
+    font-weight      : bold;
+  }
+
+  a.toc:link,
+  a.toc:visited
+  {
+    text-decoration  : none;
+    z-index          : 1;
   }
 
     </style>
@@ -412,6 +436,18 @@
     font-family      : Cambria, Georgia, serif;
   }
 
+/* lists */
+
+  #content li:first-child
+  {
+    margin-top       : 1em;
+  }
+
+  #content li
+  {
+    margin-bottom    : 1em;
+  }
+
 /* headings */
 
   h1,
@@ -492,7 +528,7 @@
     padding          : 1em;
     border           : 1px solid #C0C0C0;
     vertical-align   : top;
-    background-color : #FFFFFF;
+    background-color : inherit;
   }
 
   th
@@ -504,10 +540,35 @@
 
   #header
   {
-    margin-bottom    : 5em;
     text-align       : center;
   }
 
+  .header_outside_above,
+  #header,
+  .header_outside_below
+  {
+    margin-bottom    : 5em;
+  }
+
+  .footer_outside_above,
+  #footer,
+  .footer_outside_below
+  {
+    margin-top       : 5em;
+  }
+
+  #header .header_inside_above,
+  #footer .footer_inside_above
+  {
+    margin-bottom    : 4em;
+  }
+
+  #header .header_inside_below,
+  #footer .footer_inside_below
+  {
+    margin-top       : 4em;
+  }
+
   #abstract
   {
     margin-bottom    : 5em;
@@ -544,7 +605,6 @@
   {
     border-top       : thick dotted #DCDCDC;
     padding-top      : 1em;
-    margin-top       : 5em;
     text-align       : center;
   }
 
@@ -659,7 +719,24 @@
     _margin          : auto; /* for IE6 */
   }
 
-      /* headings */
+      /* source code */
+
+  tt
+  {
+    color            : inherit;
+    background-color : inherit;
+    font-weight      : normal;
+  }
+
+  pre,
+  .code
+  {
+    border           : none;
+    overflow         : visible;
+    background-color : inherit;
+  }
+
+/* headings */
 
   h1,
   h2,
@@ -684,8 +761,8 @@
 
   a:after
   {
-    content          : " (" attr(href) ")";
-    font-family      : sans-serif;
+    content          : " " attr(href);
+    font-family      : Consolas, "Lucida Console", monospace;
     font-weight      : normal;
     font-size        : 90%;
   }
@@ -713,23 +790,6 @@
     font-style       : normal;
   }
 
-/* source code */
-
-  tt
-  {
-    color            : inherit;
-    background-color : inherit;
-    font-weight      : normal;
-  }
-
-  pre,
-  .code
-  {
-    border           : none;
-    overflow         : visible;
-    background-color : inherit;
-  }
-
 /* document structure */
 
   #lof
@@ -758,42 +818,43 @@
     <div id="header">
     
       
-      <h1 class="title">Ruby-VPI 20.0.0 user guide</h1>
-      <h2 class="authors"><a href="http://snk.tuxfamily.org">Suraj N. Kurapati</a></h2>
-      <h3 class="date">27 January 2008</h3>
-    <div style="text-align: left; margin-top: 2em">
+      <h1 class="title">Ruby-VPI 21.0.0 user guide</h1>
+      <h2 class="authors"><a href="http://snk.rubyforge.org">Suraj N. Kurapati</a></h2>
+      <h3 class="date">08 June 2008</h3>
+    <div class="header_inside_below"><p><a href="http://ruby-vpi.rubyforge.org/log">Release notes and project news</a> &mdash; <a href="http://ruby-vpi.rubyforge.org/ann">Subscribe <img src="images/feed-icon-28x28.png" alt="" /></a></p>
 
-	<ul>
-	<li><a href="http://ruby-vpi.rubyforge.org/news.xml">News feed</a>
-  &#8211; project news and release announcements.</li>
-		<li><a href="http://rubyforge.org/frs/?group_id=1339">Download area</a>
-  &#8211; place to obtain release packages.</li>
-		<li><a href="http://rubyforge.org/mailman/listinfo/ruby-vpi-discuss">Mailing list</a>
-  &#8211; ask questions, get help, and discuss.</li>
-		<li><a href="api/">Reference</a>
-  &#8211; API documentation for source code.</li>
-		<li><a href="http://ruby-vpi.rubyforge.org/talks/">Talks</a>
-  &#8211; archive of presentations and seminars.</li>
-		<li><a href="http://ruby-vpi.rubyforge.org/papers/">Papers</a>
-  &#8211; archive of research and publications.</li>
-	</ul>
 
+	<p><a href="http://ruby-vpi.rubyforge.org/pkg">Downloads</a> &#8211; obtain the newest release package.</p>
 
-</div>
+
+	<p><a href="http://ruby-vpi.rubyforge.org/talks/">Talks</a> &#8211; archive of presentations and seminars.</p>
+
+
+	<p><a href="http://ruby-vpi.rubyforge.org/papers/">Papers</a> &#8211; archive of research and publications.</p>
+
+
+	<p><a href="http://rubyforge.org/mailman/listinfo/ruby-vpi-discuss">Mailing list</a> &#8211; ask questions, get help, and discuss.</p>
+
+
+	<p><a href="api/index.html">Reference</a> &#8211; API documentation for source code.</p>
+
+
+	<p><a href="http://ruby-vpi.rubyforge.org/dev">Developer feed</a> &#8211; news about repository commits.</p></div>
     </div>
     
 
+    
 
-    <div id="toc"><h1>Contents</h1> <ul><li>1&nbsp;&nbsp;<a id="a-606704428" href="#Introduction">Introduction</a><ul><li>1.1&nbsp;&nbsp;<a id="a-606710768" href="#Features">Features</a></li><li>1.2&nbsp;&nbsp;<a id="a-606745598" href="#License">License</a></li><li>1.3&nbsp;&nbsp;<a id="a-606752538" href="#Appetizers">Appetizers</a></li><li>1.4&nbsp;&nbsp;<a id="a-606764318" href="#Applications">Applications</a></li><li>1.5&nbsp;&nbsp;<a id="a-606770018" href="#Related-works">Related works</a></li></ul></li><li>2&nbsp;&nbsp;<a id="a-606777838" href="#setup">Setup</a><ul><li>2.1&nbsp;&nbsp;<a id="a-606779348" href="#setup.reqs">Requirements</a></li><li>2.2&nbsp;&nbsp;<a id="a-606789068" href="#setup.recom">Recommendations</a></li><li>2.3&nbsp;&nbsp;<a id="a-606794098" href="#setup.inst">Installation</a><ul><li>2.3.1&nbsp;&nbsp;<a id="a-606799148" href="#setup.inst.windows">Installing on Windows</a></li></ul></li><li>2.4&nbsp;&nbsp;<a id="a-606801708" href="#setup.maintenance">Maintenance</a></li><li>2.5&nbsp;&nbsp;<a id="a-606803858" href="#setup.manifest">Manifest</a></li></ul></li><li>3&nbsp;&nbsp;<a id="a-606810448" href="#organization">Background</a><ul><li>3.1&nbsp;&nbsp;<a id="a-606815068" href="#Motivation">Motivation</a></li><li>3.2&nbsp;&nbsp;<a id="a-606817088" href="#organization.tests">Tests</a></li></ul></li><li>4&nbsp;&nbsp;<a id="a-606822688" href="#usage">Usage</a><ul><li>4.1&nbsp;&nbsp;<a id="a-606824258" href="#usage.theory">Theory of operation</a><ul><li>4.1.1&nbsp;&nbsp;<a id="a-606835008" href="#Test-files">Test files</a></li></ul></li><li>4.2&nbsp;&nbsp;<a id="a-606840438" href="#overview.relay">Interacting with the Verilog simulator</a></li><li>4.3&nbsp;&nbsp;<a id="a-606846998" href="#vpi">VPI in Ruby</a><ul><li>4.3.1&nbsp;&nbsp;<a id="a-606850438" href="#vpi.handles">Handles</a><ul><li>4.3.1.1&nbsp;&nbsp;<a id="a-606856398" href="#vpi.handles.relatives">Accessing a handle&#8217;s relatives</a></li><li>4.3.1.2&nbsp;&nbsp;<a id="a-606858628" href="#Accessing-a-handle-s-properties">Accessing a handle&#8217;s properties</a></li></ul></li><li>4.3.2&nbsp;&nbsp;<a id="a-606870058" href="#vpi.callbacks">Callbacks</a></li></ul></li><li>4.4&nbsp;&nbsp;<a id="a-606880188" href="#usage.concurrency">Concurrency</a><ul><li>4.4.1&nbsp;&nbsp;<a id="a-606883708" href="#Creating-a-concurrent-process">Creating a concurrent process</a></li></ul></li><li>4.5&nbsp;&nbsp;<a id="a-606890138" href="#usage.prototyping">Prototyping</a><ul><li>4.5.1&nbsp;&nbsp;<a id="a-606894508" href="#Creating-a-prototype">Creating a prototype</a></li></ul></li><li>4.6&nbsp;&nbsp;<a id="a-606905198" href="#usage.debugger">Interactive debugging</a><ul><li>4.6.1&nbsp;&nbsp;<a id="a-606908278" href="#usage.debugger.init">Advanced initialization</a></li></ul></li><li>4.7&nbsp;&nbsp;<a id="a-606910748" href="#usage.runner">Test runner</a><ul><li>4.7.1&nbsp;&nbsp;<a id="a-606913938" href="#usage.runner.env-vars">Environment variables</a><ul><li>4.7.1.1&nbsp;&nbsp;<a id="a-606917008" href="#Variables-as-command-line-arguments">Variables as command-line arguments</a></li></ul></li></ul></li><li>4.8&nbsp;&nbsp;<a id="a-606921818" href="#usage.tools">Tools</a><ul><li>4.8.1&nbsp;&nbsp;<a id="a-606923678" href="#usage.tools.generate">Automated test generation</a></li><li>4.8.2&nbsp;&nbsp;<a id="a-606932168" href="#usage.tools.convert">Verilog to Ruby conversion</a></li></ul></li><li>4.9&nbsp;&nbsp;<a id="a-606934638" href="#usage.tutorial">Tutorial</a><ul><li>4.9.1&nbsp;&nbsp;<a id="a-606947158" href="#usage.tutorial.declare-design">Start with a Verilog design</a></li><li>4.9.2&nbsp;&nbsp;<a id="a-606953958" href="#usage.tutorial.generate-test">Generate a test</a></li><li>4.9.3&nbsp;&nbsp;<a id="a-606966828" href="#usage.tutorial.specification">Specify your expectations</a></li><li>4.9.4&nbsp;&nbsp;<a id="a-606069158" href="#usage.tutorial.implement-proto">Implement the prototype</a></li><li>4.9.5&nbsp;&nbsp;<a id="a-606122988" href="#usage.tutorial.test-proto">Verify the prototype</a></li><li>4.9.6&nbsp;&nbsp;<a id="a-606168938" href="#usage.tutorial.implement-design">Implement the design</a></li><li>4.9.7&nbsp;&nbsp;<a id="a-606269558" href="#usage.tutorial.test-design">Verify the design</a></li><li>4.9.8&nbsp;&nbsp;<a id="a-606358268" href="#usage.examples">More examples</a></li></ul></li></ul></li><li>5&nbsp;&nbsp;<a id="a-606376468" href="#hacking">Hacking</a><ul><li>5.1&nbsp;&nbsp;<a id="a-605850148" href="#hacking.build">Building from source code</a></li><li>5.2&nbsp;&nbsp;<a id="a-605974548" href="#Installing-without-really-installing">Installing without really installing</a></li><li>5.3&nbsp;&nbsp;<a id="a-605757818" href="#hacking.release-packages">Building release packages</a></li><li>5.4&nbsp;&nbsp;<a id="a-607050138" href="#hacking.guide">Editing this guide</a></li></ul></li><li>6&nbsp;&nbsp;<a id="a-607052618" href="#problems">Known problems</a><ul><li>6.1&nbsp;&nbsp;<a id="a-607054268" href="#problem.ivl">Icarus Verilog</a><ul><li>6.1.1&nbsp;&nbsp;<a id="a-607055848" href="#problems.ivl.vpi_handle_by_name.absolute-paths">Give full paths to Verilog objects</a></li><li>6.1.2&nbsp;&nbsp;<a id="a-607061068" href="#problems.ivl.vpi_handle_by_name.connect-registers">Registers must be connected</a></li><li>6.1.3&nbsp;&nbsp;<a id="a-607070908" href="#problems.ivl.vpi_reset">VPI::reset</a></li></ul></li></ul></li><li>7&nbsp;&nbsp;<a id="a-607073798" href="#glossary">Glossary</a><ul><li>7.1&nbsp;&nbsp;<a id="a-607075458" href="#glossary.test">Test</a></li><li>7.2&nbsp;&nbsp;<a id="a-607080108" href="#glossary.design">Design</a></li><li>7.3&nbsp;&nbsp;<a id="a-607083458" href="#glossary.specification">Specification</a></li><li>7.4&nbsp;&nbsp;<a id="a-607088168" href="#glossary.expectation">Expectation</a></li><li>7.5&nbsp;&nbsp;<a id="a-607090238" href="#glossary.handle">Handle</a></li><li>7.6&nbsp;&nbsp;<a id="a-607093668" href="#glossary.rake">Rake</a></li><li>7.7&nbsp;&nbsp;<a id="a-607095818" href="#glossary.RSpec">RSpec</a></li><li>7.8&nbsp;&nbsp;<a id="a-607099338" href="#glossary.TDD">Test driven development</a></li><li>7.9&nbsp;&nbsp;<a id="a-607101548" href="#glossary.BDD">Behavior driven development</a></li></ul></li></ul></div>
+    <div id="toc"><h1>Contents</h1> <ul><li>1&nbsp;&nbsp;<a id="a-606855468" href="#Introduction">Introduction</a><ul><li>1.1&nbsp;&nbsp;<a id="a-606864618" href="#Features">Features</a></li><li>1.2&nbsp;&nbsp;<a id="a-606881728" href="#License">License</a></li><li>1.3&nbsp;&nbsp;<a id="a-606884178" href="#Appetizers">Appetizers</a></li><li>1.4&nbsp;&nbsp;<a id="a-606888428" href="#Applications">Applications</a></li><li>1.5&nbsp;&nbsp;<a id="a-606890808" href="#Related-works">Related works</a></li></ul></li><li>2&nbsp;&nbsp;<a id="a-606895198" href="#setup">Setup</a><ul><li>2.1&nbsp;&nbsp;<a id="a-606896768" href="#setup.reqs">Requirements</a></li><li>2.2&nbsp;&nbsp;<a id="a-606908788" href="#setup.recom">Recommendations</a></li><li>2.3&nbsp;&nbsp;<a id="a-606914178" href="#setup.inst">Installation</a><ul><li>2.3.1&nbsp;&nbsp;<a id="a-606919398" href="#setup.inst.windows">Installing on Windows</a></li></ul></li><li>2.4&nbsp;&nbsp;<a id="a-606921958" href="#setup.maintenance">Maintenance</a></li><li>2.5&nbsp;&nbsp;<a id="a-606924108" href="#setup.manifest">Manifest</a></li></ul></li><li>3&nbsp;&nbsp;<a id="a-606931208" href="#organization">Background</a><ul><li>3.1&nbsp;&nbsp;<a id="a-606935998" href="#Motivation">Motivation</a></li><li>3.2&nbsp;&nbsp;<a id="a-606938018" href="#organization.tests">Tests</a></li></ul></li><li>4&nbsp;&nbsp;<a id="a-606943788" href="#usage">Usage</a><ul><li>4.1&nbsp;&nbsp;<a id="a-606945358" href="#usage.theory">Theory of operation</a><ul><li>4.1.1&nbsp;&nbsp;<a id="a-606956448" href="#Test-files">Test files</a></li></ul></li><li>4.2&nbsp;&nbsp;<a id="a-606962218" href="#overview.relay">Interacting with the Verilog simulator</a></li><li>4.3&nbsp;&nbsp;<a id="a-606969118" href="#vpi">VPI in Ruby</a><ul><li>4.3.1&nbsp;&nbsp;<a id="a-606972558" href="#vpi.handles">Handles</a><ul><li>4.3.1.1&nbsp;&nbsp;<a id="a-606978858" href="#vpi.handles.relatives">Accessing a handle&#8217;s relatives</a></li><li>4.3.1.2&nbsp;&nbsp;<a id="a-606981088" href="#Accessing-a-handle-s-properties">Accessing a handle&#8217;s properties</a></li></ul></li><li>4.3.2&nbsp;&nbsp;<a id="a-606992858" href="#vpi.callbacks">Callbacks</a></li></ul></li><li>4.4&nbsp;&nbsp;<a id="a-607003668" href="#usage.concurrency">Concurrency</a><ul><li>4.4.1&nbsp;&nbsp;<a id="a-607007188" href="#Creating-a-concurrent-process">Creating a concurrent process</a></li></ul></li><li>4.5&nbsp;&nbsp;<a id="a-607013618" href="#usage.prototyping">Prototyping</a><ul><li>4.5.1&nbsp;&nbsp;<a id="a-607018328" href="#Creating-a-prototype">Creating a prototype</a></li></ul></li><li>4.6&nbsp;&nbsp;<a id="a-607030038" href="#usage.debugger">Interactive debugging</a><ul><li>4.6.1&nbsp;&nbsp;<a id="a-607033288" href="#usage.debugger.init">Advanced initialization</a></li></ul></li><li>4.7&nbsp;&nbsp;<a id="a-607035758" href="#usage.runner">Test runner</a><ul><li>4.7.1&nbsp;&nbsp;<a id="a-607039108" href="#usage.runner.env-vars">Environment variables</a><ul><li>4.7.1.1&nbsp;&nbsp;<a id="a-607042348" href="#Variables-as-command-line-arguments">Variables as command-line arguments</a></li></ul></li></ul></li><li>4.8&nbsp;&nbsp;<a id="a-607047158" href="#usage.tools">Tools</a><ul><li>4.8.1&nbsp;&nbsp;<a id="a-607049018" href="#usage.tools.generate">Automated test generation</a></li><li>4.8.2&nbsp;&nbsp;<a id="a-607057848" href="#usage.tools.convert">Verilog to Ruby conversion</a></li></ul></li><li>4.9&nbsp;&nbsp;<a id="a-607060318" href="#usage.tutorial">Tutorial</a><ul><li>4.9.1&nbsp;&nbsp;<a id="a-607074198" href="#usage.tutorial.declare-design">Start with a Verilog design</a></li><li>4.9.2&nbsp;&nbsp;<a id="a-607081338" href="#usage.tutorial.generate-test">Generate a test</a></li><li>4.9.3&nbsp;&nbsp;<a id="a-607095058" href="#usage.tutorial.specification">Specify your expectations</a></li><li>4.9.4&nbsp;&nbsp;<a id="a-607108658" href="#usage.tutorial.implement-proto">Implement the prototype</a></li><li>4.9.5&nbsp;&nbsp;<a id="a-607115808" href="#usage.tutorial.test-proto">Verify the prototype</a></li><li>4.9.6&nbsp;&nbsp;<a id="a-606264088" href="#usage.tutorial.implement-design">Implement the design</a></li><li>4.9.7&nbsp;&nbsp;<a id="a-606356058" href="#usage.tutorial.test-design">Verify the design</a></li><li>4.9.8&nbsp;&nbsp;<a id="a-606447908" href="#usage.examples">More examples</a></li></ul></li></ul></li><li>5&nbsp;&nbsp;<a id="a-606474498" href="#hacking">Hacking</a><ul><li>5.1&nbsp;&nbsp;<a id="a-606497178" href="#hacking.build">Building from source code</a></li><li>5.2&nbsp;&nbsp;<a id="a-606511708" href="#Installing-without-really-installing">Installing without really installing</a></li><li>5.3&nbsp;&nbsp;<a id="a-606005938" href="#hacking.release-packages">Building release packages</a></li><li>5.4&nbsp;&nbsp;<a id="a-606145488" href="#hacking.guide">Editing this guide</a></li></ul></li><li>6&nbsp;&nbsp;<a id="a-605970068" href="#problems">Known problems</a><ul><li>6.1&nbsp;&nbsp;<a id="a-607199668" href="#problem.ivl">Icarus Verilog</a><ul><li>6.1.1&nbsp;&nbsp;<a id="a-607201248" href="#problems.ivl.vpi_handle_by_name.absolute-paths">Give full paths to Verilog objects</a></li><li>6.1.2&nbsp;&nbsp;<a id="a-607206638" href="#problems.ivl.vpi_handle_by_name.connect-registers">Registers must be connected</a></li><li>6.1.3&nbsp;&nbsp;<a id="a-607216988" href="#problems.ivl.vpi_reset">VPI::reset</a></li></ul></li><li>6.2&nbsp;&nbsp;<a id="a-607219468" href="#problem.ncsim">Cadence NC-Sim</a></li></ul></li><li>7&nbsp;&nbsp;<a id="a-607221888" href="#glossary">Glossary</a><ul><li>7.1&nbsp;&nbsp;<a id="a-607223548" href="#glossary.test">Test</a></li><li>7.2&nbsp;&nbsp;<a id="a-607228538" href="#glossary.design">Design</a></li><li>7.3&nbsp;&nbsp;<a id="a-607232058" href="#glossary.specification">Specification</a></li><li>7.4&nbsp;&nbsp;<a id="a-607237108" href="#glossary.expectation">Expectation</a></li><li>7.5&nbsp;&nbsp;<a id="a-607239178" href="#glossary.handle">Handle</a></li><li>7.6&nbsp;&nbsp;<a id="a-607242778" href="#glossary.rake">Rake</a></li><li>7.7&nbsp;&nbsp;<a id="a-607244928" href="#glossary.RSpec">RSpec</a></li><li>7.8&nbsp;&nbsp;<a id="a-607248618" href="#glossary.TDD">Test driven development</a></li><li>7.9&nbsp;&nbsp;<a id="a-607250828" href="#glossary.BDD">Behavior driven development</a></li></ul></li></ul></div>
 
-    <div id="lof"><h1>Cautions</h1> <ol><li><a id="a-606881928" href="#Assignments-inside-processes-are-non-blocking">Assignments inside processes are non-blocking</a></li><li><a id="a-606928078" href="#Do-not-rename-generated-files">Do not rename generated files</a></li></ol><h1>Examples</h1> <ol><li><a id="a-606871738" href="#ex:callback">Using a callback for value change notification</a></li><li><a id="a-606885348" href="#An-edge-triggered-always-block">An edge-triggered &#8220;always&#8221; block</a></li><li><a id="a-606887298" href="#A-change-triggered-combinational-always-block">A change-triggered (combinational) &#8220;always&#8221; block</a></li><li><a id="a-606919158" href="#Running-a-test-with-environment-variables">Running a test with environment variables</a></li><li><a id="a-606950328" href="#fig:counter.v_decl">Declaration of a simple up-counter with synchronous reset</a></li><li><a id="a-606962678" href="#fig:generate-test.RSpec">Generating a test with specification in RSpec format</a></li><li><a id="a-606964548" href="#fig:generate-test.xUnit">Generating a test with specification in xUnit format</a></li><li><a id="a-606972788" href="#fig:RSpec-counter_spec.rb">Specification implemented in RSpec format</a></li><li><a id="a-606975088" href="#fig:xUnit-counter_spec.rb">Specification implemented in xUnit format</a></li><li><a id="a-606100048" href="#fig:counter_proto.rb">Ruby prototype of our Verilog design</a></li><li><a id="a-606139338" href="#fig:test-proto.RSpec">Running a test with specification in RSpec format</a></li><li><a id="a-606145238" href="#fig:test-proto.unit-test">Running a test with specification in xUnit format</a></li><li><a id="a-606237758" href="#fig:counter.v_impl">Implementation of a simple up-counter with synchronous reset</a></li><li><a id="a-606307738" href="#fig:test-design.RSpec">Running a test with specification in RSpec format</a></li><li><a id="a-606325118" href="#fig:test-design.unit-test">Running a test with specification in xUnit format</a></li><li><a id="a-607058828" href="#ex:TestFoo">Part of a bench which instantiates a Verilog design</a></li><li><a id="a-607066798" href="#ex:TestFoo_bad">Bad design with unconnected registers</a></li><li><a id="a-607068638" href="#ex:TestFoo_fix">Fixed design with wired registers</a></li></ol><h1>Figures</h1> <ol><li><a id="a-606812008" href="#fig:organization.detail">Where does Ruby-VPI fit in?</a></li><li><a id="a-606820058" href="#fig:organization">Organization of a test in Ruby-VPI</a></li><li><a id="a-606843408" href="#fig:ruby_relay">Interaction between Ruby and Verilog</a></li><li><a id="a-606862348" href="#fig:method-naming-format">Method naming format for accessing a handle&#8217;s properties</a></li></ol><h1>Notes</h1> <ol><li><a id="a-606848628" href="#Constants-are-capitalized-in-Ruby">Constants are capitalized in Ruby</a></li></ol><h1>Tables</h1> <ol><li><a id="a-606865648" href="#tbl:accessors">Possible accessors and their implications</a></li><li><a id="a-606867538" href="#ex:properties">Examples of accessing a handle&#8217;s properties</a></li></ol><h1>Tips</h1> <ol><li><a id="a-606795708" href="#Tuning-for-maximum-performance">Tuning for maximum performance</a></li><li><a id="a-606929888" href="#Using-kdiff3-with-the-automated-test-generator.">Using <strong>kdiff3</strong> with the automated test generator.</a></li><li><a id="a-606150528" href="#What-can-the-test-runner-do">What can the test runner do?</a></li></ol></div>
+    <div id="lof"><h1>Cautions</h1> <ol><li><a id="a-607005408" href="#Assignments-inside-processes-are-non-blocking">Assignments inside processes are non-blocking</a></li><li><a id="a-607053758" href="#Do-not-rename-generated-files">Do not rename generated files</a></li></ol><h1>Examples</h1> <ol><li><a id="a-606994538" href="#ex:callback">Using a callback for value change notification</a></li><li><a id="a-607008828" href="#An-edge-triggered-always-block">An edge-triggered &#8220;always&#8221; block</a></li><li><a id="a-607010778" href="#A-change-triggered-combinational-always-block">A change-triggered (combinational) &#8220;always&#8221; block</a></li><li><a id="a-607044498" href="#Running-a-test-with-environment-variables">Running a test with environment variables</a></li><li><a id="a-607077538" href="#fig:counter.v_decl">Declaration of a simple up-counter with synchronous reset</a></li><li><a id="a-607090908" href="#fig:generate-test.RSpec">Generating a test with specification in RSpec format</a></li><li><a id="a-607092778" href="#fig:generate-test.xUnit">Generating a test with specification in xUnit format</a></li><li><a id="a-607101528" href="#fig:RSpec-counter_spec.rb">Specification implemented in RSpec format</a></li><li><a id="a-607103348" href="#fig:xUnit-counter_spec.rb">Specification implemented in xUnit format</a></li><li><a id="a-607112038" href="#fig:counter_proto.rb">Ruby prototype of our Verilog design</a></li><li><a id="a-606210758" href="#fig:test-proto.RSpec">Running a test with specification in RSpec format</a></li><li><a id="a-606234128" href="#fig:test-proto.unit-test">Running a test with specification in xUnit format</a></li><li><a id="a-606295138" href="#fig:counter.v_impl">Implementation of a simple up-counter with synchronous reset</a></li><li><a id="a-606419298" href="#fig:test-design.RSpec">Running a test with specification in RSpec format</a></li><li><a id="a-606425048" href="#fig:test-design.unit-test">Running a test with specification in xUnit format</a></li><li><a id="a-607204398" href="#ex:TestFoo">Part of a bench which instantiates a Verilog design</a></li><li><a id="a-607212878" href="#ex:TestFoo_bad">Bad design with unconnected registers</a></li><li><a id="a-607214718" href="#ex:TestFoo_fix">Fixed design with wired registers</a></li></ol><h1>Figures</h1> <ol><li><a id="a-606932768" href="#fig:organization.detail">Where does Ruby-VPI fit in?</a></li><li><a id="a-606941158" href="#fig:organization">Organization of a test in Ruby-VPI</a></li><li><a id="a-606965358" href="#fig:ruby_relay">Interaction between Ruby and Verilog</a></li><li><a id="a-606984978" href="#fig:method-naming-format">Method naming format for accessing a handle&#8217;s properties</a></li></ol><h1>Notes</h1> <ol><li><a id="a-606970748" href="#Constants-are-capitalized-in-Ruby">Constants are capitalized in Ruby</a></li></ol><h1>Tables</h1> <ol><li><a id="a-606988448" href="#tbl:accessors">Possible accessors and their implications</a></li><li><a id="a-606990338" href="#ex:properties">Examples of accessing a handle&#8217;s properties</a></li></ol><h1>Tips</h1> <ol><li><a id="a-606915788" href="#Tuning-for-maximum-performance">Tuning for maximum performance</a></li><li><a id="a-607055568" href="#Using-kdiff3-with-the-automated-test-generator.">Using <strong>kdiff3</strong> with the automated test generator.</a></li><li><a id="a-606244898" href="#What-can-the-test-runner-do">What can the test runner do?</a></li></ol></div>
 
     <div id="content">
 
 <div class="chapter">
   <h1 class="title">
     Chapter
-    <a class="toc" id="Introduction" href="#a-606704428">1</a>
+    <a class="toc" id="Introduction" href="#a-606855468">1</a>
 
     <br/>
 
@@ -813,17 +874,17 @@
 
 	<p><div class="section">
   <h2 class="title">
-    <a class="toc" id="Features" href="#a-606710768">1.1</a>&nbsp;&nbsp;Features
+    <a class="toc" id="Features" href="#a-606864618">1.1</a>&nbsp;&nbsp;Features
   </h2>
   <div class="content"><div class="paragraph">
-  <p class="title">Portable</p>
+  <p class="title" id="Portable">Portable</p>
   <div class="content"><ul>
 	<li>Works on Windows, Mac OSX, GNU/Linux, and UNIX.</li>
 		<li>Supports all <a class="xref" href="#setup.reqs.sim">major Verilog simulators</a> available today.</li>
 	</ul></div>
 </div>
 <div class="paragraph">
-  <p class="title">Agile</p>
+  <p class="title" id="Agile">Agile</p>
   <div class="content"><ul>
 	<li>Enables <a href="http://agilemanifesto.org">agile practices</a> such as
 	<ul>
@@ -844,7 +905,7 @@
 	</ul></div>
 </div>
 <div class="paragraph">
-  <p class="title">Powerful</p>
+  <p class="title" id="Powerful">Powerful</p>
   <div class="content"><p style="float:right"><img src="images/ruby/logo-reflection.png" title="the Ruby logo" alt="the Ruby logo" /></p>
 
 
@@ -871,7 +932,7 @@
 </div>
 <div class="section">
   <h2 class="title">
-    <a class="toc" id="License" href="#a-606745598">1.2</a>&nbsp;&nbsp;License
+    <a class="toc" id="License" href="#a-606881728">1.2</a>&nbsp;&nbsp;License
   </h2>
   <div class="content"><p>Copyright 2006 Suraj N. Kurapati &lt;SNK at GNA dot ORG&gt;<br/>
 Copyright 1999 Kazuhiro HIWADA &lt;HIWADA at KUEE dot KYOTO-U dot AC dot JP&gt;<br/></p>
@@ -887,15 +948,15 @@ Software is furnished to do so, subject to the following conditions:</p>
 
 	<ul>
 	<li>All copies and substantial portions of the Software (the &quot;Derivatives&quot;)
-and their corresponding machine-readable source code (the &quot;Code&quot;) must
-include the above copyright notice and this permission notice.</li>
+  and their corresponding machine-readable source code (the &quot;Code&quot;) must
+  include the above copyright notice and this permission notice.</li>
 	</ul>
 
 
 	<ul>
-	<li>Upon distribution, the Derivatives must be accompanied either by the Code
-or&mdash;provided that the Code is obtainable for no more than the cost of
-distribution plus a nominal fee&mdash;by information on how to obtain the Code.</li>
+	<li>Upon distribution, the Derivatives must be accompanied by either the Code
+  or&mdash;provided that the Code is obtainable for no more than the cost of
+  distribution plus a nominal fee&mdash;information on how to obtain the Code.</li>
 	</ul>
 
 
@@ -908,7 +969,7 @@ IMPLIED, INCLUDING <span class="caps">BUT NOT LIMITED TO THE WARRANTIES OF MERCH
 </div>
 <div class="section">
   <h2 class="title">
-    <a class="toc" id="Appetizers" href="#a-606752538">1.3</a>&nbsp;&nbsp;Appetizers
+    <a class="toc" id="Appetizers" href="#a-606884178">1.3</a>&nbsp;&nbsp;Appetizers
   </h2>
   <div class="content">Here is a tiny sampling of code to whet your appetite. See <a class="xref" href="#usage.tutorial">the tutorial</a> for more samples.
 
@@ -978,7 +1039,7 @@ your_memory.each_memoryWord { |w| w.put_value <span style="color:#00D; font-weig
 </div>
 <div class="section">
   <h2 class="title">
-    <a class="toc" id="Applications" href="#a-606764318">1.4</a>&nbsp;&nbsp;Applications
+    <a class="toc" id="Applications" href="#a-606888428">1.4</a>&nbsp;&nbsp;Applications
   </h2>
   <div class="content">Examples of tasks that can be performed with Ruby-VPI are:
 
@@ -1012,7 +1073,7 @@ your_memory.each_memoryWord { |w| w.put_value <span style="color:#00D; font-weig
 </div>
 <div class="section">
   <h2 class="title">
-    <a class="toc" id="Related-works" href="#a-606770018">1.5</a>&nbsp;&nbsp;Related works
+    <a class="toc" id="Related-works" href="#a-606890808">1.5</a>&nbsp;&nbsp;Related works
   </h2>
   <div class="content"><ul>
 	<li><a href="http://anvil.sourceforge.net">ANVIL</a> is a C++ interface to VPI.</li>
@@ -1025,7 +1086,7 @@ your_memory.each_memoryWord { |w| w.put_value <span style="color:#00D; font-weig
 
 
 	<p><div class="paragraph">
-  <p class="title">Ye olde PLI</p>
+  <p class="title" id="Ye-olde-PLI">Ye olde PLI</p>
   <div class="content">The following projects utilize the archaic <strong>tf</strong> and <strong>acc</strong> PLI interfaces, which have been officially deprecated in IEEE Std 1364-2005.
 
 
@@ -1039,7 +1100,7 @@ your_memory.each_memoryWord { |w| w.put_value <span style="color:#00D; font-weig
 <div class="chapter">
   <h1 class="title">
     Chapter
-    <a class="toc" id="setup" href="#a-606777838">2</a>
+    <a class="toc" id="setup" href="#a-606895198">2</a>
 
     <br/>
 
@@ -1048,13 +1109,13 @@ your_memory.each_memoryWord { |w| w.put_value <span style="color:#00D; font-weig
 
   <div class="content"><div class="section">
   <h2 class="title">
-    <a class="toc" id="setup.reqs" href="#a-606779348">2.1</a>&nbsp;&nbsp;Requirements
+    <a class="toc" id="setup.reqs" href="#a-606896768">2.1</a>&nbsp;&nbsp;Requirements
   </h2>
   <div class="content"><p>Your system needs the following software to run Ruby-VPI.</p>
 
 
 	<p><div class="paragraph">
-  <p class="title">Verilog simulator</p>
+  <p class="title" id="setup.reqs.sim">Verilog simulator</p>
   <div class="content">Ruby-VPI is known to work with the following simulators. However, you should be able to use it with any Verilog simulator that supports VPI.
 
 
@@ -1073,7 +1134,7 @@ your_memory.each_memoryWord { |w| w.put_value <span style="color:#00D; font-weig
 		</tr>
 		<tr>
 			<td> <a href="http://www.cadence.com/products/functional_ver/nc-verilog/">Cadence NC-Sim</a> </td>
-			<td> Any version that supports the <tt>+loadvpi</tt> option is acceptable. </td>
+			<td> Any version that supports the <tt>+loadvpi</tt> option is acceptable for Ruby-VPI versions 20.0.0 or older.  Version 21.0.0 of Ruby-VPI <a class="xref" href="#problem.ncsim">does not work with Cadence NC-Sim</a>. </td>
 		</tr>
 		<tr>
 			<td> <a href="http://www.pragmatic-c.com/gpl-cver/">GPL Cver</a> </td>
@@ -1086,7 +1147,7 @@ your_memory.each_memoryWord { |w| w.put_value <span style="color:#00D; font-weig
 	</table></div>
 </div>
 <div class="paragraph">
-  <p class="title">Compilers</p>
+  <p class="title" id="Compilers">Compilers</p>
   <div class="content"><table border="1">
 		<tr>
 			<th>Software </th>
@@ -1111,16 +1172,12 @@ your_memory.each_memoryWord { |w| w.put_value <span style="color:#00D; font-weig
 	</table></div>
 </div>
 <div class="paragraph">
-  <p class="title">Libraries</p>
+  <p class="title" id="Libraries">Libraries</p>
   <div class="content"><table border="1">
 		<tr>
 			<th>Library </th>
 			<th>Notes </th>
 		</tr>
-		<tr>
-			<td> <a href="http://en.wikipedia.org/wiki/Pthreads" title="pthreads">POSIX threads</a> </td>
-			<td> Header and linkable object files, and operating system support for this library are necessary. </td>
-		</tr>
 		<tr>
 			<td> <a href="http://rubyforge.org/frs/?group_id=126">RubyGems</a> </td>
 			<td> Any recent version should be acceptable. You can install RubyGems by following <a href="http://www.rubygems.org/read/chapter/3">these instructions</a>. </td>
@@ -1130,13 +1187,13 @@ your_memory.each_memoryWord { |w| w.put_value <span style="color:#00D; font-weig
 </div>
 <div class="section">
   <h2 class="title">
-    <a class="toc" id="setup.recom" href="#a-606789068">2.2</a>&nbsp;&nbsp;Recommendations
+    <a class="toc" id="setup.recom" href="#a-606908788">2.2</a>&nbsp;&nbsp;Recommendations
   </h2>
   <div class="content"><p>The following software might make your interactions with Ruby-VPI more pleasant.</p>
 
 
 	<p><div class="paragraph">
-  <p class="title">Text merging tool</p>
+  <p class="title" id="setup.recom.merger">Text merging tool</p>
   <div class="content">An <em>interactive</em> text merging tool can greatly simplify the process of transferring wanted changes from one file to another. In particular, such tools are especially beneficial when using the <a class="xref" href="#usage.tools.generate">automated test generator</a>. A handful of the currently available open-source text merging tools are listed below.
 
 
@@ -1170,10 +1227,10 @@ your_memory.each_memoryWord { |w| w.put_value <span style="color:#00D; font-weig
 </div>
 <div class="section">
   <h2 class="title">
-    <a class="toc" id="setup.inst" href="#a-606794098">2.3</a>&nbsp;&nbsp;Installation
+    <a class="toc" id="setup.inst" href="#a-606914178">2.3</a>&nbsp;&nbsp;Installation
   </h2>
   <div class="content"><p><div class="tip">
-  <p class="title"><a class="toc" id="Tuning-for-maximum-performance" href="#a-606795708">Tip 1</a>.&nbsp;&nbsp;Tuning for maximum performance</p>
+  <p class="title"><a class="toc" id="Tuning-for-maximum-performance" href="#a-606915788">Tip 1</a>.&nbsp;&nbsp;Tuning for maximum performance</p>
 
   <img src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAADAAAAAwCAYAAABXAvmHAAAABHNCSVQICAgI
 fAhkiAAAAAlwSFlzAAAN1wAADdcBQiibeAAAABl0RVh0U29mdHdhcmUAd3d3
@@ -1250,7 +1307,7 @@ ta22BwC4nZ2dXdu2bfujlpaWe4wxNDMz84OzZ88em5qamkZ9ppfjAflu+bDc
 HGAANv6XHFhk9iI4CwDNm5m3aJG9Ww4o1MPnXQVe09fovEsXBC+AXO16LBK/
 0BYggPpqs9jeBlvqCnTNAP/jIXWgBeNF/YXzBfHxIoC3z5cj+Or2X3r9Ye2F
 1izgAAAAAElFTkSuQmCC
-" alt="tip" class="icon"/>
+" class="icon"/>
 
   <div class="content">You can tune your installation of Ruby-VPI for maximum performance by adding your C compiler&#8217;s optimization flag to the <code class="code"><span style="color:#036; font-weight:bold">CFLAGS</span></code> environment variable <em>before</em> you run the installation command (shown below). For example, if your C compiler is GCC, then you can set <code class="code"><span style="color:#036; font-weight:bold">CFLAGS</span></code> to <tt>-O9</tt> for maximum optimization.</div>
 </div>
@@ -1261,9 +1318,9 @@ Once your system has the <a class="xref" href="#setup.reqs">necessary requiremen
 ruby-vpi -v</pre>
 
 
-Otherwise, follow these instructions:
+Alternatively, if you do not wish to use RubyGems:
 	<ol>
-	<li>Download the newest <tt>tar.gz</tt> release package from <a href="http://rubyforge.org/frs/?group_id=1339">the project download area</a>.</li>
+	<li>Download the newest <tt>tar.gz</tt> release package from <a href="http://ruby-vpi.rubyforge.org/pkg">the project download area</a>.</li>
 		<li>Extract the release package anywhere you want on your system.</li>
 		<li>Go inside the extracted directory and run the following commands:</li>
 	</ol>
@@ -1273,7 +1330,7 @@ Otherwise, follow these instructions:
 ruby bin/ruby-vpi -v</pre>
 
 
-	<p>If the installation was successful, then you will see output like this: <pre>ruby-vpi 20.0.0 (2008-01-27) http://ruby-vpi.rubyforge.org /home/sun/src/ruby-vpi
+	<p>If the installation was successful, then you will see output like this: <pre>ruby-vpi 21.0.0 (2008-06-08) http://ruby-vpi.rubyforge.org /home/sun/src/ruby-vpi
 </pre></p>
 
 
@@ -1282,7 +1339,7 @@ ruby bin/ruby-vpi -v</pre>
 
 	<p><div class="section">
   <h3 class="title">
-    <a class="toc" id="setup.inst.windows" href="#a-606799148">2.3.1</a>&nbsp;&nbsp;Installing on Windows
+    <a class="toc" id="setup.inst.windows" href="#a-606919398">2.3.1</a>&nbsp;&nbsp;Installing on Windows
   </h3>
   <div class="content"><p>After Ruby-VPI is compiled, it is linked to symbols whose names begin with <tt>_vpi</tt>. In GNU/Linux and similar operating systems, these symbols are allowed to be undefined. However, this is not the case in Windows because we <a href="http://sourceware.org/ml/cygwin/2001-12/msg01293.html">cannot compile a shared object file with references to undefined symbols in Windows</a>.</p>
 
@@ -1306,7 +1363,7 @@ ruby bin/ruby-vpi -v</pre>
 </div>
 <div class="section">
   <h2 class="title">
-    <a class="toc" id="setup.maintenance" href="#a-606801708">2.4</a>&nbsp;&nbsp;Maintenance
+    <a class="toc" id="setup.maintenance" href="#a-606921958">2.4</a>&nbsp;&nbsp;Maintenance
   </h2>
   <div class="content"><p>You can upgrade to the latest release of Ruby-VPI by running the following command:</p>
 
@@ -1324,7 +1381,7 @@ ruby bin/ruby-vpi -v</pre>
 </div>
 <div class="section">
   <h2 class="title">
-    <a class="toc" id="setup.manifest" href="#a-606803858">2.5</a>&nbsp;&nbsp;Manifest
+    <a class="toc" id="setup.manifest" href="#a-606924108">2.5</a>&nbsp;&nbsp;Manifest
   </h2>
   <div class="content">Now that Ruby-VPI is installed on your system, let us examine its installation directory.
 	<ul>
@@ -1347,7 +1404,7 @@ Inside Ruby-VPI&#8217;s installation directory, you will see (among other things
 <div class="chapter">
   <h1 class="title">
     Chapter
-    <a class="toc" id="organization" href="#a-606810448">3</a>
+    <a class="toc" id="organization" href="#a-606931208">3</a>
 
     <br/>
 
@@ -1358,7 +1415,7 @@ Inside Ruby-VPI&#8217;s installation directory, you will see (among other things
 
 
 	<p><div class="figure">
-  <p class="title"><a class="toc" id="fig:organization.detail" href="#a-606812008">Figure 1</a>.&nbsp;&nbsp;Where does Ruby-VPI fit in?</p>
+  <p class="title"><a class="toc" id="fig:organization.detail" href="#a-606932768">Figure 1</a>.&nbsp;&nbsp;Where does Ruby-VPI fit in?</p>
   <div class="content"><img src="figures/organization_detailed.png" alt="" /></div>
 </div>
 As <a class="xref" href="#fig:organization.detail">Figure 1: <em>Where does Ruby-VPI fit in?</em></a> shows, Ruby-VPI is composed of two complementary parts: one interacts with VPI through the C language, while the other interacts with an executable specification written in the Ruby language. The former is complied during installation to produce dynamically loadable C libraries&#8212;-each tailored to accommodate the quirks of its respective Verilog simulator. The latter is not compiled because Ruby programs are interpreted dynamically.</p>
@@ -1366,19 +1423,19 @@ As <a class="xref" href="#fig:organization.detail">Figure 1: <em>Where does Ruby
 
 	<p><div class="section">
   <h2 class="title">
-    <a class="toc" id="Motivation" href="#a-606815068">3.1</a>&nbsp;&nbsp;Motivation
+    <a class="toc" id="Motivation" href="#a-606935998">3.1</a>&nbsp;&nbsp;Motivation
   </h2>
   <div class="content">If you would like to know why Ruby-VPI developed, please read this <a href="http://ruby-vpi.rubyforge.org/papers/masters_thesis.html#tth_sEc5.2">motivation section</a> of my masters thesis.</div>
 </div>
 <div class="section">
   <h2 class="title">
-    <a class="toc" id="organization.tests" href="#a-606817088">3.2</a>&nbsp;&nbsp;Tests
+    <a class="toc" id="organization.tests" href="#a-606938018">3.2</a>&nbsp;&nbsp;Tests
   </h2>
   <div class="content"><p>In Ruby-VPI, the process of functional verification is neatly packaged into self-contained, executable tests. As <a class="xref" href="#fig:organization">Figure 2: <em>Organization of a test in Ruby-VPI</em></a> illustrates, a test is composed of a <strong>bench</strong>, a <strong>design</strong>, and a <strong>specification</strong>.</p>
 
 
 	<p><div class="figure">
-  <p class="title"><a class="toc" id="fig:organization" href="#a-606820058">Figure 2</a>.&nbsp;&nbsp;Organization of a test in Ruby-VPI</p>
+  <p class="title"><a class="toc" id="fig:organization" href="#a-606941158">Figure 2</a>.&nbsp;&nbsp;Organization of a test in Ruby-VPI</p>
   <div class="content"><img src="figures/organization.png" alt="" /></div>
 </div>
 <strong>The bench</strong> is Ruby-VPI. It defines the environment in which functional verification takes place. This is analogous to a workbench in an electronics laboratory that is furnished with tools of measurement and manipulation such as oscilloscopes, voltmeters, soldering irons, and so on which enable engineers to verify electronic components and locate the source of defects within those components.</p>
@@ -1393,7 +1450,7 @@ As <a class="xref" href="#fig:organization.detail">Figure 1: <em>Where does Ruby
 <div class="chapter">
   <h1 class="title">
     Chapter
-    <a class="toc" id="usage" href="#a-606822688">4</a>
+    <a class="toc" id="usage" href="#a-606943788">4</a>
 
     <br/>
 
@@ -1402,13 +1459,13 @@ As <a class="xref" href="#fig:organization.detail">Figure 1: <em>Where does Ruby
 
   <div class="content"><div class="section">
   <h2 class="title">
-    <a class="toc" id="usage.theory" href="#a-606824258">4.1</a>&nbsp;&nbsp;Theory of operation
+    <a class="toc" id="usage.theory" href="#a-606945358">4.1</a>&nbsp;&nbsp;Theory of operation
   </h2>
   <div class="content"><p>When you run a Ruby-VPI test, the following chain reaction occurs.</p>
 
 
 	<p><div class="paragraph">
-  <p class="title">Rake (via the <tt>Rakefile</tt>)</p>
+  <p class="title" id="Rake-via-the-Rakefile">Rake (via the <tt>Rakefile</tt>)</p>
   <div class="content"><ol>
 	<li>Specifies a user-defined Ruby script that will be loaded
   by Ruby-VPI once the simulator has been launched.</li>
@@ -1417,20 +1474,20 @@ As <a class="xref" href="#fig:organization.detail">Figure 1: <em>Where does Ruby
 	</ol></div>
 </div>
 <div class="paragraph">
-  <p class="title">Verilog simulator</p>
+  <p class="title" id="Verilog-simulator">Verilog simulator</p>
   <div class="content"><ol>
 	<li>Launches the Ruby interpreter and loads Ruby-VPI into it.</li>
 	</ol></div>
 </div>
 <div class="paragraph">
-  <p class="title">Ruby-VPI</p>
+  <p class="title" id="Ruby-VPI">Ruby-VPI</p>
   <div class="content"><ol>
 	<li>Establishes the <a class="xref" href="#vpi">basic verification environment</a> (the nice library for <a class="xref" href="#vpi.handles">working with VPI handles</a>, and so on).</li>
 		<li>Loads the user-defined Ruby script that was specified by Rake.</li>
 	</ol></div>
 </div>
 <div class="paragraph">
-  <p class="title">User-defined Ruby script</p>
+  <p class="title" id="User-defined-Ruby-script">User-defined Ruby script</p>
   <div class="content"><ol>
 	<li>Determines what Verilog modules are going to be tested.</li>
 		<li>Determines what Ruby files are going to do the testing.</li>
@@ -1459,7 +1516,7 @@ Here, the <code class="code"><span style="color:#036; font-weight:bold">RubyVPI<
 </div>
 <div class="section">
   <h3 class="title">
-    <a class="toc" id="Test-files" href="#a-606835008">4.1.1</a>&nbsp;&nbsp;Test files
+    <a class="toc" id="Test-files" href="#a-606956448">4.1.1</a>&nbsp;&nbsp;Test files
   </h3>
   <div class="content"><p>Ruby-VPI tests (when produced by the <a class="xref" href="#usage.tools.generate">automated test generator</a>) are typically composed of the following files.</p>
 
@@ -1512,7 +1569,7 @@ Here, the <code class="code"><span style="color:#036; font-weight:bold">RubyVPI<
 </div></p></div>
 </div><div class="section">
   <h2 class="title">
-    <a class="toc" id="overview.relay" href="#a-606840438">4.2</a>&nbsp;&nbsp;Interacting with the Verilog simulator
+    <a class="toc" id="overview.relay" href="#a-606962218">4.2</a>&nbsp;&nbsp;Interacting with the Verilog simulator
   </h2>
   <div class="content"><p>In a typical VPI application written in C, the <em>Verilog simulator</em> is in charge. Verilog code temporarily transfers control to C by invoking C functions, which return control to Verilog when they finish.</p>
 
@@ -1524,7 +1581,7 @@ Here, the <code class="code"><span style="color:#036; font-weight:bold">RubyVPI<
 
 
 	<p><div class="figure">
-  <p class="title"><a class="toc" id="fig:ruby_relay" href="#a-606843408">Figure 3</a>.&nbsp;&nbsp;Interaction between Ruby and Verilog</p>
+  <p class="title"><a class="toc" id="fig:ruby_relay" href="#a-606965358">Figure 3</a>.&nbsp;&nbsp;Interaction between Ruby and Verilog</p>
   <div class="content"><img src="figures/ruby_relay.png" alt="" />
 
 
@@ -1542,13 +1599,13 @@ Another means of transferring control from the specification to the Verilog simu
 </div>
 <div class="section">
   <h2 class="title">
-    <a class="toc" id="vpi" href="#a-606846998">4.3</a>&nbsp;&nbsp;VPI in Ruby
+    <a class="toc" id="vpi" href="#a-606969118">4.3</a>&nbsp;&nbsp;VPI in Ruby
   </h2>
   <div class="content"><p>Ruby-VPI provides the <em>entire</em> IEEE Std 1364-2005 VPI interface to Ruby. This section will show you how to make use of it.</p>
 
 
 	<p><div class="note">
-  <p class="title"><a class="toc" id="Constants-are-capitalized-in-Ruby" href="#a-606848628">Note 1</a>.&nbsp;&nbsp;Constants are capitalized in Ruby</p>
+  <p class="title"><a class="toc" id="Constants-are-capitalized-in-Ruby" href="#a-606970748">Note 1</a>.&nbsp;&nbsp;Constants are capitalized in Ruby</p>
 
   <img src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAADAAAAAwCAYAAABXAvmHAAAABHNCSVQICAgI
 fAhkiAAAAAlwSFlzAAAN1wAADdcBQiibeAAAABl0RVh0U29mdHdhcmUAd3d3
@@ -1607,7 +1664,7 @@ bj2VSjFnzpxrKjafSSm5cOEC/f39KUAnrVsTgAkUAYU1NTUPx2KxjUEQTLmW
 YvOZpmnxjo6O3x48eHA76S4UB3qEUgohRBQoGLoyKTJJp+nyR97kmA1IwANS
 wODQ1auUSmYP9UNjoQBwAIv0DBUMFb6WZpNuRB9wSYsfUEr5kOdfSiGETrr1
 DUCQhrhWJkj394A0gKeUCjVo3r9Zv0r2P3yyQqPd16MPAAAAAElFTkSuQmCC
-" alt="note" class="icon"/>
+" class="icon"/>
 
   <div class="content"><p>In the remainder of this guide, you may be surprised to see that VPI constants such as <code class="code">vpiIntVal</code> are written with a captialized name, as <code class="code"><span style="color:#036; font-weight:bold">VpiIntVal</span></code>. The reason for this discrepancy is that in Ruby, the names of constants are capitalized.</p>
 
@@ -1616,7 +1673,7 @@ DUCQhrhWJkj394A0gKeUCjVo3r9Zv0r2P3yyQqPd16MPAAAAAElFTkSuQmCC
 </div>
 <div class="section">
   <h3 class="title">
-    <a class="toc" id="vpi.handles" href="#a-606850438">4.3.1</a>&nbsp;&nbsp;Handles
+    <a class="toc" id="vpi.handles" href="#a-606972558">4.3.1</a>&nbsp;&nbsp;Handles
   </h3>
   <div class="content"><p>A <strong>handle</strong> is a reference to an object (such as a module, register, wire, and so on) inside the Verilog simulation. Handles allows you to inspect and manipulate the design under test and its internal components. They are instances of the <code class="code"><span style="color:#036; font-weight:bold">VPI</span>::<span style="color:#036; font-weight:bold">Handle</span></code> class (see <a href="api/ruby/classes/VPI/Handle.html">reference documentation</a> for details) in Ruby-VPI.</p>
 
@@ -1628,12 +1685,12 @@ DUCQhrhWJkj394A0gKeUCjVo3r9Zv0r2P3yyQqPd16MPAAAAAElFTkSuQmCC
 
 
 	<p><div class="paragraph">
-  <p class="title">Shortcuts for productivity</p>
+  <p class="title" id="Shortcuts-for-productivity">Shortcuts for productivity</p>
   <div class="content">Given a handle, Ruby-VPI allows you to access (1) its relatives and (2) its properties simply by invoking methods on the handle. If a handle&#8217;s relative happens to have the same name as one its properties, then the relative is given priority because a handle&#8217;s properties can always be accessed explicitly through the <code class="code">handle.get_value</code> and <code class="code">handle.put_value</code> methods.</div>
 </div>
 <div class="section">
   <h4 class="title">
-    <a class="toc" id="vpi.handles.relatives" href="#a-606856398">4.3.1.1</a>&nbsp;&nbsp;Accessing a handle&#8217;s relatives
+    <a class="toc" id="vpi.handles.relatives" href="#a-606978858">4.3.1.1</a>&nbsp;&nbsp;Accessing a handle&#8217;s relatives
   </h4>
   <div class="content"><p>Imagine that the design under test, say <em>foo</em>, instantiated a Verilog module named <em>bar</em>, which in turn contained a register named <em>baz</em>. To access baz from Ruby, one could employ VPI idioms by writing:</p>
 
@@ -1658,7 +1715,7 @@ baz = vpi_handle_by_name( <span style="background-color:#fff0f0"><span style="co
 </div>
 <div class="section">
   <h4 class="title">
-    <a class="toc" id="Accessing-a-handle-s-properties" href="#a-606858628">4.3.1.2</a>&nbsp;&nbsp;Accessing a handle&#8217;s properties
+    <a class="toc" id="Accessing-a-handle-s-properties" href="#a-606981088">4.3.1.2</a>&nbsp;&nbsp;Accessing a handle&#8217;s properties
   </h4>
   <div class="content"><p>Imagine that the design under test, say <em>foo</em>, contained a register named <em>bar</em>. To access the integer value of <em>bar</em> in Ruby-VPI, one could employ VPI idioms by writing:</p>
 
@@ -1688,7 +1745,7 @@ result = wrapper.value.str.to_i( <span style="color:#00D; font-weight:bold">16</
 	<code class="code">result = foo.bar.intVal</code></div>
 </div>
 <div class="figure">
-  <p class="title"><a class="toc" id="fig:method-naming-format" href="#a-606862348">Figure 4</a>.&nbsp;&nbsp;Method naming format for accessing a handle&#8217;s properties</p>
+  <p class="title"><a class="toc" id="fig:method-naming-format" href="#a-606984978">Figure 4</a>.&nbsp;&nbsp;Method naming format for accessing a handle&#8217;s properties</p>
   <div class="content"><table border="1">
 		<tr>
 			<th>Operation </th>
@@ -1732,7 +1789,7 @@ result = wrapper.value.str.to_i( <span style="color:#00D; font-weight:bold">16</
 	</ul></div>
 </div>
 <div class="table">
-  <p class="title"><a class="toc" id="tbl:accessors" href="#a-606865648">Table 1</a>.&nbsp;&nbsp;Possible accessors and their implications</p>
+  <p class="title"><a class="toc" id="tbl:accessors" href="#a-606988448">Table 1</a>.&nbsp;&nbsp;Possible accessors and their implications</p>
   <div class="content"><table border="1">
 		<tr>
 			<th>Accessor </th>
@@ -1777,7 +1834,7 @@ result = wrapper.value.str.to_i( <span style="color:#00D; font-weight:bold">16</
 	</table></div>
 </div>
 <div class="table">
-  <p class="title"><a class="toc" id="ex:properties" href="#a-606867538">Table 2</a>.&nbsp;&nbsp;Examples of accessing a handle&#8217;s properties</p>
+  <p class="title"><a class="toc" id="ex:properties" href="#a-606990338">Table 2</a>.&nbsp;&nbsp;Examples of accessing a handle&#8217;s properties</p>
   <div class="content"><table border="1">
 		<tr>
 			<th rowspan="2">Ruby expression </th>
@@ -2094,7 +2151,7 @@ result = wrapper.value.str.to_i( <span style="color:#00D; font-weight:bold">16</
 </div>
 <div class="section">
   <h3 class="title">
-    <a class="toc" id="vpi.callbacks" href="#a-606870058">4.3.2</a>&nbsp;&nbsp;Callbacks
+    <a class="toc" id="vpi.callbacks" href="#a-606992858">4.3.2</a>&nbsp;&nbsp;Callbacks
   </h3>
   <div class="content"><p>A <em>callback</em> is a mechanism that makes the Verilog simuluator execute a block of code (known as a &#8220;callback handler&#8221;) when some prescribed event occurs in the simulation.</p>
 
@@ -2103,7 +2160,7 @@ result = wrapper.value.str.to_i( <span style="color:#00D; font-weight:bold">16</
 
 
 	<p><div class="example">
-  <p class="title"><a class="toc" id="ex:callback" href="#a-606871738">Example 1</a>.&nbsp;&nbsp;Using a callback for value change notification</p>
+  <p class="title"><a class="toc" id="ex:callback" href="#a-606994538">Example 1</a>.&nbsp;&nbsp;Using a callback for value change notification</p>
   <div class="content"><p>This example shows how to use a callback for notification of changes in a handle&#8217;s <code class="code"><span style="color:#036; font-weight:bold">VpiIntVal</span></code> property. When you no longer need this callback, you can tear it down using <code class="code">vpi_remove_cb</code>.</p>
 
 
@@ -2140,7 +2197,7 @@ vpi_register_cb( alarm ) <span style="color:#080; font-weight:bold">do</span> |i
 </div>
 <div class="section">
   <h2 class="title">
-    <a class="toc" id="usage.concurrency" href="#a-606880188">4.4</a>&nbsp;&nbsp;Concurrency
+    <a class="toc" id="usage.concurrency" href="#a-607003668">4.4</a>&nbsp;&nbsp;Concurrency
   </h2>
   <div class="content"><p>Ruby-VPI provides a concurrency model that allows you to run blocks of code in parallel.  These blocks of code are known as <em>concurrent processes</em> and they are equivalent to the &#8220;initial&#8221;, &#8220;always&#8221; and &#8220;forever&#8221; blocks in Verilog.</p>
 
@@ -2158,7 +2215,7 @@ vpi_register_cb( alarm ) <span style="color:#080; font-weight:bold">do</span> |i
 
 
 	<p><div class="caution">
-  <p class="title"><a class="toc" id="Assignments-inside-processes-are-non-blocking" href="#a-606881928">Caution 1</a>.&nbsp;&nbsp;Assignments inside processes are non-blocking</p>
+  <p class="title"><a class="toc" id="Assignments-inside-processes-are-non-blocking" href="#a-607005408">Caution 1</a>.&nbsp;&nbsp;Assignments inside processes are non-blocking</p>
 
   <img src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAADAAAAAwCAYAAABXAvmHAAAABHNCSVQICAgI
 fAhkiAAAAAlwSFlzAAAN1wAADdcBQiibeAAAABl0RVh0U29mdHdhcmUAd3d3
@@ -2212,13 +2269,13 @@ lQP3aeBFBNHmWbBT/aV/Wn8qvh+F0Uuw73noCsEocEkpFUwKABARJ+CKFwex
 MFmBqURf37Fpcf9hIAgEgHFgDBhLzIHkJFZKjYuIAiJACJiIH79ZAhKXdSTO
 ECQGPj690VUrcfw2ZYuXhICbYRZiUUhEYFLNkjYs6s3c/5J97/9q8F/RUcwR
 4xicOQAAAABJRU5ErkJggg==
-" alt="caution" class="icon"/>
+" class="icon"/>
 
   <div class="content">As a result of the constraints described above, all assignments inside processes are treated like Verilog&#8217;s non-blocking assignments.  Think about it: blocking assignments allow a process to make changes to simulation values (possibly) before other processes read those values.  Since the second constraint makes all processes see the same input while they are executing, it is impossible to support blocking assignments inside processes.</div>
 </div>
 <div class="section">
   <h3 class="title">
-    <a class="toc" id="Creating-a-concurrent-process" href="#a-606883708">4.4.1</a>&nbsp;&nbsp;Creating a concurrent process
+    <a class="toc" id="Creating-a-concurrent-process" href="#a-607007188">4.4.1</a>&nbsp;&nbsp;Creating a concurrent process
   </h3>
   <div class="content"><p>You can create a concurrent proceess by passing a block of code to the <code class="code">process</code> method.  Once the process finishes executing this block of code, it will disappear automatically.  This behavior mimics the &#8220;initial&#8221; blocks of the Verilog language.</p>
 
@@ -2227,7 +2284,7 @@ ECQGPj690VUrcfw2ZYuXhICbYRZiUUhEYFLNkjYs6s3c/5J97/9q8F/RUcwR
 
 
 	<p><div class="example">
-  <p class="title"><a class="toc" id="An-edge-triggered-always-block" href="#a-606885348">Example 2</a>.&nbsp;&nbsp;An edge-triggered &#8220;always&#8221; block</p>
+  <p class="title"><a class="toc" id="An-edge-triggered-always-block" href="#a-607008828">Example 2</a>.&nbsp;&nbsp;An edge-triggered &#8220;always&#8221; block</p>
   <div class="content"><p>Suppose you have the following Verilog code:</p>
 
 
@@ -2252,7 +2309,7 @@ always <span style="color:#080; font-weight:bold">do</span>
 </pre></div>
 </div>
 <div class="example">
-  <p class="title"><a class="toc" id="A-change-triggered-combinational-always-block" href="#a-606887298">Example 3</a>.&nbsp;&nbsp;A change-triggered (combinational) &#8220;always&#8221; block</p>
+  <p class="title"><a class="toc" id="A-change-triggered-combinational-always-block" href="#a-607010778">Example 3</a>.&nbsp;&nbsp;A change-triggered (combinational) &#8220;always&#8221; block</p>
   <div class="content"><p>Suppose you have the following Verilog code:</p>
 
 
@@ -2288,7 +2345,7 @@ always <span style="color:#080; font-weight:bold">do</span>
 </div>
 <div class="section">
   <h2 class="title">
-    <a class="toc" id="usage.prototyping" href="#a-606890138">4.5</a>&nbsp;&nbsp;Prototyping
+    <a class="toc" id="usage.prototyping" href="#a-607013618">4.5</a>&nbsp;&nbsp;Prototyping
   </h2>
   <div class="content"><p>Ruby-VPI enables you to rapidly prototype your designs in Ruby without having to do full-scale implementations in Verilog. This lets you explore and evaluate different design choices quickly.</p>
 
@@ -2301,7 +2358,7 @@ always <span style="color:#080; font-weight:bold">do</span>
 
 	<p><div class="section">
   <h3 class="title">
-    <a class="toc" id="Creating-a-prototype" href="#a-606894508">4.5.1</a>&nbsp;&nbsp;Creating a prototype
+    <a class="toc" id="Creating-a-prototype" href="#a-607018328">4.5.1</a>&nbsp;&nbsp;Creating a prototype
   </h3>
   <div class="content"><ol>
 	<li>Start with a <a class="xref" href="#usage.tutorial.declare-design">Verilog module declaration</a> for your design.</li>
@@ -2319,7 +2376,7 @@ always <span style="color:#080; font-weight:bold">do</span>
 </div>
 <div class="section">
   <h2 class="title">
-    <a class="toc" id="usage.debugger" href="#a-606905198">4.6</a>&nbsp;&nbsp;Interactive debugging
+    <a class="toc" id="usage.debugger" href="#a-607030038">4.6</a>&nbsp;&nbsp;Interactive debugging
   </h2>
   <div class="content"><p>The <a href="http://www.datanoise.com/articles/category/ruby-debug">ruby-debug project</a> serves as the interactive debugger for Ruby-VPI.</p>
 
@@ -2332,7 +2389,7 @@ always <span style="color:#080; font-weight:bold">do</span>
 
 	<p><div class="section">
   <h3 class="title">
-    <a class="toc" id="usage.debugger.init" href="#a-606908278">4.6.1</a>&nbsp;&nbsp;Advanced initialization
+    <a class="toc" id="usage.debugger.init" href="#a-607033288">4.6.1</a>&nbsp;&nbsp;Advanced initialization
   </h3>
   <div class="content">By default, Ruby-VPI enables the debugger by invoking the <code class="code"><span style="color:#036; font-weight:bold">Debugger</span>.start</code> method. If you wish to perform more advanced initialization, such as having the debugger accept remote network connections for interfacing with a remote debugging session or perhaps with an IDE (see <a href="http://www.datanoise.com/articles/category/ruby-debug">the ruby-debug documentation</a> for details), then:
 
@@ -2345,7 +2402,7 @@ always <span style="color:#080; font-weight:bold">do</span>
 </div>
 <div class="section">
   <h2 class="title">
-    <a class="toc" id="usage.runner" href="#a-606910748">4.7</a>&nbsp;&nbsp;Test runner
+    <a class="toc" id="usage.runner" href="#a-607035758">4.7</a>&nbsp;&nbsp;Test runner
   </h2>
   <div class="content"><p>A test runner is a file, generated by the <a class="xref" href="#usage.tools.generate">automated test generator</a> whose name ends with <tt>.rake</tt>. It helps you run generated tests&#8212;you can think of it as a <em>makefile</em> if you are familiar with C programming in a UNIX environment.</p>
 
@@ -2368,7 +2425,7 @@ rake vsim     # Simulate with Mentor Modelsim.
 
 	<p><div class="section">
   <h3 class="title">
-    <a class="toc" id="usage.runner.env-vars" href="#a-606913938">4.7.1</a>&nbsp;&nbsp;Environment variables
+    <a class="toc" id="usage.runner.env-vars" href="#a-607039108">4.7.1</a>&nbsp;&nbsp;Environment variables
   </h3>
   <div class="content"><p>Test runners support the following <em>environment</em> variables, which allow you to easily change the behavior of the test runner.</p>
 
@@ -2389,7 +2446,7 @@ rake vsim     # Simulate with Mentor Modelsim.
 
 	<p><div class="section">
   <h4 class="title">
-    <a class="toc" id="Variables-as-command-line-arguments" href="#a-606917008">4.7.1.1</a>&nbsp;&nbsp;Variables as command-line arguments
+    <a class="toc" id="Variables-as-command-line-arguments" href="#a-607042348">4.7.1.1</a>&nbsp;&nbsp;Variables as command-line arguments
   </h4>
   <div class="content">You can specify variable assignments as arguments to the <strong>rake</strong> command. For example, <pre>rake DEBUGGER=1</pre> is equivalent to
 <pre>
@@ -2405,7 +2462,7 @@ rake
 
 
 	<p><div class="example">
-  <p class="title"><a class="toc" id="Running-a-test-with-environment-variables" href="#a-606919158">Example 4</a>.&nbsp;&nbsp;Running a test with environment variables</p>
+  <p class="title"><a class="toc" id="Running-a-test-with-environment-variables" href="#a-607044498">Example 4</a>.&nbsp;&nbsp;Running a test with environment variables</p>
   <div class="content"><p>Below, we enable the prototype and code coverage analysis:
 <pre>rake -f your_test_runner.rake PROTOTYPE=1 COVERAGE=1</pre></p>
 
@@ -2419,7 +2476,7 @@ rake
 </div>
 <div class="section">
   <h2 class="title">
-    <a class="toc" id="usage.tools" href="#a-606921818">4.8</a>&nbsp;&nbsp;Tools
+    <a class="toc" id="usage.tools" href="#a-607047158">4.8</a>&nbsp;&nbsp;Tools
   </h2>
   <div class="content"><p>The <strong>ruby-vpi</strong> command serves as a front-end to the tools provided by Ruby-VPI. You can see its help information (reproduced below) by simply running the command without any arguments.</p>
 
@@ -2427,27 +2484,27 @@ rake
 	<pre>This is a front-end for tools provided by Ruby-VPI.
 
 Usage:
-ruby-vpi                      Show this help message
-ruby-vpi -v                   Show version information
-ruby-vpi TOOL --help          Show help message for TOOL
-ruby-vpi TOOL arguments...    Run TOOL with some arguments
+  ruby-vpi                      Show this help message
+  ruby-vpi -v                   Show version information
+  ruby-vpi TOOL --help          Show help message for TOOL
+  ruby-vpi TOOL arguments...    Run TOOL with some arguments
 
 Tools:
-convert    Converts Verilog `defines, constants, ranges, etc. into Ruby syntax.
-generate   Generates test skeletons from Verilog 2001/1995 module declarations.
+  convert    Converts Verilog `defines, constants, ranges, etc. into Ruby syntax.
+  generate   Generates test skeletons from Verilog 2001/1995 module declarations.
 
 Simulators:
-cver       GPL Cver
-ivl        Icarus Verilog
-ncsim      Cadence NC-Sim
-vcs        Synopsys VCS
-vsim       Mentor Modelsim
+  cver       GPL Cver
+  ivl        Icarus Verilog
+  ncsim      Cadence NC-Sim
+  vcs        Synopsys VCS
+  vsim       Mentor Modelsim
 </pre>
 
 
 	<p><div class="section">
   <h3 class="title">
-    <a class="toc" id="usage.tools.generate" href="#a-606923678">4.8.1</a>&nbsp;&nbsp;Automated test generation
+    <a class="toc" id="usage.tools.generate" href="#a-607049018">4.8.1</a>&nbsp;&nbsp;Automated test generation
   </h3>
   <div class="content"><p>The <strong>generate</strong> tool generates scaffolding for Ruby-VPI tests from Verilog module declarations (written in either Verilog 2001 or Verilog 95 style).</p>
 
@@ -2467,7 +2524,7 @@ A Ruby-VPI test is composed of the following files:
 
 
 	<p><div class="caution">
-  <p class="title"><a class="toc" id="Do-not-rename-generated-files" href="#a-606928078">Caution 2</a>.&nbsp;&nbsp;Do not rename generated files</p>
+  <p class="title"><a class="toc" id="Do-not-rename-generated-files" href="#a-607053758">Caution 2</a>.&nbsp;&nbsp;Do not rename generated files</p>
 
   <img src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAADAAAAAwCAYAAABXAvmHAAAABHNCSVQICAgI
 fAhkiAAAAAlwSFlzAAAN1wAADdcBQiibeAAAABl0RVh0U29mdHdhcmUAd3d3
@@ -2521,7 +2578,7 @@ lQP3aeBFBNHmWbBT/aV/Wn8qvh+F0Uuw73noCsEocEkpFUwKABARJ+CKFwex
 MFmBqURf37Fpcf9hIAgEgHFgDBhLzIHkJFZKjYuIAiJACJiIH79ZAhKXdSTO
 ECQGPj690VUrcfw2ZYuXhICbYRZiUUhEYFLNkjYs6s3c/5J97/9q8F/RUcwR
 4xicOQAAAABJRU5ErkJggg==
-" alt="caution" class="icon"/>
+" class="icon"/>
 
   <div class="content">Ruby-VPI uses the convention described above to dynamically create a direct Ruby interface to the design under test, so <em>do not</em> rename the generated files arbitrarily.</div>
 </div>
@@ -2532,7 +2589,7 @@ By producing multiple files, the automated test generator physically decouples t
 
 
 	<p><div class="tip">
-  <p class="title"><a class="toc" id="Using-kdiff3-with-the-automated-test-generator." href="#a-606929888">Tip 2</a>.&nbsp;&nbsp;Using <strong>kdiff3</strong> with the automated test generator.</p>
+  <p class="title"><a class="toc" id="Using-kdiff3-with-the-automated-test-generator." href="#a-607055568">Tip 2</a>.&nbsp;&nbsp;Using <strong>kdiff3</strong> with the automated test generator.</p>
 
   <img src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAADAAAAAwCAYAAABXAvmHAAAABHNCSVQICAgI
 fAhkiAAAAAlwSFlzAAAN1wAADdcBQiibeAAAABl0RVh0U29mdHdhcmUAd3d3
@@ -2609,7 +2666,7 @@ ta22BwC4nZ2dXdu2bfujlpaWe4wxNDMz84OzZ88em5qamkZ9ppfjAflu+bDc
 HGAANv6XHFhk9iI4CwDNm5m3aJG9Ww4o1MPnXQVe09fovEsXBC+AXO16LBK/
 0BYggPpqs9jeBlvqCnTNAP/jIXWgBeNF/YXzBfHxIoC3z5cj+Or2X3r9Ye2F
 1izgAAAAAElFTkSuQmCC
-" alt="tip" class="icon"/>
+" class="icon"/>
 
   <div class="content"><ol>
 	<li>Create a file named <tt>merge2</tt> with the following content: <pre class="code">
@@ -2628,7 +2685,7 @@ kdiff3 --auto --output <span style="background-color:#fff0f0"><span style="color
 </div>
 <div class="section">
   <h3 class="title">
-    <a class="toc" id="usage.tools.convert" href="#a-606932168">4.8.2</a>&nbsp;&nbsp;Verilog to Ruby conversion
+    <a class="toc" id="usage.tools.convert" href="#a-607057848">4.8.2</a>&nbsp;&nbsp;Verilog to Ruby conversion
   </h3>
   <div class="content"><p>The <strong>convert</strong> tool can be used to convert Verilog header files into Ruby. You can try it by running the <pre>ruby-vpi convert --help</pre> command.</p>
 
@@ -2638,7 +2695,7 @@ kdiff3 --auto --output <span style="background-color:#fff0f0"><span style="color
 </div>
 <div class="section">
   <h2 class="title">
-    <a class="toc" id="usage.tutorial" href="#a-606934638">4.9</a>&nbsp;&nbsp;Tutorial
+    <a class="toc" id="usage.tutorial" href="#a-607060318">4.9</a>&nbsp;&nbsp;Tutorial
   </h2>
   <div class="content"><ol>
 	<li><a class="xref" href="#usage.tutorial.declare-design">Declare a design</a> using Verilog 2001 syntax.</li>
@@ -2653,7 +2710,7 @@ kdiff3 --auto --output <span style="background-color:#fff0f0"><span style="color
 
 	<p><div class="section">
   <h3 class="title">
-    <a class="toc" id="usage.tutorial.declare-design" href="#a-606947158">4.9.1</a>&nbsp;&nbsp;Start with a Verilog design
+    <a class="toc" id="usage.tutorial.declare-design" href="#a-607074198">4.9.1</a>&nbsp;&nbsp;Start with a Verilog design
   </h3>
   <div class="content"><p>First, we need a Verilog design to test. In this tutorial, <a class="xref" href="#fig:counter.v_decl">Example 5: <em>Declaration of a simple up-counter with synchronous reset</em></a> will serve as our design under test. Its interface is composed of the following parts:</p>
 
@@ -2667,7 +2724,7 @@ kdiff3 --auto --output <span style="background-color:#fff0f0"><span style="color
 
 
 	<p><div class="example">
-  <p class="title"><a class="toc" id="fig:counter.v_decl" href="#a-606950328">Example 5</a>.&nbsp;&nbsp;Declaration of a simple up-counter with synchronous reset</p>
+  <p class="title"><a class="toc" id="fig:counter.v_decl" href="#a-607077538">Example 5</a>.&nbsp;&nbsp;Declaration of a simple up-counter with synchronous reset</p>
   <div class="content"><pre class="code" lang="verilog">
 module counter #(parameter Size = 5) (
   input                   clock,
@@ -2681,7 +2738,7 @@ Before we continue, save the source code shown in <a class="xref" href="#fig:cou
 </div>
 <div class="section">
   <h3 class="title">
-    <a class="toc" id="usage.tutorial.generate-test" href="#a-606953958">4.9.2</a>&nbsp;&nbsp;Generate a test
+    <a class="toc" id="usage.tutorial.generate-test" href="#a-607081338">4.9.2</a>&nbsp;&nbsp;Generate a test
   </h3>
   <div class="content"><p>Now that we have a Verilog design to test, we shall use the <a class="xref" href="#usage.tools.generate">generate</a> tool to generate some scaffolding for our test. This tool allows us to implement our specification using RSpec, xUnit, or any other format.</p>
 
@@ -2706,7 +2763,7 @@ cp counter.v xUnit
 
 
 	<p><div class="example">
-  <p class="title"><a class="toc" id="fig:generate-test.RSpec" href="#a-606962678">Example 6</a>.&nbsp;&nbsp;Generating a test with specification in RSpec format</p>
+  <p class="title"><a class="toc" id="fig:generate-test.RSpec" href="#a-607090908">Example 6</a>.&nbsp;&nbsp;Generating a test with specification in RSpec format</p>
   <div class="content"><pre>
 $ ruby-vpi generate counter.v --RSpec
 
@@ -2719,7 +2776,7 @@ $ ruby-vpi generate counter.v --RSpec
 </pre></div>
 </div>
 <div class="example">
-  <p class="title"><a class="toc" id="fig:generate-test.xUnit" href="#a-606964548">Example 7</a>.&nbsp;&nbsp;Generating a test with specification in xUnit format</p>
+  <p class="title"><a class="toc" id="fig:generate-test.xUnit" href="#a-607092778">Example 7</a>.&nbsp;&nbsp;Generating a test with specification in xUnit format</p>
   <div class="content"><pre>
 $ ruby-vpi generate counter.v --xUnit
 
@@ -2734,7 +2791,7 @@ $ ruby-vpi generate counter.v --xUnit
 </div>
 <div class="section">
   <h3 class="title">
-    <a class="toc" id="usage.tutorial.specification" href="#a-606966828">4.9.3</a>&nbsp;&nbsp;Specify your expectations
+    <a class="toc" id="usage.tutorial.specification" href="#a-607095058">4.9.3</a>&nbsp;&nbsp;Specify your expectations
   </h3>
   <div class="content"><p>So far, the test generation tool has created a basic foundation for our test Now we must build upon this foundation by identifying our <a class="xref" href="#glossary.expectation">expectation</a> of the design under test. That is, how do we expect the design to <em>behave</em> under certain conditions?</p>
 
@@ -2751,7 +2808,7 @@ Here are some reasonable expectations for our simple counter:
 
 
 <div class="example">
-  <p class="title"><a class="toc" id="fig:RSpec-counter_spec.rb" href="#a-606972788">Example 8</a>.&nbsp;&nbsp;Specification implemented in RSpec format</p>
+  <p class="title"><a class="toc" id="fig:RSpec-counter_spec.rb" href="#a-607101528">Example 8</a>.&nbsp;&nbsp;Specification implemented in RSpec format</p>
   <div class="content"><pre class="code">require <span style="background-color:#fff0f0"><span style="color:#710">'</span><span style="color:#D20">spec</span><span style="color:#710">'</span></span>
 
 <span style="color:#888"># lowest upper bound of counter's value</span>
@@ -2790,10 +2847,11 @@ describe <span style="background-color:#fff0f0"><span style="color:#710">&quot;<
     <span style="color:#036; font-weight:bold">DUT</span>.cycle! <span style="color:#888"># increment the counter</span>
     <span style="color:#036; font-weight:bold">DUT</span>.count.intVal.should == <span style="color:#00D; font-weight:bold">0</span>
   <span style="color:#080; font-weight:bold">end</span>
-<span style="color:#080; font-weight:bold">end</span></pre></div>
+<span style="color:#080; font-weight:bold">end</span>
+</pre></div>
 </div>
 <div class="example">
-  <p class="title"><a class="toc" id="fig:xUnit-counter_spec.rb" href="#a-606975088">Example 9</a>.&nbsp;&nbsp;Specification implemented in xUnit format</p>
+  <p class="title"><a class="toc" id="fig:xUnit-counter_spec.rb" href="#a-607103348">Example 9</a>.&nbsp;&nbsp;Specification implemented in xUnit format</p>
   <div class="content"><pre class="code">require <span style="background-color:#fff0f0"><span style="color:#710">'</span><span style="color:#D20">test/unit</span><span style="color:#710">'</span></span>
 
 <span style="color:#888"># lowest upper bound of counter's value</span>
@@ -2832,7 +2890,8 @@ describe <span style="background-color:#fff0f0"><span style="color:#710">&quot;<
     <span style="color:#036; font-weight:bold">DUT</span>.cycle! <span style="color:#888"># increment the counter</span>
     assert_equal( <span style="color:#00D; font-weight:bold">0</span>, <span style="color:#036; font-weight:bold">DUT</span>.count.intVal )
   <span style="color:#080; font-weight:bold">end</span>
-<span style="color:#080; font-weight:bold">end</span></pre></div>
+<span style="color:#080; font-weight:bold">end</span>
+</pre></div>
 </div>
 Before we continue,
 	<ol>
@@ -2842,13 +2901,13 @@ Before we continue,
 </div>
 <div class="section">
   <h3 class="title">
-    <a class="toc" id="usage.tutorial.implement-proto" href="#a-606069158">4.9.4</a>&nbsp;&nbsp;Implement the prototype
+    <a class="toc" id="usage.tutorial.implement-proto" href="#a-607108658">4.9.4</a>&nbsp;&nbsp;Implement the prototype
   </h3>
   <div class="content"><p>Now that we have a specification against which to verify our design 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. The result of this proceess is illustrated by <a class="xref" href="#fig:counter_proto.rb">Example 10: <em>Ruby prototype of our Verilog design</em></a>.</p>
 
 
 	<p><div class="example">
-  <p class="title"><a class="toc" id="fig:counter_proto.rb" href="#a-606100048">Example 10</a>.&nbsp;&nbsp;Ruby prototype of our Verilog design</p>
+  <p class="title"><a class="toc" id="fig:counter_proto.rb" href="#a-607112038">Example 10</a>.&nbsp;&nbsp;Ruby prototype of our Verilog design</p>
   <div class="content"><pre class="code"><span style="color:#080; font-weight:bold">if</span> <span style="color:#036; font-weight:bold">RubyVPI</span>::<span style="color:#036; font-weight:bold">USE_PROTOTYPE</span>
   always <span style="color:#080; font-weight:bold">do</span>
     wait <span style="color:#080; font-weight:bold">until</span> <span style="color:#036; font-weight:bold">DUT</span>.clock.posedge?
@@ -2859,13 +2918,14 @@ Before we continue,
       <span style="color:#036; font-weight:bold">DUT</span>.count.intVal += <span style="color:#00D; font-weight:bold">1</span>
     <span style="color:#080; font-weight:bold">end</span>
   <span style="color:#080; font-weight:bold">end</span>
-<span style="color:#080; font-weight:bold">end</span></pre></div>
+<span style="color:#080; font-weight:bold">end</span>
+</pre></div>
 </div>
 Before we continue, replace the contents of the files named <tt>RSpec/counter_proto.rb</tt> and <tt>xUnit/counter_proto.rb</tt> with the source code shown in <a class="xref" href="#fig:counter_proto.rb">Example 10: <em>Ruby prototype of our Verilog design</em></a>.</p></div>
 </div>
 <div class="section">
   <h3 class="title">
-    <a class="toc" id="usage.tutorial.test-proto" href="#a-606122988">4.9.5</a>&nbsp;&nbsp;Verify the prototype
+    <a class="toc" id="usage.tutorial.test-proto" href="#a-607115808">4.9.5</a>&nbsp;&nbsp;Verify the prototype
   </h3>
   <div class="content"><p>Now that we have implemented our prototype, we are ready to verify it against our specification by running the test This process is illustrated by <a class="xref" href="#fig:test-proto.RSpec">Example 11: <em>Running a test with specification in RSpec format</em></a> and <a class="xref" href="#fig:test-proto.unit-test">Example 12: <em>Running a test with specification in xUnit format</em></a>.</p>
 
@@ -2874,7 +2934,7 @@ Before we continue, replace the contents of the files named <tt>RSpec/counter_pr
 
 
 	<p><div class="example">
-  <p class="title"><a class="toc" id="fig:test-proto.RSpec" href="#a-606139338">Example 11</a>.&nbsp;&nbsp;Running a test with specification in RSpec format</p>
+  <p class="title"><a class="toc" id="fig:test-proto.RSpec" href="#a-606210758">Example 11</a>.&nbsp;&nbsp;Running a test with specification in RSpec format</p>
   <div class="content"><pre>
 $ cd RSpec
 $ rake cver PROTOTYPE=1
@@ -2889,7 +2949,7 @@ cd -
 </pre></div>
 </div>
 <div class="example">
-  <p class="title"><a class="toc" id="fig:test-proto.unit-test" href="#a-606145238">Example 12</a>.&nbsp;&nbsp;Running a test with specification in xUnit format</p>
+  <p class="title"><a class="toc" id="fig:test-proto.unit-test" href="#a-606234128">Example 12</a>.&nbsp;&nbsp;Running a test with specification in xUnit format</p>
   <div class="content"><pre>
 $ cd xUnit
 $ rake cver PROTOTYPE=1
@@ -2904,7 +2964,7 @@ Finished in 0.043859 seconds.
 </pre></div>
 </div>
 <div class="tip">
-  <p class="title"><a class="toc" id="What-can-the-test-runner-do" href="#a-606150528">Tip 3</a>.&nbsp;&nbsp;What can the test runner do?</p>
+  <p class="title"><a class="toc" id="What-can-the-test-runner-do" href="#a-606244898">Tip 3</a>.&nbsp;&nbsp;What can the test runner do?</p>
 
   <img src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAADAAAAAwCAYAAABXAvmHAAAABHNCSVQICAgI
 fAhkiAAAAAlwSFlzAAAN1wAADdcBQiibeAAAABl0RVh0U29mdHdhcmUAd3d3
@@ -2981,20 +3041,20 @@ ta22BwC4nZ2dXdu2bfujlpaWe4wxNDMz84OzZ88em5qamkZ9ppfjAflu+bDc
 HGAANv6XHFhk9iI4CwDNm5m3aJG9Ww4o1MPnXQVe09fovEsXBC+AXO16LBK/
 0BYggPpqs9jeBlvqCnTNAP/jIXWgBeNF/YXzBfHxIoC3z5cj+Or2X3r9Ye2F
 1izgAAAAAElFTkSuQmCC
-" alt="tip" class="icon"/>
+" class="icon"/>
 
   <div class="content">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.</div>
 </div></p></div>
 </div>
 <div class="section">
   <h3 class="title">
-    <a class="toc" id="usage.tutorial.implement-design" href="#a-606168938">4.9.6</a>&nbsp;&nbsp;Implement the design
+    <a class="toc" id="usage.tutorial.implement-design" href="#a-606264088">4.9.6</a>&nbsp;&nbsp;Implement the design
   </h3>
   <div class="content"><p>Now that we have implemented and verified our prototype, we are ready to implement our design This is often quite simple because we translate <em>existing</em> code from Ruby (our prototype) into Verilog (our design). The result of this process is illustrated by <a class="xref" href="#fig:counter.v_impl">Example 13: <em>Implementation of a simple up-counter with synchronous reset</em></a>.</p>
 
 
 	<p><div class="example">
-  <p class="title"><a class="toc" id="fig:counter.v_impl" href="#a-606237758">Example 13</a>.&nbsp;&nbsp;Implementation of a simple up-counter with synchronous reset</p>
+  <p class="title"><a class="toc" id="fig:counter.v_impl" href="#a-606295138">Example 13</a>.&nbsp;&nbsp;Implementation of a simple up-counter with synchronous reset</p>
   <div class="content"><pre class="code" lang="verilog">/**
   A simple up-counter with synchronous reset.
 
@@ -3014,13 +3074,14 @@ module counter #(parameter Size = 5) (
     else
       count &lt;= count + 1;
   end
-endmodule</pre></div>
+endmodule
+</pre></div>
 </div>
 Before we continue, replace the contents of the files named <tt>RSpec/counter.v</tt> and <tt>xUnit/counter.v</tt> with the source code shown in <a class="xref" href="#fig:counter.v_impl">Example 13: <em>Implementation of a simple up-counter with synchronous reset</em></a></p></div>
 </div>
 <div class="section">
   <h3 class="title">
-    <a class="toc" id="usage.tutorial.test-design" href="#a-606269558">4.9.7</a>&nbsp;&nbsp;Verify the design
+    <a class="toc" id="usage.tutorial.test-design" href="#a-606356058">4.9.7</a>&nbsp;&nbsp;Verify the design
   </h3>
   <div class="content"><p>Now that we have implemented our design we are ready to verify it against our specification by running the test <a class="xref" href="#fig:test-design.RSpec">Example 14: <em>Running a test with specification in RSpec format</em></a> and <a class="xref" href="#fig:test-design.unit-test">Example 15: <em>Running a test with specification in xUnit format</em></a> illustrate this process.</p>
 
@@ -3029,7 +3090,7 @@ Before we continue, replace the contents of the files named <tt>RSpec/counter.v<
 
 
 	<p><div class="example">
-  <p class="title"><a class="toc" id="fig:test-design.RSpec" href="#a-606307738">Example 14</a>.&nbsp;&nbsp;Running a test with specification in RSpec format</p>
+  <p class="title"><a class="toc" id="fig:test-design.RSpec" href="#a-606419298">Example 14</a>.&nbsp;&nbsp;Running a test with specification in RSpec format</p>
   <div class="content"><pre>
 $ cd RSpec
 $ rake cver
@@ -3042,7 +3103,7 @@ Finished in 0.041198 seconds
 </pre></div>
 </div>
 <div class="example">
-  <p class="title"><a class="toc" id="fig:test-design.unit-test" href="#a-606325118">Example 15</a>.&nbsp;&nbsp;Running a test with specification in xUnit format</p>
+  <p class="title"><a class="toc" id="fig:test-design.unit-test" href="#a-606425048">Example 15</a>.&nbsp;&nbsp;Running a test with specification in xUnit format</p>
   <div class="content"><pre>
 $ cd xUnit
 $ rake cver
@@ -3058,7 +3119,7 @@ Finished in 0.040262 seconds.
 </div>
 <div class="section">
   <h3 class="title">
-    <a class="toc" id="usage.examples" href="#a-606358268">4.9.8</a>&nbsp;&nbsp;More examples
+    <a class="toc" id="usage.examples" href="#a-606447908">4.9.8</a>&nbsp;&nbsp;More examples
   </h3>
   <div class="content">The <tt>examples</tt> directory (<a href="http://ruby-vpi.rubyforge.org/src/examples/">browse it online</a>) contains several example tests which illustrate how Ruby-VPI can be used. Each example has an associated <tt>Rakefile</tt> which simplifies the process of running it. Therefore, simply navigate into an example directory and run the <pre>rake</pre> command to get started.</div>
 </div></p></div>
@@ -3067,7 +3128,7 @@ Finished in 0.040262 seconds.
 <div class="chapter">
   <h1 class="title">
     Chapter
-    <a class="toc" id="hacking" href="#a-606376468">5</a>
+    <a class="toc" id="hacking" href="#a-606474498">5</a>
 
     <br/>
 
@@ -3076,7 +3137,7 @@ Finished in 0.040262 seconds.
 
   <div class="content"><div class="section">
   <h2 class="title">
-    <a class="toc" id="hacking.build" href="#a-605850148">5.1</a>&nbsp;&nbsp;Building from source code
+    <a class="toc" id="hacking.build" href="#a-606497178">5.1</a>&nbsp;&nbsp;Building from source code
   </h2>
   <div class="content"><p>Obtain the source code from the project <a href="http://darcs.net">Darcs</a> repository:</p>
 
@@ -3091,7 +3152,7 @@ Finished in 0.040262 seconds.
 ruby bin/ruby-vpi -v</pre>
 
 
-	<p>If the commands were successful, then you will see output like this: <pre>ruby-vpi 20.0.0 (2008-01-27) http://ruby-vpi.rubyforge.org /home/sun/src/ruby-vpi
+	<p>If the commands were successful, then you will see output like this: <pre>ruby-vpi 21.0.0 (2008-06-08) http://ruby-vpi.rubyforge.org /home/sun/src/ruby-vpi
 </pre></p>
 
 
@@ -3099,7 +3160,7 @@ ruby bin/ruby-vpi -v</pre>
 </div>
 <div class="section">
   <h2 class="title">
-    <a class="toc" id="Installing-without-really-installing" href="#a-605974548">5.2</a>&nbsp;&nbsp;Installing without really installing
+    <a class="toc" id="Installing-without-really-installing" href="#a-606511708">5.2</a>&nbsp;&nbsp;Installing without really installing
   </h2>
   <div class="content"><p>After successfully building from source (see <a class="xref" href="#hacking.build">Section 5.1: <em>Building from source code</em></a>), set the <code class="code"><span style="color:#036; font-weight:bold">RUBYLIB</span></code> environment variable to the path where you checked out the source code <em>plus</em> the <tt>lib/</tt> directory.</p>
 
@@ -3108,7 +3169,7 @@ ruby bin/ruby-vpi -v</pre>
 </div>
 <div class="section">
   <h2 class="title">
-    <a class="toc" id="hacking.release-packages" href="#a-605757818">5.3</a>&nbsp;&nbsp;Building release packages
+    <a class="toc" id="hacking.release-packages" href="#a-606005938">5.3</a>&nbsp;&nbsp;Building release packages
   </h2>
   <div class="content"><p>In addition to the <a class="xref" href="#setup.reqs">normal requirements</a> you need the following software to build release packages:</p>
 
@@ -3139,7 +3200,7 @@ rake dist                  # Build release packages.
 rake doc                   # Build the documentation.
 rake doc/api/c             # Build API reference for C.
 rake doc/api/ruby          # Build the doc/api/ruby HTML Files
-rake gem                   # Build the gem file ruby-vpi-20.0.0.gem
+rake gem                   # Build the gem file ruby-vpi-21.0.0.gem
 rake gem_config_inst       # Configures the gem during installation.
 rake package               # Build all the packages
 rake redoc/api/ruby        # Force a rebuild of the RDOC files
@@ -3151,7 +3212,7 @@ rake upload                # Upload to project website.
 </div>
 <div class="section">
   <h2 class="title">
-    <a class="toc" id="hacking.guide" href="#a-607050138">5.4</a>&nbsp;&nbsp;Editing this guide
+    <a class="toc" id="hacking.guide" href="#a-606145488">5.4</a>&nbsp;&nbsp;Editing this guide
   </h2>
   <div class="content">The <tt>doc/guide.erb</tt> file contains the source code of this guide. You must install <a href="http://gerbil.rubyforge.org">Gerbil</a> before you can run the <pre>rake doc</pre> command to automatically generate the HTML documentation you are currently viewing.</div>
 </div></div>
@@ -3159,7 +3220,7 @@ rake upload                # Upload to project website.
 <div class="chapter">
   <h1 class="title">
     Chapter
-    <a class="toc" id="problems" href="#a-607052618">6</a>
+    <a class="toc" id="problems" href="#a-605970068">6</a>
 
     <br/>
 
@@ -3171,14 +3232,14 @@ rake upload                # Upload to project website.
 
 	<p><div class="section">
   <h2 class="title">
-    <a class="toc" id="problem.ivl" href="#a-607054268">6.1</a>&nbsp;&nbsp;Icarus Verilog
+    <a class="toc" id="problem.ivl" href="#a-607199668">6.1</a>&nbsp;&nbsp;Icarus Verilog
   </h2>
   <div class="content"><p>The following sections describe problems that occur when Icarus Verilog is used with Ruby-VPI.</p>
 
 
 	<p><div class="section">
   <h3 class="title">
-    <a class="toc" id="problems.ivl.vpi_handle_by_name.absolute-paths" href="#a-607055848">6.1.1</a>&nbsp;&nbsp;Give full paths to Verilog objects
+    <a class="toc" id="problems.ivl.vpi_handle_by_name.absolute-paths" href="#a-607201248">6.1.1</a>&nbsp;&nbsp;Give full paths to Verilog objects
   </h3>
   <div class="content"><p>In version 0.8 and snapshot 20061009 of Icarus Verilog, the <code class="code">vpi_handle_by_name</code> function requires an <em>absolute</em> path (including the name of the bench which instantiates the design) to a Verilog object. In addition, <code class="code">vpi_handle_by_name</code> always returns <code class="code"><span style="color:#038; font-weight:bold">nil</span></code> when its second parameter is specified.</p>
 
@@ -3187,7 +3248,7 @@ rake upload                # Upload to project website.
 
 
 	<p><div class="example">
-  <p class="title"><a class="toc" id="ex:TestFoo" href="#a-607058828">Example 16</a>.&nbsp;&nbsp;Part of a bench which instantiates a Verilog design</p>
+  <p class="title"><a class="toc" id="ex:TestFoo" href="#a-607204398">Example 16</a>.&nbsp;&nbsp;Part of a bench which instantiates a Verilog design</p>
   <div class="content"><pre class="code" lang="verilog">
 module TestFoo;
   reg clk_reg;
@@ -3198,7 +3259,7 @@ endmodule
 </div>
 <div class="section">
   <h3 class="title">
-    <a class="toc" id="problems.ivl.vpi_handle_by_name.connect-registers" href="#a-607061068">6.1.2</a>&nbsp;&nbsp;Registers must be connected
+    <a class="toc" id="problems.ivl.vpi_handle_by_name.connect-registers" href="#a-607206638">6.1.2</a>&nbsp;&nbsp;Registers must be connected
   </h3>
   <div class="content"><p>In version 0.8 of Icarus Verilog, if you want to access a register in a design, then it must be connected to something (either assigned to a wire or passed as a parameter to a module instantiation). Otherwise, you will get a <code class="code"><span style="color:#038; font-weight:bold">nil</span></code> value as the result of <code class="code">vpi_handle_by_name</code> method.</p>
 
@@ -3210,7 +3271,7 @@ endmodule
 
 
 	<p><div class="example">
-  <p class="title"><a class="toc" id="ex:TestFoo_bad" href="#a-607066798">Example 17</a>.&nbsp;&nbsp;Bad design with unconnected registers</p>
+  <p class="title"><a class="toc" id="ex:TestFoo_bad" href="#a-607212878">Example 17</a>.&nbsp;&nbsp;Bad design with unconnected registers</p>
   <div class="content"><p>Here the <code class="code">clk_reg</code> register is not connected to anything.</p>
 
 
@@ -3221,7 +3282,7 @@ endmodule
 </pre></div>
 </div>
 <div class="example">
-  <p class="title"><a class="toc" id="ex:TestFoo_fix" href="#a-607068638">Example 18</a>.&nbsp;&nbsp;Fixed design with wired registers</p>
+  <p class="title"><a class="toc" id="ex:TestFoo_fix" href="#a-607214718">Example 18</a>.&nbsp;&nbsp;Fixed design with wired registers</p>
   <div class="content"><p>Here the <code class="code">clk_reg</code> register is connected to the <code class="code">clk_wire</code> wire.</p>
 
 
@@ -3236,16 +3297,22 @@ endmodule
 </div>
 <div class="section">
   <h3 class="title">
-    <a class="toc" id="problems.ivl.vpi_reset" href="#a-607070908">6.1.3</a>&nbsp;&nbsp;VPI::reset
+    <a class="toc" id="problems.ivl.vpi_reset" href="#a-607216988">6.1.3</a>&nbsp;&nbsp;VPI::reset
   </h3>
   <div class="content">In version 0.8 of Icarus Verilog, the <code class="code">vpi_control(vpiReset)</code> VPI function causes an assertion to fail inside the simulator. As a result, the simulation terminates and a core dump is produced.</div>
 </div></p></div>
+</div>
+<div class="section">
+  <h2 class="title">
+    <a class="toc" id="problem.ncsim" href="#a-607219468">6.2</a>&nbsp;&nbsp;Cadence NC-Sim
+  </h2>
+  <div class="content"><strong>ncsim</strong> crashes with Ruby-VPI 21.0.0.  The problem is most likely an interaction issue with Ruby&#8217;s threads implementation because <strong>ncsim</strong> worked fine with a <a href="http://en.wikipedia.org/wiki/Pthreads" title="pthreads">POSIX threads</a> based implementation of Ruby-VPI (version 20.0.0).</div>
 </div></p></div>
 </div>
 <div class="chapter">
   <h1 class="title">
     Chapter
-    <a class="toc" id="glossary" href="#a-607073798">7</a>
+    <a class="toc" id="glossary" href="#a-607221888">7</a>
 
     <br/>
 
@@ -3254,37 +3321,37 @@ endmodule
 
   <div class="content"><div class="section">
   <h2 class="title">
-    <a class="toc" id="glossary.test" href="#a-607075458">7.1</a>&nbsp;&nbsp;Test
+    <a class="toc" id="glossary.test" href="#a-607223548">7.1</a>&nbsp;&nbsp;Test
   </h2>
   <div class="content">Something that checks if a <a class="xref" href="#glossary.design">design</a> satisfies a <a class="xref" href="#glossary.specification">specification</a></div>
 </div>
 <div class="section">
   <h2 class="title">
-    <a class="toc" id="glossary.design" href="#a-607080108">7.2</a>&nbsp;&nbsp;Design
+    <a class="toc" id="glossary.design" href="#a-607228538">7.2</a>&nbsp;&nbsp;Design
   </h2>
   <div class="content">A Verilog module that is verified against a <a class="xref" href="#glossary.specification">specification</a> in order to ensure correctness or soundness of its being. In other words, it is the thing being checked: does it work or not?</div>
 </div>
 <div class="section">
   <h2 class="title">
-    <a class="toc" id="glossary.specification" href="#a-607083458">7.3</a>&nbsp;&nbsp;Specification
+    <a class="toc" id="glossary.specification" href="#a-607232058">7.3</a>&nbsp;&nbsp;Specification
   </h2>
   <div class="content">A set of <a class="xref" href="#glossary.expectation">expectations</a> which define the desired behavior of a <a class="xref" href="#glossary.design">design</a> when it is subjected to certain stimulus.</div>
 </div>
 <div class="section">
   <h2 class="title">
-    <a class="toc" id="glossary.expectation" href="#a-607088168">7.4</a>&nbsp;&nbsp;Expectation
+    <a class="toc" id="glossary.expectation" href="#a-607237108">7.4</a>&nbsp;&nbsp;Expectation
   </h2>
   <div class="content">The desired response to some stimulus.</div>
 </div>
 <div class="section">
   <h2 class="title">
-    <a class="toc" id="glossary.handle" href="#a-607090238">7.5</a>&nbsp;&nbsp;Handle
+    <a class="toc" id="glossary.handle" href="#a-607239178">7.5</a>&nbsp;&nbsp;Handle
   </h2>
   <div class="content">A reference to an object inside the Verilog simulation. See <a class="xref" href="#vpi.handles">Section 4.3.1: <em>Handles</em></a> for usage instructions.</div>
 </div>
 <div class="section">
   <h2 class="title">
-    <a class="toc" id="glossary.rake" href="#a-607093668">7.6</a>&nbsp;&nbsp;Rake
+    <a class="toc" id="glossary.rake" href="#a-607242778">7.6</a>&nbsp;&nbsp;Rake
   </h2>
   <div class="content"><blockquote>
 		<p>Rake is a build tool, written in Ruby, using Ruby as a build language. Rake is similar to <strong>make</strong> in scope and purpose.</p>
@@ -3295,7 +3362,7 @@ endmodule
 </div>
 <div class="section">
   <h2 class="title">
-    <a class="toc" id="glossary.RSpec" href="#a-607095818">7.7</a>&nbsp;&nbsp;RSpec
+    <a class="toc" id="glossary.RSpec" href="#a-607244928">7.7</a>&nbsp;&nbsp;RSpec
   </h2>
   <div class="content"><p>The <a class="xref" href="#glossary.BDD">BDD</a> framework for Ruby.</p>
 
@@ -3304,7 +3371,7 @@ endmodule
 </div>
 <div class="section">
   <h2 class="title">
-    <a class="toc" id="glossary.TDD" href="#a-607099338">7.8</a>&nbsp;&nbsp;Test driven development
+    <a class="toc" id="glossary.TDD" href="#a-607248618">7.8</a>&nbsp;&nbsp;Test driven development
   </h2>
   <div class="content"><p>An <a href="http://agilemanifesto.org/">agile software development methodology</a> which emphasizes (1) testing functionality before implementing it and (2) refactoring.</p>
 
@@ -3313,7 +3380,7 @@ endmodule
 </div>
 <div class="section">
   <h2 class="title">
-    <a class="toc" id="glossary.BDD" href="#a-607101548">7.9</a>&nbsp;&nbsp;Behavior driven development
+    <a class="toc" id="glossary.BDD" href="#a-607250828">7.9</a>&nbsp;&nbsp;Behavior driven development
   </h2>
   <div class="content"><p>An <a href="http://agilemanifesto.org/">agile software development methodology</a> which emphasizes thinking in terms of behavior when designing, implementing, and verifying software.</p>
 
@@ -3330,7 +3397,7 @@ endmodule
     
     <div id="footer">
     
-      Generated on Sun Jan 27 22:46:48 -0800 2008 by <a href="http://gerbil.rubyforge.org">Gerbil</a> 1.1.0.
+      Generated on Sun Jun 08 15:55:46 -0700 2008 by <a href="http://gerbil.rubyforge.org">Gerbil</a> 3.0.2.
 
       <p>The admonition icons (<img src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAADAAAAAwCAYAAABXAvmHAAAABHNCSVQICAgI
 fAhkiAAAAAlwSFlzAAAN1wAADdcBQiibeAAAABl0RVh0U29mdHdhcmUAd3d3
@@ -3407,7 +3474,7 @@ ta22BwC4nZ2dXdu2bfujlpaWe4wxNDMz84OzZ88em5qamkZ9ppfjAflu+bDc
 HGAANv6XHFhk9iI4CwDNm5m3aJG9Ww4o1MPnXQVe09fovEsXBC+AXO16LBK/
 0BYggPpqs9jeBlvqCnTNAP/jIXWgBeNF/YXzBfHxIoC3z5cj+Or2X3r9Ye2F
 1izgAAAAAElFTkSuQmCC
-" alt="tip"/> <img src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAADAAAAAwCAYAAABXAvmHAAAABHNCSVQICAgI
+"/> <img src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAADAAAAAwCAYAAABXAvmHAAAABHNCSVQICAgI
 fAhkiAAAAAlwSFlzAAAN1wAADdcBQiibeAAAABl0RVh0U29mdHdhcmUAd3d3
 Lmlua3NjYXBlLm9yZ5vuPBoAAAmCSURBVGiB1ZltbJXlGcd/9/N+Tlssh1Ja
 hNEJaK2UFxFptqC2wGCSTWdM3DSQzWVDEzVxy4xfjNkHQ8xMnEEXviwZ62Rj
@@ -3464,7 +3531,7 @@ bj2VSjFnzpxrKjafSSm5cOEC/f39KUAnrVsTgAkUAYU1NTUPx2KxjUEQTLmW
 YvOZpmnxjo6O3x48eHA76S4UB3qEUgohRBQoGLoyKTJJp+nyR97kmA1IwANS
 wODQ1auUSmYP9UNjoQBwAIv0DBUMFb6WZpNuRB9wSYsfUEr5kOdfSiGETrr1
 DUCQhrhWJkj394A0gKeUCjVo3r9Zv0r2P3yyQqPd16MPAAAAAElFTkSuQmCC
-" alt="note"/> <img src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAADAAAAAwCAYAAABXAvmHAAAABHNCSVQICAgI
+"/> <img src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAADAAAAAwCAYAAABXAvmHAAAABHNCSVQICAgI
 fAhkiAAAAAlwSFlzAAAN1wAADdcBQiibeAAAABl0RVh0U29mdHdhcmUAd3d3
 Lmlua3NjYXBlLm9yZ5vuPBoAAAiESURBVGiB7ZpdbBzVFcd/Z2Znd2d3vbtm
 /RWvsbEdfyauSWzq2MZWEFVD5AqBaBpRVyaKoaakEBMEBRRVBaukKiqhQF+i
@@ -3516,7 +3583,7 @@ lQP3aeBFBNHmWbBT/aV/Wn8qvh+F0Uuw73noCsEocEkpFUwKABARJ+CKFwex
 MFmBqURf37Fpcf9hIAgEgHFgDBhLzIHkJFZKjYuIAiJACJiIH79ZAhKXdSTO
 ECQGPj690VUrcfw2ZYuXhICbYRZiUUhEYFLNkjYs6s3c/5J97/9q8F/RUcwR
 4xicOQAAAABJRU5ErkJggg==
-" alt="caution"/>) used in this document are Copyright &copy; 2005 <a href="http://tango.freedesktop.org">Tango Desktop Project</a>. They are part of the <a href="http://tango.freedesktop.org/Tango_Icon_Library">Tango Icon Theme</a> set, which is distributed under the <a href="http://creativecommons.org/licenses/by-sa/2.5/">Creative Commons Attribution-ShareAlike 2.5 License Agreement</a>.</p>
+"/>) used in this document are Copyright &copy; 2005 <a href="http://tango.freedesktop.org">Tango Desktop Project</a>. They are part of the <a href="http://tango.freedesktop.org/Tango_Icon_Library">Tango Icon Theme</a> set, which is distributed under the <a href="http://creativecommons.org/licenses/by-sa/2.5/">Creative Commons Attribution-ShareAlike 2.5 License Agreement</a>.</p>
     
     </div>