Calvin Wong wrote: > This test program introduces another scheme to handle multiple > atPosEdge/atNegEdge/wait routines in multiple threads using > cbValueChange callbacks for edge triggering and cbAfterDelay for > fixed wait times.
IMHO this example is reinventing the wheel by diving too deeply into the project internals. I know the current Handle#posedge? and Handle#negedge? methods aren't very precise (they check the current value when invoked) but that can be fixed. So I am wondering, is there any particular reason, other than increased accuracy of value change / edge detection, for reimplementing the entire threading model in this example?
