streamline io check by using isIo instead of isModuleIo which was redundant
Fixed Verilog ROM generation. Issue was when ROM values were declared outside the ROM, the backend used a default name instead of the actual value.
Uniquify names on a per-module basis

Name mangling resulted in occasional collisions, e.g. foo.bar would become
foo_bar, which could conflict with a node truly named foo_bar.
add new tester with peek and poke
change to testy name
Merge pull request #139 from ucb-bar/is-io-check

streamline io check by using isIo instead of isModuleIo which was redund...
Merge pull request #140 from ucb-bar/new-tester

New tester
improve testy to wait for processIO and add more to testy docs
fix two regression tests caused by recent changes to debug_nodes
one more fix
change ConnectTest output location
varName now from markComponent in Module, no longer from setVarName in Backend (#73)
fix #119
fix #119
Don't "return 0" in a void function

This was causing my compile to fail, so I just blew away the return
value.  Hopefully that's a sane thing to do...
merge
change name back to Tester
change Tester21 MapTester
update docs to 2.2.0
new for 2.2.0