[Python-Dev] capturing RETURN_VALUE (original) (raw)

Christian Tismer tismer at stackless.com
Mon Aug 9 01🔞23 CEST 2004

Tim Peters wrote:

...

It did in your specific example, but not necessarily. In your specific example, the finally block didn't execute "break" if an exception was raised, it only did "break" if the finally block was entered because of a return. If it had done "break" in the exception case too, it would have "abandoned" the exception too:

Sure, that was by design. I'm trying to inline functions into each other, with smallest possible changes to the bytecodes of the inlined functions. Exceptions shall pass through, returns shall be captured and not cause the embracing function to return, but to continue with the "returned" value.

thanks for this answer -- 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/

More information about the Python-Dev mailing list