From: Noah Lavine <noah.b.lavine@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guile-devel@gnu.org
Subject: Re: PEG Parser
Date: Fri, 21 Jan 2011 10:23:00 -0500 [thread overview]
Message-ID: <AANLkTikPStAEGy0bJQ7QwdDhCie4DsnXJArAxEhuqEFT@mail.gmail.com> (raw)
In-Reply-To: <87bp3fi5cp.fsf@gnu.org>
Hello,
> “./check-guile --coverage peg.test” can be used to measure code
> coverage, normally.
I tried running that, but what all I got was this output:
Running peg.test
Totals for this test run:
passes: 21
failures: 0
unexpected passes: 0
expected failures: 0
unresolved test cases: 0
untested test cases: 0
unsupported test cases: 0
errors: 0
That seems incorrect, but I don't know anything about check-guile.
I can probably make smaller unit tests too if you'd like. I'll need a
little bit more time looking at it to understand what to test.
I also have a process question - how can I send patches for the peg
stuff that don't erase mlucy's contributions? If I just sent a diff
between the mainline and myself, it would seem to all come from me. (I
just started a peg branch on my machine.)
Noah
next prev parent reply other threads:[~2011-01-21 15:23 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-13 21:29 PEG Parser Noah Lavine
2011-01-17 21:32 ` Ludovic Courtès
2011-01-21 15:23 ` Noah Lavine [this message]
2011-01-22 21:02 ` Ludovic Courtès
2011-01-24 1:29 ` Noah Lavine
2011-01-24 20:55 ` Ludovic Courtès
2011-01-27 1:40 ` Noah Lavine
2011-01-27 2:23 ` Michael Lucy
2011-01-27 2:38 ` Noah Lavine
2011-01-27 3:02 ` Michael Lucy
2011-01-27 5:17 ` Noah Lavine
2011-01-28 3:25 ` Noah Lavine
2011-01-28 5:13 ` Michael Lucy
2011-01-28 15:48 ` Andy Wingo
2011-01-29 3:07 ` Noah Lavine
2011-01-29 4:15 ` Michael Lucy
2011-01-29 11:34 ` Andy Wingo
2011-01-29 19:37 ` Noah Lavine
2011-01-30 11:43 ` Andy Wingo
2011-02-02 0:26 ` Noah Lavine
2011-02-06 15:31 ` Noah Lavine
2011-02-18 22:03 ` Andy Wingo
2011-02-23 15:10 ` Noah Lavine
2011-03-04 10:52 ` Andy Wingo
2011-03-04 13:09 ` Noah Lavine
2011-01-29 11:33 ` Andy Wingo
-- strict thread matches above, loose matches on Subject: below --
2010-05-27 5:19 Michael Lucy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTikPStAEGy0bJQ7QwdDhCie4DsnXJArAxEhuqEFT@mail.gmail.com \
--to=noah.b.lavine@gmail.com \
--cc=guile-devel@gnu.org \
--cc=ludo@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).