openbsd-ports/devel/p5-Benchmark-Timer/distinfo

MD5 (Benchmark-Timer-0.7100.tar.gz) = coc/5vDBhCCn4qx+alvA/w==
RMD160 (Benchmark-Timer-0.7100.tar.gz) = 6++wCQCcjzwH7W9qeT4lXXEl1CM=
SHA1 (Benchmark-Timer-0.7100.tar.gz) = 9FuNqkL4svdmTZ06HB4UK7EiBb4=
SHA256 (Benchmark-Timer-0.7100.tar.gz) = H9gGl/rz8HjNEGJRGOnTa7Z8YjEQwoDGu8CUIeXmc7w=
SIZE (Benchmark-Timer-0.7100.tar.gz) = 38218
base64 distinfo with SHA256 2007-04-05 11:37:40 -04:00			`MD5 (Benchmark-Timer-0.7100.tar.gz) = coc/5vDBhCCn4qx+alvA/w==`
			`RMD160 (Benchmark-Timer-0.7100.tar.gz) = 6++wCQCcjzwH7W9qeT4lXXEl1CM=`
			`SHA1 (Benchmark-Timer-0.7100.tar.gz) = 9FuNqkL4svdmTZ06HB4UK7EiBb4=`
			`SHA256 (Benchmark-Timer-0.7100.tar.gz) = H9gGl/rz8HjNEGJRGOnTa7Z8YjEQwoDGu8CUIeXmc7w=`
import p5-Benchmark-Timer 0.7100, requirement for grepmail 5.x The Benchmark::Timer class allows you to time portions of code conveniently, as well as benchmark code by allowing timings of repeated trials. It is perfect for when you need more precise information about the running time of portions of your code than the Benchmark module will give you, but don't want to go all out and profile your code. ok jasper@ 2007-03-18 16:17:10 -04:00			`SIZE (Benchmark-Timer-0.7100.tar.gz) = 38218`