Armin, On Thu, Sep 09, 2004 at 11:14:44AM +0100, Armin Rigo wrote: | I agree with Samuele that the proposal is far too vague currently. You | should try to describe what precisely should occur in each situation. Oh, absolutely. This was a draft PEP to collect feedback. It will be a bit before I have a chunk of time to assimilate the comments and produce another (more detailed) draft. Your comments were very helpful, I've got a bit of education in my future. | A major problem I see with the proposal is that you can describe what | should occur in some situations by presenting source code snippets; such | descriptions correspond easily to possible semantics at the bytecode | level. But bytecode is not a natural granularity for coroutine issues. *nod* | This doesn't mean that it is impossible to figure out a more limited | concept, like you are trying to do. However keeping the "restartable | exception" idea in mind should help focusing on the difficult problems | and where restrictions are needed. Best, Clark
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