Changeset 6750 for lib

Timestamp:

09/05/05 23:28:04 (3 years ago)

Author:

iblech

Message:

* Usual svn props.
* STATUS: Update (P5 regexes in PIL2JS, laziness in PIL-Run, more tests)
* pugs::run: Fixed information about -Bbackend and pointed to PIL2JS's

jspugs.pl and PIL-Run's crude_repl.pl. Also updated the entries about
-Cbackend and Pugs's safemode.

Files:

• lib/pugs/run.pod (modified) (2 diffs)

lib/pugs/run.pod

@@ -70 +70 @@
 
 causes Pugs to execute the program using C<I<backend>>. Currently, valid
-backends are C<Pugs>, C<Parrot>, C<PIR>, and C<Haskell>.
+backends are C<Parrot> and C<PIR>.
+
+The JavaScript backend provides an interactive shell in
+F<perl5/PIL2JS/jspugs.pl>; The interactive compiler and evaluator of the Perl 5
+backend can be found in F<perl5/PIL-Run/crude_repl.pl>.
 
 =item C<-CI<backend>>
 
 causes Pugs to compile the program using C<I<backend>>. Currently, valid
-backends are C<Pugs>, C<Parrot>, C<PIR>, and C<Haskell>.
+backends are C<Pugs>, C<Parrot>, C<PIR>, C<Haskell>, and C<PIL> with its
+variants C<Perl5>, C<JSON>, and C<Binary>.
 
 Note that, as with C<-c>, C<BEGIN {...}> and C<CHECK {...}> blocks, as well as
-C<use Module>, are still executed. So don't try to compile potentially unsafe
-code!
+C<use Module> statements, are still executed. So don't try to compile
+potentially unsafe code!
 
 =item C<-MI<module>>
@@ -175 +180 @@
 "unsafe" -- e.g. operations which use IO -- unavailable to a Perl program.
 
-    $ env PUGS_SAFEMODE=1 pugs -e 'say "I am unsafe"'
-    *** No compatible subroutine found: "&say"
-        at -e line 1, column 1-9
+    $ env PUGS_SAFEMODE=1 pugs -e 'unlink "foo"'
+    *** No compatible subroutine found: "&unlink"
+        at -e line 1, column 1-13
 
 =item C<PUGS_PARROT_OPTS>