From: Andrew Birkett <adb@tardis.ed.ac.uk>
To: sourcenav@sources.redhat.com
Subject: SN status?
Date: Wed, 21 Feb 2001 02:54:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.10.10102211041230.4550-100000@tardis.tardis.ed.ac.uk> (raw)
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.
2. Is there a list of known issues with the C++ parsing and xref code? Or
a public bugs database?
3. What language are the comments in the C++ parser in? :-)
4. Are there unit tests to check the expected behaviour of the C++ parser?
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. 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++.
BTW, the 'welcome to the list' message still refers to the address
'sourcenav@sourceware.cygnus.com' which presumably is out of date?
Andrew
- www.tardis.ed.ac.uk/~adb -
next reply other threads:[~2001-02-21 2:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-21 2:54 Andrew Birkett [this message]
2001-02-21 5:23 ` Ben Elliston
2001-02-21 19:40 ` Mo DeJong
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.GSO.4.10.10102211041230.4550-100000@tardis.tardis.ed.ac.uk \
--to=adb@tardis.ed.ac.uk \
--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).