Re: i'm going crazy with task

[Adrien Plisson <aplisson-news@stochastique.net>]

Dennis Lee Bieber wrote:
> 	Such should only require some data structure for the event
> timing, and the externally created process to be started (path to a
> script file, perhaps). But the original question seemed to be assuming
> diverse internally coded processes... Okay, I suppose timed one-shots
> could still be applied to internal code modules -- and those could be
> (very rough description here) handled as a sort of call-back from the
> timer to plain procedures.

i was only making suppositions on what the OP was trying to do, i don't speak 
on behalf of him. so, until he posts some more informations, we can't assume 
anything on what he is trying to do. i only raised the point about the 
scheduler because the term is confusing.

you are right pointing out that a "task scheduler" should not need that much 
tasks, but you forgot a case which forces the use of tasks. consider that 
actions of the scheduler are internal procedures. if you implement it with 
callbacks, the scheduler will block until the actions terminates. if actions 
are lengthy, you have a problem. the solution is from the scheduler to create a 
new task which will call the procedure.

anyway, even when doing this there is no need for a big array of tasks...

-- 
rien