From: Rafael Garcia-Suarez <rgarciasuarez@gmail.com>
Date: Thu, 22 Mar 2007 14:37:43 +0000 (+0000)
Subject: Remove references to perlcc from the core docs.
X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=59f521f4af7acce29f3bf3ecf4f2c911e305e59b;p=p5sagit%2Fp5-mst-13.2.git

Remove references to perlcc from the core docs.

p4raw-id: //depot/perl@30685
---

diff --git a/pod/perlfunc.pod b/pod/perlfunc.pod
index 30387c2..c23dbd9 100644
--- a/pod/perlfunc.pod
+++ b/pod/perlfunc.pod
@@ -1406,20 +1406,11 @@ B<WARNING>: Any files opened at the time of the dump will I<not>
 be open any more when the program is reincarnated, with possible
 resulting confusion on the part of Perl.
 
-This function is now largely obsolete, partly because it's very
-hard to convert a core file into an executable, and because the
-real compiler backends for generating portable bytecode and compilable
-C code have superseded it.  That's why you should now invoke it as
-C<CORE::dump()>, if you don't want to be warned against a possible
+This function is now largely obsolete, mostly because it's very hard to
+convert a core file into an executable. That's why you should now invoke
+it as C<CORE::dump()>, if you don't want to be warned against a possible
 typo.
 
-If you're looking to use L<dump> to speed up your program, consider
-generating bytecode or native C code as described in L<perlcc>.  If
-you're just trying to accelerate a CGI script, consider using the
-C<mod_perl> extension to B<Apache>, or the CPAN module, CGI::Fast.
-You might also consider autoloading or selfloading, which at least
-make your program I<appear> to run faster.
-
 =item each HASH
 X<each> X<hash, iterator>
 
diff --git a/pod/perlmod.pod b/pod/perlmod.pod
index 240630c..53f3d21 100644
--- a/pod/perlmod.pod
+++ b/pod/perlmod.pod
@@ -323,9 +323,7 @@ and before the run time begins, in LIFO order.  C<CHECK> code blocks are used
 in the Perl compiler suite to save the compiled state of the program.
 
 C<INIT> blocks are run just before the Perl runtime begins execution, in
-"first in, first out" (FIFO) order. For example, the code generators
-documented in L<perlcc> make use of C<INIT> blocks to initialize and
-resolve pointers to XSUBs.
+"first in, first out" (FIFO) order.
 
 When you use the B<-n> and B<-p> switches to Perl, C<BEGIN> and
 C<END> work just as they do in B<awk>, as a degenerate case.
diff --git a/pod/perlutil.pod b/pod/perlutil.pod
index 19d2dec..3c703c1 100644
--- a/pod/perlutil.pod
+++ b/pod/perlutil.pod
@@ -210,10 +210,6 @@ F<dprofpp> utility analyzes the output of this profiler and tells you
 which subroutines are taking up the most run time. See L<Devel::DProf>
 for more information.
 
-=item L<perlcc|perlcc>
-
-F<perlcc> is the interface to the experimental Perl compiler suite.
-
 =item L<prove>
 
 F<prove> is a command-line interface to the test-running functionality of
@@ -286,7 +282,7 @@ L<podchecker|podchecker>, L<splain|splain>, L<perldiag>,
 L<roffitall|roffitall>, L<a2p|a2p>, L<s2p|s2p>, L<find2perl|find2perl>,
 L<File::Find|File::Find>, L<pl2pm|pl2pm>, L<perlbug|perlbug>,
 L<h2ph|h2ph>, L<c2ph|c2ph>, L<h2xs|h2xs>, L<dprofpp|dprofpp>,
-L<Devel::DProf>, L<perlcc|perlcc>, L<enc2xs>, L<xsubpp>, L<cpan>,
+L<Devel::DProf>, L<enc2xs>, L<xsubpp>, L<cpan>,
 L<instmodsh>, L<piconv>, L<prove>, L<corelist>, L<ptar>, L<ptardiff>,
 L<shasum>
 
diff --git a/pod/perlvar.pod b/pod/perlvar.pod
index f39ac7d..c3adfa0 100644
--- a/pod/perlvar.pod
+++ b/pod/perlvar.pod
@@ -1047,7 +1047,7 @@ X<$^C> X<$COMPILING>
 The current value of the flag associated with the B<-c> switch.
 Mainly of use with B<-MO=...> to allow code to alter its behavior
 when being compiled, such as for example to AUTOLOAD at compile
-time rather than normal, deferred loading.  See L<perlcc>.  Setting
+time rather than normal, deferred loading.  Setting
 C<$^C = 1> is similar to calling C<B::minus_c>.
 
 =item $DEBUGGING