[Stackless] Make the Stackless Scheduler Your Friend Re: Realistic ticking and acting

[Richard Tew]

On 7/14/06, stackless at kaishaku.org <stackless at kaishaku.org> wrote:
> Like generators, I want the sub-routine/tasklet to execute *some*
> (ie. one "iteration") then return control to the caller. In tasklets
> the "iteration" is defined by channels, in generators by yield.

This is not possible without micromanaging the tasklets and
the scheduler.

I was looking for the ability to do this myself the other day, while
looking into a bug.  Since I needed to have the main tasklet raise
an exception on another tasklet, then return to itself, avoiding
running any other tasklets following the raised-on one before
getting back to itself.  I can do this at a C level in Stackless by
moving the main tasklet after the one I want to raise the exception
on and then running the non-main one, but it is still unreliable.

I think that this would make a useful addition to Stackless, but
given that Stackless is so oriented around the scheduler I
am not sure how easy it would be.

Richard.

_______________________________________________
Stackless mailing list
Stackless at stackless.com
http://www.stackless.com/mailman/listinfo/stackless