[patch] blead@25226 on OpenVMS/vms.c - fopen bug.

[p5sagit/p5-mst-13.2.git] / pod / perlcompile.pod

diff --git a/pod/perlcompile.pod b/pod/perlcompile.pod
index 07c4202..046576b 100644 (file)
--- a/pod/perlcompile.pod
+++ b/pod/perlcompile.pod
@@ -236,9 +236,9 @@ execute the bytecode that it produces.  The ByteLoader module provides
 this functionality.
 
 To turn a Perl program into executable byte code, you can use C<perlcc>
-with the C<-b> switch:
+with the C<-B> switch:
 
-  perlcc -b myperlprogram.pl
+  perlcc -B myperlprogram.pl
 
 The byte code is machine independent, so once you have a compiled
 module or program, it is as portable as Perl source (assuming that
@@ -256,18 +256,20 @@ the Perl data structures directly.  The program will still link against
 the Perl interpreter library, to allow for eval(), C<s///e>,
 C<require>, etc.
 
-The C<perlcc> tool generates such executables when using the -opt
+The C<perlcc> tool generates such executables when using the -O
 switch.  To compile a Perl program (ending in C<.pl>
 or C<.p>):
 
-  perlcc -opt myperlprogram.pl
+  perlcc -O myperlprogram.pl
 
 To produce a shared library from a Perl module (ending in C<.pm>):
 
-  perlcc -opt Myperlmodule.pm
+  perlcc -O Myperlmodule.pm
 
 For more information, see L<perlcc> and L<B::CC>.
 
+=head1 Module List for the Compiler Suite
+
 =over 4
 
 =item B
@@ -335,6 +337,14 @@ programs translated into C by B::CC can execute faster than normal
 interpreted programs.  See L</"The Optimized C Back End"> for
 details about usage.
 
+=item B::Concise
+
+This module prints a concise (but complete) version of the Perl parse
+tree.  Its output is more customizable than the one of B::Terse or
+B::Debug (and it can emulate them). This module useful for people who
+are writing their own back end, or who are learning about the Perl
+internals.  It's not useful to the average programmer.
+
 =item B::Debug
 
 This module dumps the Perl parse tree in verbose detail to STDOUT.