diff options
| author | Florian Ragwitz <rafl@debian.org> | 2011-06-14 12:28:12 +0200 |
|---|---|---|
| committer | Florian Ragwitz <rafl@debian.org> | 2011-06-14 22:49:14 +0200 |
| commit | c9dab4e97a0bc57966ab975591aa385f9d89f9e2 (patch) | |
| tree | da608c32e98bf2902e4ed9f466ff8cb9fcd06c6e /pod/perlperf.pod | |
| parent | 7ac818b24e0ec6f68348321cc96349db90c36cb9 (diff) | |
| download | perl-c9dab4e97a0bc57966ab975591aa385f9d89f9e2.tar.gz | |
Kill Devel::DProf
It has been deprecated in 5.14. Now is the time to remove it.
Diffstat (limited to 'pod/perlperf.pod')
| -rw-r--r-- | pod/perlperf.pod | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/pod/perlperf.pod b/pod/perlperf.pod index cac6eee665..4751e3591c 100644 --- a/pod/perlperf.pod +++ b/pod/perlperf.pod @@ -30,7 +30,7 @@ optimization process. Firstly, you need to establish a baseline time for the existing code, which timing needs to be reliable and repeatable. You'll probably want to use the -C<Benchmark> or C<Devel::DProf> modules, or something similar, for this step, +C<Benchmark> or C<Devel::NYTProf> modules, or something similar, for this step, or perhaps the Unix system C<time> utility, whichever is appropriate. See the base of this document for a longer list of benchmarking and profiling modules, and recommended further reading. |