[Stackless] Stackless API (Custom Scheduling)
tismer at stackless.com
Thu Jan 29 20:21:32 CET 2004
Bob Ippolito wrote:
[not commenting on the general ideas until I have understood them all]
>> Once this, and the scheduler are in place, I feel methods like capture()
>> and become() should be removed. These methods scare me :) They look like
>> they exist to expose cool things you can do as a result of the current
>> implementation strategy, but are semantically hair-raising.
> All I know is that they make the interpreter misbehave, I have no idea
> what use they have either :)
They were an initial idea from CCPgames developers.
This was during my stay in Reykjavík, where we were
developing wild things, in summer 2002...
...the idea came out of some laziness when setting up
some code, which at some point decides it would be better
to continue as a tasklet.
This can of course be replaced by writing an extra function
and running a new tasklet with that function.
It was just handy to have, as we tried to figure
out how to use Stackless. :-)
Code of the form "hmm, do we need to run in an extra task, here?
Let's stick a become() into this to check it out".
Handy, but maybe better to drop?
I think I would follow a vote in this case,
especially since Kristján V. Jónsson is on this list,
representing CCPgames. He can tell whether they still need it.
ciao - chris
Christian Tismer :^) <mailto:tismer at stackless.com>
Mission Impossible 5oftware : Have a break! Take a ride on Python's
Johannes-Niemeyer-Weg 9a : *Starship* http://starship.python.net/
14109 Berlin : PGP key -> http://wwwkeys.pgp.net/
work +49 30 89 09 53 34 home +49 30 802 86 56 mobile +49 173 24 18 776
PGP 0x57F3BF04 9064 F4E1 D754 C2FF 1619 305B C09C 5A3B 57F3 BF04
whom do you want to sponsor today? http://www.stackless.com/
Stackless mailing list
Stackless at stackless.com
More information about the Stackless