"Martin v. Löwis" <martin at v.loewis.de> writes: > Oliver Schoenborn wrote: >> I can accept that only if there is something inherent to the technique which >> exploits a non-specified aspect of the language. I can't think of any. Could >> you be more specific about what aspect is not portable? > > The idea that you can execute code at the end of a function to invoke > teardown operations, even in the presence of exceptions. That cannot be > done for Jython, AFAIK. Jython generates Java byte code from Python > source code, so there is no Python virtual machine anywhere. I'm sure I missed something important along the way here, but the fact that you can generate Java bytecode for Python's "finally" in Jython, it seems to me, _proves_ that you can also generate code to that will be executed at the end of a function even in the presence of exceptions. -- Dave Abrahams Boost Consulting http://www.boost-consulting.com
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4