public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: Ben Elliston <bje@redhat.com>
To: William Gacquer <wgacquer@ubisoft.fr>
Cc: sourcenav@sources.redhat.com
Subject: Re: Xref-ing non used symbols
Date: Fri, 04 Aug 2000 16:25:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.21.0008050923450.7475-100000@moshpit.cygnus.com> (raw)
In-Reply-To: <5D2A198567EED311BD0F009027A25C872EF015@SRVMAIL-ANN>

   	I would like to retrieve all symbols (especialy C functions) that
   are not used at all using the cross referencer. But I did not find the
   way to do that. Is this feasible? How?

Take a look at some of the example Tcl scripts for examples.  There is one
that finds unused global variables in: 

  snavigator/sdk/api/tcl/database/examples/unused.tcl

Ben

  reply	other threads:[~2000-08-04 16:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-04  6:07 William Gacquer
2000-08-04 16:25 ` Ben Elliston [this message]
2000-08-07  3:37 William Gacquer
2000-08-07  3:47 ` Bruce Stephens
2000-08-07  4:09   ` Bruce Stephens
2000-08-07  4:00 William Gacquer
2000-08-07  4:12 ` Bruce Stephens
2000-08-07  5:36 William Gacquer
2000-08-08 14:43 ` Ben Elliston

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.LNX.4.21.0008050923450.7475-100000@moshpit.cygnus.com \
    --to=bje@redhat.com \
    --cc=sourcenav@sources.redhat.com \
    --cc=wgacquer@ubisoft.fr \
    /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).