diff options
author | Peter J. Acklam) (via RT <perlbug-followup@perl.org> | 2011-01-06 23:12:59 -0800 |
---|---|---|
committer | Abigail <abigail@abigail.be> | 2011-01-07 11:40:18 +0100 |
commit | 98dc955152ee6f0a1849a6e47a0c2c3b5fae00a6 (patch) | |
tree | 4a1a6ed94068d15eaf6c1f2ab7a71c3ecc3767ce /lib/Benchmark.t | |
parent | 1b298e71cb5407f2917b03adc3bddf8526e7043d (diff) | |
download | perl-98dc955152ee6f0a1849a6e47a0c2c3b5fae00a6.tar.gz |
Fix typos (spelling errors) in lib/*
# New Ticket Created by (Peter J. Acklam)
# Please include the string: [perl #81890]
# in the subject line of all future correspondence about this issue.
# <URL: http://rt.perl.org/rt3/Ticket/Display.html?id=81890 >
Signed-off-by: Abigail <abigail@abigail.be>
Diffstat (limited to 'lib/Benchmark.t')
-rw-r--r-- | lib/Benchmark.t | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/lib/Benchmark.t b/lib/Benchmark.t index 9b8e2af1d9..73e09c6f51 100644 --- a/lib/Benchmark.t +++ b/lib/Benchmark.t @@ -28,7 +28,7 @@ my $Noc_Pattern = qr/(\d+) +wallclock secs? +\( *(-?\d+\.\d\d) +usr +\+ +(-?\d+\.\d\d) +sys += +(-?\d+\.\d\d) +CPU\)/; my $Nop_Pattern = qr/(\d+) +wallclock secs? +\( *(-?\d+\.\d\d) +cusr +\+ +(-?\d+\.\d\d) +csys += +\d+\.\d\d +CPU\)/; -# Please don't trust the matching parenthises to be useful in this :-) +# Please don't trust the matching parentheses to be useful in this :-) my $Default_Pattern = qr/$All_Pattern|$Noc_Pattern/; my $t0 = new Benchmark; @@ -111,7 +111,7 @@ is ($auto, $default, 'timestr ($diff, "auto") matches timestr ($diff)'); my ($wallclock, $usr, $sys, $cusr, $csys, $cpu) = $all =~ $All_Pattern; - is (timestr ($diff, 'none'), '', "none supresses output"); + is (timestr ($diff, 'none'), '', "none suppresses output"); my $noc = timestr ($diff, 'noc'); like ($noc, qr/$wallclock +wallclock secs? +\( *$usr +usr +\+ +$sys +sys += +$cpu +CPU\)/, 'timestr ($diff, "noc")'); @@ -529,7 +529,7 @@ undef $debug; untie *STDERR; # To check the cache we are poking where we don't belong, inside the namespace. -# The way benchmark is written We can't actually check whehter the cache is +# The way benchmark is written we can't actually check whether the cache is # being used, merely what's become cached. clearallcache(); |