Changeset 7127 for lib/pugs/run.pod
- Timestamp:
- 09/24/05 15:28:50 (3 years ago)
- Files:
-
- 1 modified
-
lib/pugs/run.pod (modified) (1 diff)
Legend:
- Unmodified
- Added
- Removed
-
lib/pugs/run.pod
r6926 r7127 70 70 71 71 causes Pugs to execute the program using C<I<backend>>. Currently, valid 72 backends are C<Parrot> and C<PIR>.73 74 T he JavaScript backend (PIL2JS) provides an interactive shell in75 F<perl5/PIL2JS/jspugs.pl>; The interactive compiler and evaluator of the Perl 5 76 backend (PIL-Run) can be found in F<perl5/PIL-Run/crude_repl.pl>.72 backends are C<Parrot>, C<PIR>, C<Perl5>, and C<JS>. 73 74 To start the interactive shell of a backend, run C<pugs -BI<backend>>, but note 75 that currently only the Perl 5 and JavaScript backends provide interactive 76 shells. 77 77 78 78 The normal runcore supports more features than the other runcores, the Parrot 79 backend is quite fast, PIL2JS is good on binding and references, and PIL-Run80 offers excellent support for laziness.79 backend is quite fast, the JavaScript backend is good on binding and 80 references, and Perl 6 on Perl 5 offers excellent support for laziness. 81 81 82 82 =item C<-CI<backend>> 83 83 84 84 causes Pugs to compile the program using C<I<backend>>. Currently, valid 85 backends are C<Pugs>, C<Parrot>, C<PIR>, C<Haskell>, and C<PIL> with its85 backends are C<Pugs>, C<Parrot>, C<PIR>, C<Haskell>, C<JS>, and C<PIL> with its 86 86 variants C<Perl5>, C<JSON>, and C<Binary>. 87 87
