X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=pod%2Fperlcompile.pod;h=e5544ec444cbc2efea1a8fc40c2e8f8f1ac342df;hb=c9d5ac959cdfa7a668b3bfbbc2b56923c316ef43;hp=04dc019b36b3932b2aedaa178daa8df40de0f687;hpb=cb50131aab68ac6dda048612c6e853b8cb08701e;p=p5sagit%2Fp5-mst-13.2.git diff --git a/pod/perlcompile.pod b/pod/perlcompile.pod index 04dc019..e5544ec 100644 --- a/pod/perlcompile.pod +++ b/pod/perlcompile.pod @@ -103,9 +103,9 @@ This is why all the back ends print: before producing any other output. -=head2 The Cross Referencing Back End (B::Xref) +=head2 The Cross Referencing Back End -The cross referencing back end produces a report on your program, +The cross referencing back end (B::Xref) produces a report on your program, breaking down declarations and uses of subroutines and variables (and formats) by file and subroutine. For instance, here's part of the report from the I program that comes with Perl: @@ -203,11 +203,11 @@ The B<-p> option adds parentheses where normally they are omitted: See L for more information on the formatting options. -=head2 The Lint Back End (B::Lint) +=head2 The Lint Back End -The lint back end inspects programs for poor style. One programmer's -bad style is another programmer's useful tool, so options let you -select what is complained about. +The lint back end (B::Lint) inspects programs for poor style. One +programmer's bad style is another programmer's useful tool, so options +let you select what is complained about. To run the style checker across your source code: @@ -306,8 +306,9 @@ I program that produces bytecode. =item B::Bblock -This module is used by the B::CC back end. It walks "basic blocks", -whatever they may be. +This module is used by the B::CC back end. It walks "basic blocks". +A basic block is a series of operations which is known to execute from +start to finish, with no possibility of branching or halting. =item B::Bytecode @@ -368,12 +369,12 @@ can identify. See L for details about usage. =item B::Showlex This module prints out the my() variables used in a function or a -file. To gt a list of the my() variables used in the subroutine +file. To get a list of the my() variables used in the subroutine mysub() defined in the file myperlprogram: $ perl -MO=Showlex,mysub myperlprogram -To gt a list of the my() variables used in the file myperlprogram: +To get a list of the my() variables used in the file myperlprogram: $ perl -MO=Showlex myperlprogram @@ -418,7 +419,7 @@ names. The optimized C backend outputs code for more modules than it should (e.g., DirHandle). It also has little hope of properly handling -C outside the running subroutine (C is ok). +C outside the running subroutine (C is okay). C currently does not work at all in this backend. It also creates a huge initialization function that gives C compilers headaches. Splitting the initialization function gives