vpi_interator API needs to allow the full range of object types, not just vpiNet

[GordonMcGregor]

One of the most useful features of pyHVL in large ASIC projects has been the simple access to the VPI iterators/ scan API.

For this to be useful though, it has to be more flexible than just vpiNet (e.g, vpiModule to walk the design hierarchy)

Ideally the full set of VPI constants would be accessible from Python and could be passed through the iterate_signals call (or probably a more generic 'iterate' API if you want to keep iterate_signals specific to vpiNets

PyHVL actually generated the defines dynamically by parsing the vpi_user.h - I could port that code over. It then populated the Python namespace with those vpi defines.

[GordonMcGregor]

Issue #17 this issue and #41 are all related. The pull request with the vpi defines in the simulator module dictionary can help with this too. (branch/ pull request traverse_nets )

[chiggs]

This will be implemented by issue #17 so closing.