ruby-vpi 11.0.0 → 11.1.0

data/memo.html

@@ -35,107 +35,97 @@
 <dt>
 <span class="term">
 <a href="http://rubyforge.org/projects/ruby-vpi" target="_top">
-Project</a>
+Facilities</a>
 </span>
 </dt>
 <dd>
 <p>
-Access project facilities, hosted generously by <a href="http://rubyforge.org" target="_top">
+Access the issue tracker, file downloads, support requests, discussion forums, and more at <a href="http://rubyforge.org" target="_top">
 RubyForge</a>.
 </p>
 </dd>
 
 <dt>
 <span class="term">
-<a href="http://rubyforge.org/tracker/?group_id=1339" target="_top">
-Tracker</a>
+<a href="http://ruby-vpi.rubyforge.org" target="_top">
+Project</a>
 </span>
 </dt>
 <dd>
 <p>
-Report problems, contribute patches, and more.</p>
+Access more information at the project&#8217;s home page.
+</p>
 </dd>
 
 <dt>
 <span class="term">
-<a href="http://rubyforge.org/frs/?group_id=1339" target="_top">
-Releases</a>
+<a href="http://ruby-vpi.rubyforge.org/src/ruby-vpi" target="_top">
+Sources</a>
 </span>
 </dt>
 <dd>
 <p>
-Download the newest releases.</p>
+Browse or access the source code repository.</p>
 </dd>
 
 <dt>
 <span class="term">
-<a href="http://ruby-vpi.rubyforge.org/src/ruby-vpi" target="_top">
-Sources</a>
+<a href="http://ruby-vpi.rubyforge.org/talks" target="_top">
+Talks</a>
 </span>
 </dt>
 <dd>
 <p>
-Browse or access the source code repository.</p>
+Access public presentations about Ruby-VPI.</p>
 </dd>
 
 <dt>
 <span class="term">
-<a href="http://rubyforge.org/forum/?group_id=1339" target="_top">
-Forums</a>
+<a href="http://ruby-vpi.rubyforge.org/blog" target="_top">
+News</a>
 </span>
 </dt>
 <dd>
 <p>
-Ask for help, give feedback, or discuss.</p>
+See what the developers are cooking up.</p>
 </dd>
 
 </dl>
 </div>
 </div>
 
-	<h1>Notes</h1>
-
-
-	<ul>
-	<li>When within Rake, rubygems is automatically available for use. no need to require() it again</li>
-	</ul>
-
-
 	<h1>Pending tasks</h1>
 
 
 	<ul>
-	<li>interactive console <span class="caps">IRB</span> wrapper for spec (just like Breakpoints in Rails)</li>
+	<li>add support for reading &#38; writing <span class="caps">VPI</span> delay values</li>
 	</ul>
 
 
 	<ul>
-	<li>add support for reading &#38; writing vpi_delay values</li>
+	<li><span class="caps">GHDL</span> simulator supports <span class="caps">VPI</span>
+	<ul>
+	<li>need way to invoke <span class="caps">VPI</span> tasks from <span class="caps">VHDL</span>, like <code>$ruby_init();</code></li>
+	</ul></li>
 	</ul>
 
 
 	<ul>
-	<li>define handled methods in Vpi::method_missing for faster response
+	<li>need to dump signal values when expectation fails in rSpec
 	<ul>
-	<li>this has been verified as bottleneck from profiling data</li>
+	<li>maybe a waveform dump will also help</li>
+		<li>this will help in debugging the problem</li>
 	</ul></li>
 	</ul>
 
 
 	<ul>
-	<li><span class="caps">GHDL</span> simulator supports <span class="caps">VPI</span>
-	<ul>
-	<li>need way to invoke <span class="caps">VPI</span> tasks from <span class="caps">VHDL</span>, like <code>$ruby_init();</code></li>
-	</ul></li>
+	<li>add instructions for using <strong>ruby-debug</strong> with a graphical debugging tool or <span class="caps">IDE</span> like RadRails</li>
 	</ul>
 
 
 	<ul>
-	<li>need to dump signal values when expectation fails in rSpec
-	<ul>
-	<li>maybe a waveform dump will also help</li>
-		<li>this will help in debugging the problem</li>
-	</ul></li>
+	<li>make RCov correctly profile the code and report useful coverage metrics&#8230;</li>
 	</ul>
 
 
@@ -189,17 +179,33 @@ Ask for help, give feedback, or discuss.</p>
 	</ul>
 
 
+	<ul>
+	<li>define handled methods in Vpi::method_missing for faster response
+	<ul>
+	<li>this has been verified as bottleneck from profiling data</li>
+	</ul></li>
+	</ul>
+
+
 	<h1>Obsolete tasks</h1>
 
 
 	<ul>
