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. > If it is portable, then since it works as-is in Python, it could be put into > the specs. It doesn't work in Python. I believe your implementation also fails in Jython (but didn't test). Regards, Martin
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