+1 On Dec 11, 2012 8:47 AM, "Ned Batchelder" <ned@nedbatchelder.com> wrote:
On 12/9/2012 5:22 PM, Mark Shannon wrote:
The current CPython bytecode interpreter is rather more complex than it needs to be. A number of bytecodes could be eliminated and a few more simplified by moving the work involved in handling compound statements (loops, try-blocks, etc) from the interpreter to the compiler.
As with all suggestions to optimize the bytecode generation, I'd like to re-iterate the need for a way to disable all optimization, for the sake of reasoning about the program. For example, debugging, coverage measurement, etc. This idea was misunderstood and defeated in http://bugs.python.org/* *issue2506 <http://bugs.python.org/issue2506>, but I strongly believe it is important.
--Ned. ______________________________**_________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/**mailman/listinfo/python-dev<http://mail.python.org/mailman/listinfo/python-dev> Unsubscribe: http://mail.python.org/**mailman/options/python-dev/** guido%40python.org<http://mail.python.org/mailman/options/python-dev/guido%40python.org>