-	<li>file bug report for Icarus 0.8 (l0_dcache)
+	<li>smarter test generation, which adjusts to user modifications in previously generated output&#8212;just use a smart merging tool like <strong>kdiff3</strong></li>
+	</ul>
+
+
 	<ul>
-	<li>try new icarus snapshot</li>
+	<li>interactive console <span class="caps">IRB</span> wrapper for spec (just like Breakpoints in Rails)
+	<ul>
+	<li>use the <strong>ruby-debug</strong> library with <a href="http://www.datanoise.com/articles/category/ruby-debug"><strong>debugger</strong> command for breakpoints</a> instead!</li>
 	</ul></li>
 	</ul>
 
 
+	<h1>Notes</h1>
+
+
 	<ul>
-	<li>smarter test generation, which adjusts to user modifications in previously generated output&#8212;just use a smart merging tool like <strong>kdiff3</strong></li>
+	<li>When within Rake, rubygems is automatically available for use. no need to require() it again</li>
 	</ul>

data/memo.part.html

@@ -1,46 +1,35 @@
-<h1>Notes</h1>
+<h1>Pending tasks</h1>
 
 
 	<ul>
-	<li>When within Rake, rubygems is automatically available for use. no need to require() it again</li>
+	<li>add support for reading &#38; writing <span class="caps">VPI</span> delay values</li>
 	</ul>
 
 
-	<h1>Pending tasks</h1>
-
-
 	<ul>
-	<li>interactive console <span class="caps">IRB</span> wrapper for spec (just like Breakpoints in Rails)</li>
-	</ul>
-
-
+	<li><span class="caps">GHDL</span> simulator supports <span class="caps">VPI</span>
 	<ul>
-	<li>add support for reading &#38; writing vpi_delay values</li>
+	<li>need way to invoke <span class="caps">VPI</span> tasks from <span class="caps">VHDL</span>, like <code>$ruby_init();</code></li>
+	</ul></li>
 	</ul>
 
 
 	<ul>
-	<li>define handled methods in Vpi::method_missing for faster response
+	<li>need to dump signal values when expectation fails in rSpec
 	<ul>
-	<li>this has been verified as bottleneck from profiling data</li>
+	<li>maybe a waveform dump will also help</li>
+		<li>this will help in debugging the problem</li>
 	</ul></li>
 	</ul>
 
 
 	<ul>
-	<li><span class="caps">GHDL</span> simulator supports <span class="caps">VPI</span>
-	<ul>
-	<li>need way to invoke <span class="caps">VPI</span> tasks from <span class="caps">VHDL</span>, like <code>$ruby_init();</code></li>
-	</ul></li>
+	<li>add instructions for using <strong>ruby-debug</strong> with a graphical debugging tool or <span class="caps">IDE</span> like RadRails</li>
 	</ul>
 
 
 	<ul>
-	<li>need to dump signal values when expectation fails in rSpec
-	<ul>
-	<li>maybe a waveform dump will also help</li>
-		<li>this will help in debugging the problem</li>
-	</ul></li>
+	<li>make RCov correctly profile the code and report useful coverage metrics&#8230;</li>
 	</ul>
 
 
@@ -94,17 +83,33 @@
 	</ul>
 
 
+	<ul>
+	<li>define handled methods in Vpi::method_missing for faster response
+	<ul>
+	<li>this has been verified as bottleneck from profiling data</li>
+	</ul></li>
+	</ul>
+
+
 	<h1>Obsolete tasks</h1>
 
 
 	<ul>
-	<li>file bug report for Icarus 0.8 (l0_dcache)
+	<li>smarter test generation, which adjusts to user modifications in previously generated output&#8212;just use a smart merging tool like <strong>kdiff3</strong></li>
+	</ul>
+
+
+	<ul>
+	<li>interactive console <span class="caps">IRB</span> wrapper for spec (just like Breakpoints in Rails)
 	<ul>
-	<li>try new icarus snapshot</li>
+	<li>use the <strong>ruby-debug</strong> library with <a href="http://www.datanoise.com/articles/category/ruby-debug"><strong>debugger</strong> command for breakpoints</a> instead!</li>
 	</ul></li>
 	</ul>
 
 
+	<h1>Notes</h1>
+
+
 	<ul>
-	<li>smarter test generation, which adjusts to user modifications in previously generated output&#8212;just use a smart merging tool like <strong>kdiff3</strong></li>
+	<li>When within Rake, rubygems is automatically available for use. no need to require() it again</li>
 	</ul>

data/readme.html

