> >BTW, eval() is also part of that full set, and exec is part of the > >language. These invoke the Python bytecode compiler. (And Jim > >Hugunin's IronPython is really slow on this, like 60x slower than > >CPython; I think Jim reported that Jython was 20x slower on exec().) > > > >How do you plan to handle these? What if the entire benchmark was > >given as a triple quoted string that was passed to the exec statement? > > We agreed no eval as part of this challenge, since the point was the > speed of the interpreter engine not of the compiler. I don't see that > on the list of challenge points you posted earlier, though, so it was > either omitted inadvertently or I got snookered. The former, I expect. Fair enough. "No exec or eval" is now officially part of the challenge. You know, I *want* you to win, at least if you can win by a great big margin. Because then we could switch to Parrot to make Python faster. I just very much doubt that you'll be able to bat CPython. --Guido van Rossum (home page: http://www.python.org/~guido/)
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