summaryrefslogtreecommitdiff
path: root/pod/perlfaq3.pod
diff options
context:
space:
mode:
authorJohn Borwick <jhborwic@unity.ncsu.edu>2000-11-01 08:19:21 -0500
committerJarkko Hietaniemi <jhi@iki.fi>2000-11-01 18:34:55 +0000
commitb73a15ae73f7f71da9a3815a2de5baed524d5e64 (patch)
treef43c11216c2985ca75373148d493fbefd10e639e /pod/perlfaq3.pod
parentb7ee89cee3c5aae4c446f4045b031f8bf83c927e (diff)
downloadperl-b73a15ae73f7f71da9a3815a2de5baed524d5e64.tar.gz
Generalize the Camel wording.
Subject: Re: perlfaq style changes Message-ID: <Pine.GSO.4.21.0011011318270.7428-100000@eos00du.eos.ncsu.edu> p4raw-id: //depot/perl@7516
Diffstat (limited to 'pod/perlfaq3.pod')
-rw-r--r--pod/perlfaq3.pod3
1 files changed, 1 insertions, 2 deletions
diff --git a/pod/perlfaq3.pod b/pod/perlfaq3.pod
index 0400b2756e..1d06c2dc10 100644
--- a/pod/perlfaq3.pod
+++ b/pod/perlfaq3.pod
@@ -244,8 +244,7 @@ See the next question on ``How can I make my Perl program run faster?''
=head2 How can I make my Perl program run faster?
The best way to do this is to come up with a better algorithm. This
-can often make a dramatic difference. Chapter 8 in the Camel has some
-efficiency tips in it you might want to look at. Jon Bentley's book
+can often make a dramatic difference. Jon Bentley's book
``Programming Pearls'' (that's not a misspelling!) has some good tips
on optimization, too. Advice on benchmarking boils down to: benchmark
and profile to make sure you're optimizing the right part, look for