@@ -35,58 +35,59 @@
 <dt>
 <span class="term">
 <a href="http://rubyforge.org/projects/ruby-vpi" target="_top">
-Project</a>
+Facilities</a>
 </span>
 </dt>
 <dd>
 <p>
-Access project facilities, hosted generously by <a href="http://rubyforge.org" target="_top">
+Access the issue tracker, file downloads, support requests, discussion forums, and more at <a href="http://rubyforge.org" target="_top">
 RubyForge</a>.
 </p>
 </dd>
 
 <dt>
 <span class="term">
-<a href="http://rubyforge.org/tracker/?group_id=1339" target="_top">
-Tracker</a>
+<a href="http://ruby-vpi.rubyforge.org" target="_top">
+Project</a>
 </span>
 </dt>
 <dd>
 <p>
-Report problems, contribute patches, and more.</p>
+Access more information at the project&#8217;s home page.
+</p>
 </dd>
 
 <dt>
 <span class="term">
-<a href="http://rubyforge.org/frs/?group_id=1339" target="_top">
-Releases</a>
+<a href="http://ruby-vpi.rubyforge.org/src/ruby-vpi" target="_top">
+Sources</a>
 </span>
 </dt>
 <dd>
 <p>
-Download the newest releases.</p>
+Browse or access the source code repository.</p>
 </dd>
 
 <dt>
 <span class="term">
-<a href="http://ruby-vpi.rubyforge.org/src/ruby-vpi" target="_top">
-Sources</a>
+<a href="http://ruby-vpi.rubyforge.org/talks" target="_top">
+Talks</a>
 </span>
 </dt>
 <dd>
 <p>
-Browse or access the source code repository.</p>
+Access public presentations about Ruby-VPI.</p>
 </dd>
 
 <dt>
 <span class="term">
-<a href="http://rubyforge.org/forum/?group_id=1339" target="_top">
-Forums</a>
+<a href="http://ruby-vpi.rubyforge.org/blog" target="_top">
+News</a>
 </span>
 </dt>
 <dd>
 <p>
-Ask for help, give feedback, or discuss.</p>
+See what the developers are cooking up.</p>
 </dd>
 
 </dl>
@@ -124,12 +125,7 @@ Ask for help, give feedback, or discuss.</p>
 	</ul>
 
 
-	<h1>Getting started</h1>
-
-
-	<ul>
-	<li>See the <a href="./doc">user manual</a> to begin using Ruby-VPI.</li>
-	</ul>
+	<h1>Release notes</h1>
 
 
 	<ul>
@@ -138,31 +134,5 @@ Ask for help, give feedback, or discuss.</p>
 
 
 	<ul>
-	<li>See <span class="caps">API</span> documentation for the <a href="./ref/c">C extension</a> or <a href="./ref/ruby">Ruby-VPI libraries</a>.</li>
+	<li>See the <a href="./memo.html">project memo</a> for a list of pending tasks.</li>
 	</ul>
-
-
-	<ul>
-	<li>Visit the <a href="http://ruby-vpi.rubyforge.org">project website</a> for additional resources.</li>
-	</ul>
-
-
-	<h1>Building release packages</h1>
-
-
-	<p>In addition to the <a href="./doc/usage.requirements.html">normal requirements</a>, you need the following software to build release packages:</p>
-
-
-	<ul>
-	<li><a href="http://www.docbook.org/">DocBook-XML</a>
-	<ul>
-	<li>xsltproc</li>
-		<li>xmlto</li>
-	</ul>
-	</li>
-		<li><a href="http://rubyforge.org/projects/redcloth/">RedCloth</a></li>
-		<li><a href="http://www.swig.org/"><span class="caps">SWIG</span></a></li>
-	</ul>
-
-
-	<p>Once you have satisfied these requirements, you can run <code>rake release</code> to build the release packages. Also, see the output of <code>rake -T</code> for more build options.</p>

data/readme.part.html

@@ -29,12 +29,7 @@
 	</ul>
 
 
-	<h1>Getting started</h1>
-
-
-	<ul>
-	<li>See the <a href="./doc">user manual</a> to begin using Ruby-VPI.</li>
-	</ul>
+	<h1>Release notes</h1>
 
 
 	<ul>
@@ -43,31 +38,5 @@
 
 
 	<ul>
