cvsuser 04/07/24 03:26:50
Modified: . MANIFEST Added: languages/python README Log: Pie-thon 96 - add a README Revision Changes Path 1.710 +1 -0 parrot/MANIFEST Index: MANIFEST =================================================================== RCS file: /cvs/public/parrot/MANIFEST,v retrieving revision 1.709 retrieving revision 1.710 diff -u -w -r1.709 -r1.710 --- MANIFEST 22 Jul 2004 12:48:10 -0000 1.709 +++ MANIFEST 24 Jul 2004 10:26:39 -0000 1.710 @@ -2260,6 +2260,7 @@ languages/perl6/t/subs/simple.t [perl6] languages/perl6/t/var/scalar/string/qq.t [perl6] languages/python/Makefile [] +languages/python/README [] languages/python/python.bnf [] languages/python/python.prd [] languages/python/mdis.py [] 1.1 parrot/languages/python/README Index: README =================================================================== This directory contains the outcome of the (failed) attempt to implement - within five weeks - enough of Python, to run the Pie-thon benchmark for OSCON: http://mail.python.org/pipermail/python-dev/2003-December/040977.html The bytecode translator pie-thon.pl was just intended as a quick hack, to see, what parts of parrot are missing and to get the project running. The implementation is a mess and partially wrong, OTOH it's enough to get four and half tests running. F<t/pie/b*.t> shows implemented features. IMHO its not a good idea to translate a language at the bytecode level: too much information is hidden in the linearized opcode stream, the opcodes are already specialized for the target VM. The translator has more or less to guess, what's really intended. A real implementation of a compiler should use the AST to produce Parrot bytecode. leo
