- Timestamp:
- 11/06/05 14:07:06 (3 years ago)
- Files:
-
- 1 modified
-
lib/pugs/run.pod (modified) (2 diffs)
Legend:
- Unmodified
- Added
- Removed
-
lib/pugs/run.pod
r7606 r7871 87 87 88 88 causes Pugs to execute the program using C<I<backend>>. Currently, valid 89 backends are C<P arrot>, C<PIR>, C<Perl5>, and C<JS>.89 backends are C<PIR> (execution via Parrot), C<JS> (JavaScript), and C<Pugs>. 90 90 91 91 To start the interactive shell of a backend, run C<pugs -BI<backend>>, but note … … 100 100 101 101 causes Pugs to compile the program using C<I<backend>>. Currently, valid 102 backends are C<Pugs>, C<P arrot>, C<PIR>, C<Haskell>, C<JS>, and C<PIL> with its103 variants C<Perl5>, C<JSON>, and C<Binary>.102 backends are C<Pugs>, C<PIR>, C<GHC>, C<JS>, and various variants of PIL: 103 C<PIL1>, C<PIL1-Binary>, C<PIL1-JSON>, C<PIL1-Perl5> (and C<PIL2-...>). 104 104 105 105 Note that, as with C<-c>, C<BEGIN {...}> and C<CHECK {...}> blocks, as well as
