From: Ben Elliston <bje@redhat.com>
To: Mo DeJong <mdejong@cygnus.com>
Cc: sourcenav@sources.redhat.com
Subject: Re: SN status?
Date: Wed, 21 Feb 2001 21:12:00 -0000 [thread overview]
Message-ID: <14996.40831.914146.298575@scooby.cygnus.com> (raw)
In-Reply-To: <Pine.SOL.3.91.1010221192723.24403B-100000@cse.cygnus.com>
>>>>> "Mo" == Mo DeJong <mdejong@cygnus.com> writes:
Mo> No. We have been talking about implementing a nice XML layer
Mo> that would sit between the parsers and the DB backend.
Mo> That would let us write test cases quite easily, the
Mo> problem is finding enough time to implement it.
One thing I've been itching to do is knock together a DejaGNU
framework that allows us to test the C/C++ parser against the GCC
testsuite. Of course, we can maintain our own smaller regression
testsuite, but to get all of these tests for such little effort would
be a win.
Ben
next prev parent reply other threads:[~2001-02-21 21:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-21 2:54 Andrew Birkett
2001-02-21 5:23 ` Ben Elliston
2001-02-21 19:40 ` Mo DeJong
2001-02-21 21:12 ` Ben Elliston [this message]
2001-02-21 21:21 ` Mo DeJong
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=14996.40831.914146.298575@scooby.cygnus.com \
--to=bje@redhat.com \
--cc=mdejong@cygnus.com \
--cc=sourcenav@sources.redhat.com \
/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).