memo.doc in ruby-vpi-15.0.1

- old
+ new

@@ -1,13 +1,14 @@
 h1. Pending tasks
 
-* add support for reading & writing VPI delay values
+* add shortcuts for reading & writing VPI delay values
 
 * GHDL simulator supports VPI
-** -need way to invoke VPI tasks from VHDL, like @$ruby_init();@-
-No need for tasks; Ruby-VPI uses callbacks now!
+** need way to invoke VPI tasks from VHDL, like @$ruby_init();@
 
+  +No need for system tasks/functions. Ruby-VPI uses callbacks now!+
+
 * add instructions for using *ruby-debug* with a graphical debugging tool or IDE like RadRails
 
 * write section about code coverage and prototyping in manual
 
 * clean up the teriminology section... unnecessary
@@ -42,14 +43,19 @@
 * add support for VPI callbacks which execute Ruby blocks
 
 
 h1. Obsolete tasks
 
-* -smarter test generation, which adjusts to user modifications in previously generated output-
-Just use a smart merging tool like *kdiff3*.
+* smarter test generation, which adjusts to user modifications in previously generated output
 
-* -interactive console IRB wrapper for spec (just like Breakpoints in Rails)- Use the *ruby-debug* library with "*debugger* command for breakpoints":http://www.datanoise.com/articles/category/ruby-debug instead!
+  +Just use a smart merging tool like *kdiff3*.+
 
-* -need to dump signal values when expectation fails in rSpec-
-You can use the interactive debugger instead.
-** -maybe a waveform dump will also help-
-After reading some RTL verification books, this is not necessarily true.
+* interactive console IRB wrapper for spec (just like Breakpoints in Rails)
+
+  +Use the *ruby-debug* library with "*debugger* command for breakpoints":http://www.datanoise.com/articles/category/ruby-debug instead!+
+
+* need to dump signal values when expectation fails in rSpec
+
+  +You can use the interactive debugger instead.+
+** maybe a waveform dump will also help
+
+  +After reading some RTL verification books, this is not necessarily true.+