[Stackless] unexpected tasklet & channel behaviour
ardatur at mail.ru
Thu Nov 2 08:02:15 CET 2006
Wednesday, November 1, 2006, 1:01:19 PM, you wrote:
RT> There is a logic to this behaviour.
RT> The interpreter internals, but only for executing that expression. But
RT> what if the blocking on the receive is soft switching? That receive
RT> is effectively finished and the tasklet is blocked only waiting for
RT> something to send it a return value, but the stack unwinds and all
RT> now unused objects like the channel are freed as nothing really holds
RT> a reference to them.
Ah, that explains the last bit. I actually thought of blocking as of
something happening _inside_ the receive() call, thus the confusion.
Stackless mailing list
Stackless at stackless.com
More information about the Stackless