Would be nice if Clock() type exposed 'clock ticks' to 'simulation ticks' ratio.

[NickShaffner]

This would be particularly useful for being able to delay a certain number of clock ticks. Adding a delay() generator method to the clock type would be another means of exposing this.

ex:

something.next = False
yield glbl.clock.delay(1)
something.next = True

[cfelton]

@NickShaffner this sounds reasonable, my gut says a slightly different name: wait or pause possibly, mainly to avoid confusion with myhdl.delay.

[NickShaffner]

@cfelton I can see that - wait() would work for me. Also about the clock ticks to simulation ticks constant - how about 'ticks'? (since _hticks is used as half ticks in the clock already).

[NickShaffner]

#40 has Clock.ticks and Clock.delay. @cfelton - it made sense to me to use delay() instead of wait() in the end because it's really doing exactly the same thing as delay() does for the simulation clock. In fact, it might be cool if the simulation clock was somehow exposed as a Clock() object. (but that's the subject for another pull request :))

[NickShaffner]

Added in: #40