public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: Ian Roxborough <irox@redhat.com>
To: Mike_D_Davies@fmo.com
Cc: sourcenav@sourceware.cygnus.com
Subject: Re: Adding a Parser: SN_LOCAL_VAR_DEF ?
Date: Fri, 10 Aug 2001 10:21:00 -0000	[thread overview]
Message-ID: <3B741AB3.932EE7E3@redhat.com> (raw)
In-Reply-To: <85256AA4.002F0DB1.00@sfldmint11.na.fmo.com>

Mike_D_Davies@fmo.com wrote:
> 
> >  Local variables should be working in C/C++ use now.  You should
> >     see them in the Xref window.
> 
> When you say "now" what do you mean in terms of version number ?

5.0

> I am using SN under Windows from the sourcenav-010412-windows.zip file.
> Local C/C++ variables don't work for me despite having the "generate
> references to local variables" checkbox checked.
>
> I think there may be a problem still lingering in there somewhere,
> but I got no response when I posted earlier.

I hunted out your earlier post and ran your example code
snippet.  I did an Xref of the "main" function and could
see "y" and "retval" as local variable.  This was under
a Linux system not Windows.

Source-Navigator doesn't (seem) handle local variables like global
variables (WRT the GUI).  It filters them out most of the time and
I only see them in "show references" branches of an xref.

There is a chance of some weird stuff going on under Windows
WRT to local variables.

Ian.

  reply	other threads:[~2001-08-10 10:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-10  1:39 Mike_D_Davies
2001-08-10 10:21 ` Ian Roxborough [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-08-14  1:08 Mike_D_Davies
2001-08-09 16:33 Keogh, Craig
2001-08-09 17:14 ` Ian Roxborough

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=3B741AB3.932EE7E3@redhat.com \
    --to=irox@redhat.com \
    --cc=Mike_D_Davies@fmo.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).