On Sat, Jul 29, 2000 at 01:18:06PM +0100, Hildo Biersma wrote:
> There's 'gcov', a test coverage program for gcc.
gcov looks like it does enough for our purposes for the moment. Since
its text, we should be able to set up a fairly automated thing to
parse the output and alert us to uncovered por
Tony Payne wrote:
>
> Yes, Devel::Coverage is great for testing perl code. That won't help us
> test perl itself, however. For that, we must have a C coverage tool --
> assuming perl6 will also be written in C.
There's 'gcov', a test coverage program for gcc.
Also, I expect that some of the
> I have no idea what coverage tools are available for C. Someone want
> to compile a list? I have also never really done much coverage
> analysis. Would someone with time and experience step forward and
> take responsiblity for it?
There don't seem to be many free/open tools. I was able to
On Fri, Jul 28, 2000 at 03:07:09PM -0700, Tony Payne wrote:
> I think Schwern's proposal of a patch for every test, applied appropriately
> will do a good job of making sure the Perl test suite has close to 100%
> functional coverage of the core. However, we should also consider doing
> code cove
