From: Mo DeJong <mdejong@cygnus.com>
To: sourcenav@sourceware.cygnus.com
Subject: Re: Source Nav 4.5 XREF
Date: Tue, 18 Jul 2000 10:57:00 -0000 [thread overview]
Message-ID: <Pine.SOL.3.91.1000718105426.5282F-100000@cse.cygnus.com> (raw)
In-Reply-To: <3973A604.C883B0C4@highlander.com>
On Mon, 17 Jul 2000, Jorge E. Rodriguez wrote:
> Hello,
>
> I was wondering if there are any options/features to source navigator 4.5 which would
> allow me to determine all symbols which are not referenced in a given project.
>
> My situation is that I have a C++ Source Nav project which may contain a
> fairly sizeable amount of "dead code" (i.e. not used, not referenced,... you get it).
> Well I would like to be able to get rid of these methods, constants,....
>
> I was hoping that since source nav basically creates a Xref database, there would be a
> way to query this XREF db (or run a command on it maybe) which would give me a list
> (does not have to be graphical) of all the symbols which are not referenced.
>
> Any help in this area would be greatly appreciated.
You would need to write your own code to query the databade
for this sort of thing.
http://sources.redhat.com/sourcenav/online-docs/progref/index_pr.html
Mo DeJong
Red Hat Inc
prev parent reply other threads:[~2000-07-18 10:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-17 17:35 Jorge E. Rodriguez
2000-07-18 10:57 ` Mo DeJong [this message]
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.1000718105426.5282F-100000@cse.cygnus.com \
--to=mdejong@cygnus.com \
--cc=sourcenav@sourceware.cygnus.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).