From: Mo DeJong <mdejong@cygnus.com>
To: sourcenav@sources.redhat.com
Subject: Re: SN status?
Date: Wed, 21 Feb 2001 19:40:00 -0000 [thread overview]
Message-ID: <Pine.SOL.3.91.1010221192723.24403B-100000@cse.cygnus.com> (raw)
In-Reply-To: <Pine.GSO.4.10.10102211041230.4550-100000@tardis.tardis.ed.ac.uk>
On Wed, 21 Feb 2001, Andrew Birkett wrote:
> Hi,
>
> I'm mainly interested in the C++ parsing and xref side of SN, and I've got
> a few questions which I hope someone can answer.
>
> 1. The latest released version is 4.5.2 and I understand that Redhat
> people are working on 5.0. Is there cvs access to the latest development
> sources? I don't want to start tweaking bits of the 4.5.2 snavigator
> source if whole chunks are going to be rewritten for 5.0.
No, we don't have 5.0 available via CVS yet. Heck, we don't
have it available via FTP yet (but we are getting closer).
The code that implements the GUI has changed quite a bit,
the back end stuff has not.
> 2. Is there a list of known issues with the C++ parsing and xref code? Or
> a public bugs database?
No and not yet but there will be.
> 3. What language are the comments in the C++ parser in? :-)
Welcome to the party!
> 4. Are there unit tests to check the expected behaviour of the C++ parser?
No. We have been talking about implementing a nice XML layer
that would sit between the parsers and the DB backend.
That would let us write test cases quite easily, the
problem is finding enough time to implement it.
> From reading the list archive and web searches, there doesn't appear to be
> a massive amount of external development on SN, which is a pity because
> it looks like it could be a great tool.
We think that will pick up after 5.0 is out.
> I'd like the C++ parser to get to
> the stage where I'm confident it's picking up all of the xref's, since I'm
> looking to write a refactoring assistant for C++.
Sounds like you are interested in helping with C++
regression tests, we welcome such help. The C++
support is an area that needs work.
Mo DeJong
Red Hat Inc
next prev parent reply other threads:[~2001-02-21 19:40 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 [this message]
2001-02-21 21:12 ` Ben Elliston
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=Pine.SOL.3.91.1010221192723.24403B-100000@cse.cygnus.com \
--to=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).