Content deleted Content added
→Trimming: re |
No edit summary |
||
Line 19:
The feature did sound like something to include, the only thing is that this information needs to be put in a context so that the user of the article understands what that means to a certain level, and there is very little to be understood by the statement that it is "temporal recursion". Now it can be linked to Clojure, and that brings the capabilities of the subject into a proper context. One question, how is it that this framework uses triggers that equivalent packages don't? - [[User:Frankie|frankie]] ([[User talk:Frankie|talk]]) 18:50, 5 June 2011 (UTC)
: I think most music programming languages have some form of scheduling like this. From what I recall, in ChucK one can schedule the rest/continuation of a "shard" (thread) to resume after a some time by chucking some interval into the predefined variable "now". Many threading libraries and OS kernels have something similar, except for the syntactic sugar: you put the thread/LWP/process in a queue to be activated on some event, and then call something like yield()/schedule() to relinquish the CPU. This so called "temporal recursion" seems to be just a pause by a specified amount, which yields the CPU and schedules a continuation that just does a normal [[tail call]]. [[User:FuFoFuEd|FuFoFuEd]] ([[User talk:FuFoFuEd|talk]]) 20:21, 5 June 2011 (UTC)
| |||