[Stackless] Re: [Python-Dev] Stackless Design Q.
Gordon McMillan
gmcm@hypernet.com
Wed, 20 Feb 2002 21:00:50 -0500
Wed, 20 Feb 2002 21:00:50 -0500
- Previous message: [Stackless] Re: [Python-Dev] Stackless Design Q.
- Next message: [Stackless] Re: [Python-Dev] Stackless Design Q.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 20 Feb 2002 at 16:01, Greg Ewing wrote: [Christian's plea] > It seems to me you need only two things: > > (1) A constructor for new tasklets: > > t = tasklet(f) [snip] > (2) A way of switching to another tasklet: > > t.transfer() [snip] > All the other stuff you talk about -- passing > values between tasklets, rings of runnable tasklets, > scheduling policies, etc -- can all be implemented > in Python on top of these primitives. Unless you've got a way to detect or pass tasklet's through transfer, you don't have enough. -- Gordon http://www.mcmillan-inc.com/
- Previous message: [Stackless] Re: [Python-Dev] Stackless Design Q.
- Next message: [Stackless] Re: [Python-Dev] Stackless Design Q.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]