Comments on: Python’s Innards: Hello, ceval.c! http://tech.blog.aknin.name/2010/09/02/pythons-innards-hello-ceval-c-2/ Glossolalia about technology by @aknin Tue, 31 Jan 2012 18:23:15 +0000 hourly 1 http://wordpress.com/ By: Abafei Software http://tech.blog.aknin.name/2010/09/02/pythons-innards-hello-ceval-c-2/#comment-1121 Mon, 28 Mar 2011 03:18:26 +0000 http://tech.blog.aknin.name/?p=989#comment-1121 Yasher Koach!

Amazingly explained!

]]> By: Eli Bendersky http://tech.blog.aknin.name/2010/09/02/pythons-innards-hello-ceval-c-2/#comment-919 Mon, 06 Sep 2010 03:45:15 +0000 http://tech.blog.aknin.name/?p=989#comment-919 Yaniv, nice job differentiating between the simple core and the optimized & complicated outer shell. As always, optimization and clarity are in a clash here and optimization wins. When trying to understand how these things work under the hood, optimization tricks are a big stumbling block, and simplifying them as much as possible is crucial.

]]> By: Nick Coghlan http://tech.blog.aknin.name/2010/09/02/pythons-innards-hello-ceval-c-2/#comment-910 Thu, 02 Sep 2010 22:01:33 +0000 http://tech.blog.aknin.name/?p=989#comment-910 And the curious can search ceval.c for CASE_TOO_BIG to see that yes, indeed, there is a #define that allows configure and/or pyport.h to break the switch into two separate pieces :)

]]>