public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: Thomas Stroesslin <thomas.stroesslin@epfl.ch>
To: sourcenav@sources.redhat.com
Subject: Xref and find declaration of variables
Date: Tue, 01 May 2001 09:10:00 -0000	[thread overview]
Message-ID: <Pine.GSO.4.21.0105011800580.28286-100000@mantrasun3.epfl.ch> (raw)

consider the following "project":

myfile.c :

int myglobalvar;
int myfunc(int myarg) {
  int mylocalvar;
  int myvar;

  myvar = 1;
  mylocalvar = 1;
  myarg = 1;
  myglobalvar=1;
}

myotherfile.c :

int myvar; // which is global
...

I am working on myfile.c and try to find out things about my variables:

1) find declaration of myvar on the assignment line -> leads me to myvar
     of myotherfile.c (don't you have scope info in the db?)

2) same as 1) for mylocalvar
   -> doesn't find anything, doesn't report error -> does nothing!

3) same as 1) for myarg
   -> same as 2)

4) myglobalvar referred by -> finds nothing

5) myvar or mylocalvar or myarg referred by in function myfunc()
   -> same as 4


all these features are available in sniff+. IMHO, they are among the top
10 most importand code analysis features (the other 5 are working in
sourcenavigator, good stuff)

do you plan to include such features in future releases of
sourcenavigator? If so, when - roughly - can I expect them to be
implemented?

cheers,
tom

             reply	other threads:[~2001-05-01  9:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-01  9:10 Thomas Stroesslin [this message]
2001-05-01 10:32 ` Richard F Weber
2001-05-02  4:33   ` Thomas Stroesslin
2001-05-02 11:28     ` Ian Roxborough
2001-05-03  0:15       ` Thomas Stroesslin
2001-05-02 12:43     ` Mo DeJong
2001-05-01 10:52 ` Mo DeJong
  -- strict thread matches above, loose matches on Subject: below --
2001-03-30  5:45 Thomas Stroesslin

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.21.0105011800580.28286-100000@mantrasun3.epfl.ch \
    --to=thomas.stroesslin@epfl.ch \
    --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).