From 85a71c86b1d412e41773a89f52834384f8a764ff Mon Sep 17 00:00:00 2001 From: jkeenan Date: Mon, 28 Feb 2011 21:50:00 -0500 Subject: [PATCH] Re-rag POD so it will look better in HTML. --- config/auto/coverage.pm | 17 ++++++++--------- 1 file changed, 8 insertions(+), 9 deletions(-) diff --git a/config/auto/coverage.pm b/config/auto/coverage.pm index b04a729ced..374f03604f 100644 --- a/config/auto/coverage.pm +++ b/config/auto/coverage.pm @@ -9,15 +9,14 @@ config/auto/coverage- Check whether coverage analysis tools are present Coverage analysis is the measurement of the extent to which a program's source code is exercised by its tests. -In Parrot, we can perform coverage analysis -on our Parrot source code (well, at least on F<.c> and F<.pmc> files) and on -the Perl 5 components used in our tools. - -To conduct such analysis, we need -the C coverage utility F and two utilities, F and F, -which are included in the Devel-Cover distribution from CPAN. (Paul -Johnson++). This configuration step determines whether those utilities are -present. +In Parrot, we can perform coverage analysis on our Parrot source code (well, +at least on F<.c> and F<.pmc> files) and on the Perl 5 components used in our +tools. + +To conduct such analysis, we need the C coverage utility F and two +utilities, F and F, which are included in the Devel-Cover +distribution from CPAN. (Paul Johnson++). This configuration step determines +whether those utilities are present. =cut