[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: PEG Parser
From: |
Ludovic Courtès |
Subject: |
Re: PEG Parser |
Date: |
Mon, 24 Jan 2011 21:55:26 +0100 |
User-agent: |
Gnus/5.110011 (No Gnus v0.11) Emacs/23.2 (gnu/linux) |
Hi,
Noah Lavine <address@hidden> writes:
>> It should have produced $top_builddir/guile.info, which can be used as
>> input to LCOV to generate an HTML code coverage report
>> (http://ltp.sourceforge.net/coverage/lcov.php).
>
> Oh, that worked. The current tests check 92.6% of the lines in
> peg.scm, and 90.7% of the functions. I looked through lcov's HTML
> guide, and it looks like what the tests miss is almost all
> error-handling code. However, I must say that the HTML output looked a
> bit suspicious - for instance, there were places where the first line
> of a function was marked as hit, but the second line was not.
Often, if a function is defined but unused, the ‘define’ line will be
marked as hit whereas the rest of the function will remain red–but
that’s OK since strictly speaking the ‘define’ line /is/ executed.
However, it could be that the code coverage code is buggy. If you find
obvious errors and can reduce them, I’d be happy to look into it.
Thanks,
Ludo’.
- PEG Parser, Noah Lavine, 2011/01/13
- Re: PEG Parser, Ludovic Courtès, 2011/01/17
- Re: PEG Parser, Noah Lavine, 2011/01/21
- Re: PEG Parser, Ludovic Courtès, 2011/01/22
- Re: PEG Parser, Noah Lavine, 2011/01/23
- Re: PEG Parser,
Ludovic Courtès <=
- Re: PEG Parser, Noah Lavine, 2011/01/26
- Re: PEG Parser, Michael Lucy, 2011/01/26
- Re: PEG Parser, Noah Lavine, 2011/01/26
- Re: PEG Parser, Michael Lucy, 2011/01/26
- Re: PEG Parser, Noah Lavine, 2011/01/27
- Re: PEG Parser, Noah Lavine, 2011/01/28
- Re: PEG Parser, Michael Lucy, 2011/01/28
- Re: PEG Parser, Andy Wingo, 2011/01/28
- Re: PEG Parser, Noah Lavine, 2011/01/28
- Re: PEG Parser, Michael Lucy, 2011/01/28