Calvin Wong wrote: > I know this is going to be a lot to ask, but have you thought > about creating a threading methodology for synchronizing two > ruby processes.
Ah yes, Rob MacAulay also asked about this feature recently. I'll need to get your example to work first before identifying what can be encapsulated. So give me some time to hack on this and I'll get back to you. > Using the ruby threads mechanism and encapsulating > those two inital blocks on separate threads doesn't work > because the ruby threads have a different context switch > mechanism. Correct. The easiest approach I can think of is to use cbValueChange callbacks and let the simulator do the hard work of detecting when signals change. However, this approach won't work when prototyping is enabled, because in that mode, we never give control back to the Verilog simulator. I'll need to think about this some more.
