[pypy-dev] coroutine problem

Christian Tismer tismer at stackless.com
Tue Feb 14 19:54:10 CET 2006


Armin Rigo wrote:

> This is wrong.  The only two ways in which a stack switch occurs in
> RPython is by calling a switch() method explicitly, or by returning
> a frame object from a function that itself contained a call to
> yield_current_frame_to_caller(), like def _bind().

I think you are right. The exception is happening in another
place, my logic of kill() was imperfect.

ciao & thanks - chris

-- 
Christian Tismer             :^)   <mailto:tismer at stackless.com>
tismerysoft GmbH             :     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 802 86 56  mobile +49 173 24 18 776  fax +49 30 80 90 57 05
PGP 0x57F3BF04       9064 F4E1 D754 C2FF 1619  305B C09C 5A3B 57F3 BF04
      whom do you want to sponsor today?   http://www.stackless.com/




More information about the Pypy-dev mailing list