-	<li>See <span class="caps">API</span> documentation for the <a href="./ref/c">C extension</a> or <a href="./ref/ruby">Ruby-VPI libraries</a>.</li>
-	</ul>
-
-
-	<ul>
-	<li>Visit the <a href="http://ruby-vpi.rubyforge.org">project website</a> for additional resources.</li>
-	</ul>
-
-
-	<h1>Building release packages</h1>
-
-
-	<p>In addition to the <a href="./doc/usage.requirements.html">normal requirements</a>, you need the following software to build release packages:</p>
-
-
-	<ul>
-	<li><a href="http://www.docbook.org/">DocBook-XML</a>
-	<ul>
-	<li>xsltproc</li>
-		<li>xmlto</li>
-	</ul>
-	</li>
-		<li><a href="http://rubyforge.org/projects/redcloth/">RedCloth</a></li>
-		<li><a href="http://www.swig.org/"><span class="caps">SWIG</span></a></li>
+	<li>See the <a href="./memo.html">project memo</a> for a list of pending tasks.</li>
 	</ul>
-
-
-	<p>Once you have satisfied these requirements, you can run <code>rake release</code> to build the release packages. Also, see the output of <code>rake -T</code> for more build options.</p>

data/ref/c/annotated.html

@@ -0,0 +1,40 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html><head><meta http-equiv="Content-Type" content="text/html;charset=iso-8859-1">
+<title>Ruby-VPI: Data Structures</title>
+<link href="doxygen.css" rel="stylesheet" type="text/css">
+<link href="tabs.css" rel="stylesheet" type="text/css">
+</head><body>
+<!-- Generated by Doxygen 1.4.7 -->
+<div class="tabs">
+  <ul>
+    <li><a href="index.html"><span>Main&nbsp;Page</span></a></li>
+    <li id="current"><a href="annotated.html"><span>Data&nbsp;Structures</span></a></li>
+    <li><a href="files.html"><span>Files</span></a></li>
+  </ul></div>
+<div class="tabs">
+  <ul>
+    <li id="current"><a href="annotated.html"><span>Data&nbsp;Structures</span></a></li>
+    <li><a href="functions.html"><span>Data&nbsp;Fields</span></a></li>
+  </ul></div>
+<h1>Ruby-VPI Data Structures</h1>Here are the data structures with brief descriptions:<table>
+  <tr><td class="indexkey"><a class="el" href="structrelay____RubyOptions____def.html">relay__RubyOptions__def</a></td><td class="indexvalue"></td></tr>
+  <tr><td class="indexkey"><a class="el" href="unions__vpi__value__value.html">s_vpi_value_value</a></td><td class="indexvalue"></td></tr>
+  <tr><td class="indexkey"><a class="el" href="structswig__cast__info.html">swig_cast_info</a></td><td class="indexvalue"></td></tr>
+  <tr><td class="indexkey"><a class="el" href="structswig__class.html">swig_class</a></td><td class="indexvalue"></td></tr>
+  <tr><td class="indexkey"><a class="el" href="structswig__module__info.html">swig_module_info</a></td><td class="indexvalue"></td></tr>
+  <tr><td class="indexkey"><a class="el" href="structswig__type__info.html">swig_type_info</a></td><td class="indexvalue"></td></tr>
+  <tr><td class="indexkey"><a class="el" href="structt__cb__data.html">t_cb_data</a></td><td class="indexvalue"></td></tr>
+  <tr><td class="indexkey"><a class="el" href="structt__vpi__delay.html">t_vpi_delay</a></td><td class="indexvalue"></td></tr>
+  <tr><td class="indexkey"><a class="el" href="structt__vpi__error__info.html">t_vpi_error_info</a></td><td class="indexvalue"></td></tr>
+  <tr><td class="indexkey"><a class="el" href="structt__vpi__strengthval.html">t_vpi_strengthval</a></td><td class="indexvalue"></td></tr>
+  <tr><td class="indexkey"><a class="el" href="structt__vpi__systf__data.html">t_vpi_systf_data</a></td><td class="indexvalue"></td></tr>
+  <tr><td class="indexkey"><a class="el" href="structt__vpi__time.html">t_vpi_time</a></td><td class="indexvalue"></td></tr>
+  <tr><td class="indexkey"><a class="el" href="structt__vpi__value.html">t_vpi_value</a></td><td class="indexvalue"></td></tr>
+  <tr><td class="indexkey"><a class="el" href="structt__vpi__vecval.html">t_vpi_vecval</a></td><td class="indexvalue"></td></tr>
+  <tr><td class="indexkey"><a class="el" href="structt__vpi__vlog__info.html">t_vpi_vlog_info</a></td><td class="indexvalue"></td></tr>
+</table>
+<hr size="1"><address style="align: right;"><small>Generated on Wed Nov 8 19:07:51 2006 for Ruby-VPI by&nbsp;
+<a href="http://www.doxygen.org/index.html">
+<img src="doxygen.png" alt="doxygen" align="middle" border="0"></a> 1.4.7 </small></address>
+</body>
+</html>