On May 8, 5:53 pm, John Nagle <[EMAIL PROTECTED]> wrote: > The point here is that we don't need language changes or declarations > to make Python much faster. All we need are a few restrictions that > insure that, when you're doing something unusual, the compiler can > tell.
Franz, CMUCL, SBCL and GCL teams made Lisp almost as fast as C. A dynamic language can be fast if the implementation is good. If you look at SBCL and GCL, no code is interpreted. It's all compiled on the fly to native machine code. The compiler begins with some code and some input data, and compiles as much as it can. Then the RT executes the machine code, compiles again, etc. Often long stretches of code can be compiled without break, and tight performance critical loops are usually compiled only once. In addition to this, one needs an efficient system to cache compiled code, in order to do the compilation work only once. making a dynamic language fast is not rocket science. We should have somthing like "GPython", a Python RT on top of a GCC backend, similar to what the GCL team did for Lisp. There is no obvious reason as to why Lisp should have better performance than Python. -- http://mail.python.org/mailman/listinfo/python-list