[PD-dev] timing of a clock_delay(x->x_clock, 0);

[Miller Puckette]

It's indeed "as soon as possible", except that if someone else has previously
scheduled something ASAP that ASAP will get in earlier than yours.  You
can chain arbitrarily many clock_delay(..., 0) calls without DSP or event
polling getting in between.

cheers
Miller

On Thu, Dec 28, 2006 at 11:05:36PM -0500, Hans-Christoph Steiner wrote:
> 
> If I issue a clock_delay(x->x_clock, 0), will the registered tick  
> function be executed in the same clock tick, or will it always wait  
> for the next clock tick?
> 
> Basically, I am looking for a way to schedule something "as soon as  
> possible".
> 
> .hc
> 
> ------------------------------------------------------------------------
> 
> Man has survived hitherto because he was too ignorant to know how to  
> realize his wishes.  Now that he can realize them, he must either  
> change them, or perish.    -William Carlos Williams
> 
> 
> 
> _______________________________________________
> PD-dev mailing list
> PD-dev at iem.at
> http://lists.puredata.info/listinfo/pd-dev