cvsuser 05/04/01 08:34:26
Modified: docs faq.pod Log: Describe the beneifts of cross language runtime that parrot gives. Patch courtesy of Matthew Zimmerman <[EMAIL PROTECTED]> Revision Changes Path 1.19 +9 -2 parrot/docs/faq.pod Index: faq.pod =================================================================== RCS file: /cvs/public/parrot/docs/faq.pod,v retrieving revision 1.18 retrieving revision 1.19 diff -u -r1.18 -r1.19 --- faq.pod 1 Apr 2005 15:29:38 -0000 1.18 +++ faq.pod 1 Apr 2005 16:34:26 -0000 1.19 @@ -230,6 +230,13 @@ impossible on small systems. So by going with Pugs and GHC we'd be sacrificing portability. +As well, other languages apart from Perl 6 are being targeted to Parrot. +Significant parts of Python, TCL, Perl 5, and Basic have already been +implemented and others are on the way. Running multiple languages on the +same Parrot engine allows them to be cross-language compatible-- in other +words, one targeted language could directly invoke the methods of another +at the bytecode level. + Finally there is a reason the Parrot design keeps talking about running bytecode direct from disk rather than relying on doing compiling (from Perl or with a JIT) in memory. It's all very well doing such operations when running
