At 8:57 AM -0500 2/28/03, A.M. Kuchling wrote:
>Terry Reedy wrote:
>>In any case, this seems to makes the contest one more of special-case
>>optimization and less of general-case running time, and therefore of
>>less relevance to users who want *their* programs to run faster with
>>an out-of-the-box interpreter.
>
>Indeed. I suspect, though, that if the test program exercises a sizable
>chunk of Python's functionality, we won't see a Parrot-based
>implementation that can run it. 2004 is a long time away, time
>enough for the PyPy effort to bear fruit.
The challenge is core interpreter speed, so if the challenge programs
use that and Parrot can't cope, I lose and pie will be flung. If the
PyPy stuff gives a good turbo boost to the python core, great,
that'll make it more challenging.
--
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
dan@sidhe.org have teddy bears and even
teddy bears get drunk
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